From The Scobleizer Weblog: "Translation #2: Microsoft is trying to kill the Windows API and move toward a completely .NET future. Hmmm. Let your mind twist around that one for a few minutes."
This seemed obvious to me from the first time I worked with the framework, and it's a risky move. Developers know Win32. Many developers like to stick with what they know. I think if the .NET framework was presented as "Everything you know about writing a Windows application has just changed!", they would have had a much harder sell, and the media would have gone nuts with it. As it is, Microsoft has presented .NET in such a vague manner that few people really understand what it is.
I would rather P/Invoke didn't exist, and that they'd forced you to create a COM object if you wanted to access some native functionality - that way the COM interface could be implemented in a compatible way on a non-Win32 platform. It would also give developers an incentive to look for a native .NET way rather than going to the trouble of creating the COM object.
Considering that C# and .NET is really a brand new language on a new framework, it is pretty amazing how much good software is being written with it already. I think that's due to the quality of the tools - VS.Net makes it easy to jump in and start working with the framework even if you don't know much about it.
6:57:41 AM 
|
