.NET Archive

Microsoft: .Net Beat Java, Who’s Next?

Microsoft is leaving Java in the dust, but the company still has room to grow in the developer arena, a key executive said. Speaking at the Microsoft FAM (Financial Analyst Meeting) on July 27 in Redmond, Wash., Bob Muglia, Microsoft's senior vice president of Server and Tools business, said Microsoft's .Net platform has outpaced Java, particularly the Java Enterprise Edition, over the past five years to become the development platform of choice for enterprise development.

WinFX Is Officially .NET Framework 3.0

When speaking to developers about WinFX one question that repeatedly comes up is, "WinFX sounds great, but what happens to .NET?" Vice President S. Somasegar describes the decision to rename WinFX to the .NET Framework 3.0. Now the WinFX technology you know has a name that identifies it for exactly what it is - the next version of Microsoft's developer framework.

Hooking Windows Messages in .NET

"In the previous article in this series, you discovered a whole world of messages that the .NET Framework doesn't even capture. These messages can signal all kinds of events, request changes, and even can end your application. Unfortunately, the techniques described in that article only work for messages that the CLR passes to your application. Sometimes, you want to track messages that the CLR doesn't support."

Creating Scripts with Monad

"Microsoft's Monad provides a new command processor and a new way to create batch tasks. They leave the antiquated batch file in the dust. Monad offers you the full power of the .NET Framework to create your batch files. Its depth of functionality makes it part batch file and part application environment. Theoretically, you can create a full-blown application using just this scripting environment."

Working with Windows Messages in .NET

"You might not be familiar with messages, but they're extremely important, especially when you need to perform tasks outside of the range of tasks that Microsoft programmed into the .NET Framework. All communication in Windows relies on messages. This article reveals Windows messages to you, shows you how to capture messages that a .NET application doesn't normally capture, and demonstrates how to generate messages that .NET applications don't normally generate. In short, by the time you finish this article, you'll know about an entirely different world: the one that the .NET Framework hides from view."

Karmencita: Object Query Language for .NET

"Karmencita is a high level object query language for .NET. It's purpose is to allow easy querying from in memory structured data. Features: easy, SQL like language; common, slim API used for querying data; supports any IEnumerable data source, DataTables and XmlDataDocuments; extensible implementation; and much more."

Microsoft Porting C# Programming to the Mac

On his blog, Mike Harsh of Microsoft writes that the support of WPF/E on the Macintosh platform will not be limited to a JavaScript engine: "WPF/E supports programmability through JavaScript for tight browser integration. The WPF/E package also contains a small, cross platform subset of the CLR and .NET Framework that can run C# or VB.NET code. Yes, we are bringing C# programming to the Mac."

Analysis of .NET Use in Longhorn, Vista

This article presents results of an investigation of the usage of .NET on five versions of Windows. The operating system files for the first version of Windows tested, XP Pro with Service Pack 2 applied, did not use .NET at all. This is understandable because XP was released before .NET was first released. The next version of Windows was the PDC 2003 build of Longhorn. This has a similar number of unmanaged executable files as XPSP2 but it also had thirty five .NET assemblies. Amongst these assemblies were two services.

New Language Features in C# 3.0

C# 2.0 is just out and Microsoft is already working hard on the next version of C#, version 3.0. In this post, Niek describes a few of the new language features that will be introduced in this version. Please note that the resulting binaries will be backwards compatible with .NET 2.0, so C# 3.0 is only new on the compiler side.

Presenting Data with the DataGridView Control in .NET 2.0

In .NET 1.0, the DataGrid control was the primary Windows Forms control for presenting tabular data. Even though that control had a lot of capability and could present basic tabular data well, it was fairly difficult to customize many aspects of the control. Additionally, the DataGrid control didn’t expose enough information to the programmer about the user interactions with the grid and changes occurring in the grid due to programmatic modifications of the data or formatting. Due to these factors and a large number of new features that customers requested, the Windows Client team at Microsoft decided to introduce a replacement control for the DataGrid in .NET 2.0. That new control, the DataGridView control, is the focus of this chapter.