Thursday, October 09, 2003
Getting caught in a .NET?
If you're developing Windows applications not looking at or already using .NET, you should be. In response to a question on the Universal Thread, I made the following observation:
If you do a bit of research, you'll find that .NET will get into everything MS. Examples:
- Developer tool division pushing Visual Studio .NET and VB.NET and C#
- Yukon, the next version of SQL Server will support some type of .NET coding for stored procedures
- Office 2003 supports .NET and VBA
- Win32 APIs will go into maintenance mode in the next version of Windows, code named Longhorn. These APIs will be replaced/superceeded with .NET assemblies
- Some new features of Longhorn will require the use of .NET. There is some question as to if VFP and other COM/API based languages/tools will be able to support these new features.
If you're developing Windows applications not looking at or already using .NET, you should be. In response to a question on the Universal Thread, I made the following observation:
If you do a bit of research, you'll find that .NET will get into everything MS. Examples:
- Developer tool division pushing Visual Studio .NET and VB.NET and C#
- Yukon, the next version of SQL Server will support some type of .NET coding for stored procedures
- Office 2003 supports .NET and VBA
- Win32 APIs will go into maintenance mode in the next version of Windows, code named Longhorn. These APIs will be replaced/superceeded with .NET assemblies
- Some new features of Longhorn will require the use of .NET. There is some question as to if VFP and other COM/API based languages/tools will be able to support these new features.
Subscribe to Posts [Atom]