Posted By: mawcc | Jun 9th, 2006 @ 2:37 PM
page 3 of 3
Comments: 56 | Views: 20870
The problem is that MS has recently released 2.0 but not many computers in the world have 2.0, and that is a real limitation to .NET developers in terms of deplyment into user's machines. Many users in the world have dial-up and they cant download a 300 MB (approx) file because its takes for ever to do so.

I think there needs to be a better way to make .NET framework 2.0 and 3.0 mandetory for all Windows machines in windows update.
They really put themselves in a bind. It's short-sighted. What are they supposed to call future versions? And Compact Framework 3.5? Even though there's no "3" (WinFX) on the Compact Framework?

http://www.petitiononline.com/winfx/petition.html
ZippyV
ZippyV
Fired Up
It's not an effort to look at the dates before you post, it's fun. Check out the date of a post before replying.
omg that's crazy, I was looking at the thread title and was thinking one big wtf, how I didn't know about that, then I checked the timestamp...
Looking back though, calling it .NET 3.0 was a terrible idea.
Yggdrasil
Yggdrasil
Pour me a cab, 'cause I can't drink no more.
I disagree. It kept the .NET brand strong by having all the programming libraries be a part of .NET. 
.NET 3.5 is a superset of 3.0 which is a superset of 2.0. It's not entirely intuitive, but it's very simple once you're told.
When I ask someone what version of the framework he has installed, it tells me everything I need to know - I don't have to ask "Well, in addition to .NET 2.0 do you also have WinFX? How about the LinqFX?". The version number says it all.
page 3 of 3
Comments: 56 | Views: 20870
Microsoft Communities