Log in

View Full Version : No More Product .NET from Microsoft


Andy Sjostrom
01-09-2003, 11:17 AM
I just learned about the Windows .NET Server 2003 name change that Microsoft has had under NDA until today. The new server product will be called Windows Server 2003. Microsoft has instead come up with "Microsoft .NET Connected" requirements and an accompanying logo program that will help customers and partners identify ".NET-enabled" products. I think that Microsoft has been much more consistent regarding their ".NET" naming the past months than they were when ".NET" was first marketed. I hope the same stringency and consistency will be applied within the "Microsoft .NET Connected" program! I guess that we will eventually hear about "Microsoft .NET Connected" Pocket PCs, huh?<br /><br />Read on for more details from Microsoft! <!><br />"The product name Microsoft(R) Windows(R) .NET Server 2003 will be changing to Windows Server 2003. Microsoft is making an effort to clarify the naming and branding strategy for .NET. As support for Web services becomes intrinsic across our entire product line, we are moving toward a consistent naming and branding strategy to better enable partners to affiliate with this strategy and customers to identify .NET-enabled products. The first product to be affected is Windows .NET Server 2003. The new name for the next version of Windows is Windows Server 2003.<br /> <br />Details:<br />* We are pursuing an overall effort to clarify the naming and branding strategy around .NET. As support for Web services becomes intrinsic across our entire product line, we are moving toward a consistent naming and branding strategy to better enable partners to affiliate with this strategy and customers to identify .NET-enabled products.<br />* The next version of Windows Server will be formally called Windows Server 2003. The reason for this is to simplify the product's naming and reconcile it with our branding strategy for .NET.<br />* Windows Server 2003 will carry the "Microsoft .NET Connected" logo indicating its ability to easily and consistently connect disparate information, systems, and devices to meet customers' people and business needs (regardless of underlying platform or programming language). This logo is also available to our partners building solutions on the Microsoft platform to help customers identify solutions and products that support standards-based interoperability.<br />* The more complete integration of .NET Web services and products is one of several major enhancements in Windows Server 2003 -- all aimed at providing a highly connected, productive, and dependable infrastructure with excellent economic value for our customers.<br /><br />Questions &amp; Answers:<br />Q) Why the name change?<br />A) In response to customer and partner feedback to provide clarity around our .NET strategy and programs. Specifically, we are moving toward a branding approach where ".NET Connected" is the way we communicate our products (and our partners' products) that enable customers to easily and consistently connect disparate information, systems, and devices to meet their people and business needs, regardless of underlying platform or programming languages.<br /><br />Q) Why make this change now?<br />A) Product naming, features, etc. are never final until the product ships -- this is both in response to customer feedback as well as part of a larger effort to provide clarity for customers and partners interested in affiliating with and benefiting from Microsoft .NET. <br /><br />Q) What changes technically in the Windows Server product as a result of this name change?<br />A) There are no feature changes in the product. This is a naming change, and does not affect the functionality of the product in any way.<br /><br />Q) Will this cause a slip in the Windows Server 2003 product schedule?<br />A) No -- we remain on track for a worldwide launch of Windows Server 2003 in April 2003.<br /><br />Q) Is this an indication that Microsoft is backing away from .NET? <br />A) Quite the opposite -- Windows Server 2003 is a major step forward in our effort to provide a highly connected, productive, and dependable infrastructure with excellent economic value for our customers. Windows Server 2003, with integration of the Microsoft .NET Framework, UDDI services, and other XML Web services support has set the industry bar for Web service development and performance -- combined with the new security, scalability, and performance of Windows Server 2003 and we are delivering a platform optimized for the next generation of enterprise computing."

Kevin Daly
01-09-2003, 12:02 PM
This is good news - it's nice to see a bit of sanity.

It was starting to make the mad, bad old days when everything was Active (ActiveX, Active Server Pages, Active Data Objects, Active Directory...I'll stop now) look like a mild case of excessive marketing-speak.

By restricting the use of the .NET branding in this way Microsoft will now have a much better chance of actually getting the .NET message across.

I wonder if this has implications for Windows CE.NET?

Janak Parekh
01-09-2003, 04:32 PM
This is good news - it's nice to see a bit of sanity.
Yes, thank god. It's also awkward to say "dot-NET" every time you have to mention a MS product. Now we can just call it "Win2k3 server". ;)

--janak

johncj
01-09-2003, 05:52 PM
I got this last night and it said NDA til today, and I thought to myself, "That means Andy will post if before I can tell them". Sure enough, I get up this morning and there it is....

I think this is a great idea. Microsoft's marketing department does occasionally listen to its customers.

Andy Sjostrom
01-09-2003, 08:19 PM
I got this last night and it said NDA til today, and I thought to myself, "That means Andy will post if before I can tell them". Sure enough, I get up this morning and there it is....

Sorry! Will delay my posts a little in the future! :lol:

Daniel
01-10-2003, 06:11 AM
It is about time!

The whole .Net marketing thing was ridiculous! .Net this, .Net that, talk about diluting the brand! Not to mention confusing existing and potential customers!

.Net as a programming language is excellent, however, naming everything as whatever .Net is just plane stooopid!

I'm glad MS changed this, great move!

I wonder if this has implications for Windows CE.NET
I would guess it would, seems like Windows CE 2003 (or in fact 2004 because that might be the next release and they've already released Windows CE.NET) would be likely.

Daniel

p.s. I run a mac but I'm happy to say that I have ROTOR running. :D
p.p.s When did .NET stop being .net which is what it was originally?

jgrnt1
01-11-2003, 09:06 PM
I'm not sure if this belongs here or not, or even if it's been mentioned before. I just downloaded Windows Media Player 9 for XP and found the EULA very interesting. It states that the software may contain components from the .Net Framework and I am forbidden from disclosing any benchmarks of the .Net Framework to third parties without Microsoft's permission.