I read a comment to a thread on Scott Hanselman’s blog that said “The day Microsoft is writing Office, Media Player, Visual Studio totally in .NET is the day I would expect that Windows Forms are finally ready.” I wanted to talk about that and a few other misconceptions (as I see them).
When a company moves to a new development framework like .NET – I don’t expect anyone to immediately do so. You pick a new application, build it, see the ROI, the training time involved, and work from there. You select portions of applications that are being built and can be separated, and start there. We’re doing that her at Microsoft. Here’s a partial list of applications (internal and external) that use .NET. I’m not including things like Windows Server 2003 that included the framework; but I am including any applications that ship with it and are built on the framework.
My point here is that we have made a bet across the company on managed code. We use it internally in our own IT systems, we are writing new applications with it, and we are continuing to do so.
A similar question often arises – which language does Microsoft use? The answer is yes. <g> Many of our applications were written in C++, and those developers now write applications in Managed C++ and C#. Much of our testing and many internal systems were written in VB6, and are now being written in VB.NET. The nice thing is that these can all interoperate, and you can use your knowledge in the other languages to move forward to the .NET versions.