Welcome to AspAdvice Sign in | Join | Help

Does Microsoft Buy In To .NET?

Every now and then some high profile personality, perhaps one who once had close ties to Microsoft, about how .NET is really a total failure.  How it's clear that it isn't going anywhere.  That, as proof of these assertions, Microsoft cannot even manage to use it for its own products, so why should we?  Personally I think these kinds of articles are rather easy to debunk, and show that their author is either ignorant of the facts (which is unlikely) or has a personal agenda that is coloring his or her opinion (which is pretty much a given - yes, I have one too).

Here is some information I have gathered on approximate numbers of managed code in a few Microsoft products.  The point of providing this information is simply to show that yes, there are in fact .NET developers working at Microsoft, and yes, they are building actual shipping products.

Managed Code

  • Visual Studio 2005 - 7.5 million lines
  • SQL Server 2005 - 3 million lines
  • BizTalk Server - 2 million lines
  • Visual Studio Team System - 1.7 million lines
  • Windows Presentation Foundation (formerly Avalon) - 900,000 lines
  • Windows Sharepoint Services - 750,000 lines
  • Expression Interactive Designer - 250,000 lines
  • Sharepoint Portal Server - 200,000 lines
  • Content Management Server - 100,000 lines

Another great one I don't have stats for is CRM 3, which is written almost entirely in .NET.  And of course this doesn't even go into things like ASP.NET, which is itself written in .NET.

Given the fantastic growth of .NET adoption over the last 5 years (sorry, no figures handy, but it surpassed Java a couple of years ago and has retained its lead) and the tremendous improvements in the framework and IDE that have come with version 2.0 as of last year, I hardly see .NET as a product on its way out.  Maybe I'm just being blinded by how closely entrenched I am in .NET development and community, but I don't think that's the chief explanation.  I think there is some truth in the statement that .NET is alive and well and continuing to improve.

Published Thursday, March 16, 2006 9:12 AM by ssmith

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: Does Microsoft Buy In To .NET?

Hi Steve,

Very interesting figures, it gives an idea how complex those products are :). One of the MS guys from BizTalk team said that BizTalk 2004 is written entirely using .NET Framework (C#).
<br>
Personally I'm still not sure that .NET is retained its lead over Java, I have to say that Java at the moment is major Enterprise Dev platform, and probably this situation will stay for next few years. I'm a .NET developer, and .NET as a platform is much more standardized and developer friendly than Java.
Thursday, March 16, 2006 6:06 PM by Max Mulawa

# re: Does Microsoft Buy In To .NET?

Steve. Another product is Microsoft Project Server 12 (or 2007 I believe they are calling it). Almost all Server Side code is managed code (according to demos at the Project Conference in January I went to). They are using the 2.0 .NET framework for this. Not sure how many lines of code that will be.
Friday, March 17, 2006 9:05 AM by Eric Landes

# re: Does Microsoft Buy In To .NET?

Just bumped into this post by Scott Swiggart, which touches on this same topic (in the form of a rebuttal against an extremely long attempt to prove that MS is in fact ditching .NET).

http://swigartconsulting.blogs.com/tech_blender/2006/03/microsoft_gives.html
Friday, March 17, 2006 7:46 PM by Michael K. Campbell

# re: Does Microsoft Buy In To .NET?

I think different groups within Microsoft have bought into .NET, in greatly varying amounts. The developer and enterprise products groups are cranking out tons of code, but there's very little .NET code on a fresh Vista install. The Office .NET code investment is at the bridge stage at best - the core is still oldschool C++.

I know that .NET is Microsoft's future, but I wish they'd make some bigger on it.
Saturday, April 15, 2006 2:09 AM by Jon Galloway

# re: Does Microsoft Buy In To .NET?

Could somebody explain the main reason why Managed C++ is not a viable option for Vista?  At what point does the .NET Library break down in regards to writing an OS?  Why does Microsoft need to resort to Unmanaged Code in order to do Vista?  Call me a Conspiracy Theorist, which I consider a badge of honor these days considering the 911 fiction, but maybe Microsoft does this because it is easier to keep things at that level Proprietary and protected?  .NET almost seems to me to be the Public Wrapper around the Proprietary C++ OS Code that allows Microsoft to play on a whole other playing field than the public when it comes to writing programs?  Office is there Bread and Butter, and just coincidently, it is the least based .NET Product?  Too much Code to re-write?  Nonsense...  The .NET Library allows them to filter out the functionality of the Core OS in the way they see fit.  I am pro Microsoft and love their products, but something doesn't seem right in Denmark when they don't make .NET good enough to use for everything.

If this is their motive, I suggest they make part of the .NET Library Fee Based where you can use certain Functions using a Certificate Key and then maybe be charged a Subscription Fee every time you call into the BlackOps.NET Library.

Sunday, January 07, 2007 5:37 PM by IlluminatiPilot

Leave a Comment

(required) 
required 
(required) 
Enter the code you see below