Printable View
http://www.microsoft.com/downloads/d...displaylang=en
Previously known as WinFx.
I don't agree with the naming though, as it's not actually a new framework version, but simply the 2.0 framework combined with new technologies. They cited 'developer confusion' when renaming it. (Thanks a lot, stupid developers... I didn't even know they existed) :rolleyes:
Anyways, I wonder about Orcas now...
They finally discovered nobody reads the license agreement so now it doesn't take a full page it's smaller than the quick reply box
Huh? :confused:
i once read that it was always best to read the licence agreement... because of some case in sweden where the poor person in question downloaded a file, and just skipped the licence agreement as we all do, and actually installed a virus in his system.. .. the funnienst thing was that in the licence agreement there was a part...and you are hereby agreeing that you are installing the ***** virus in your system... so be careful what you install...
cheers
patrick:Wave:
This thread gets more and more surreal. :ehh:
I'll stay on topic and agree with you. This whole .Net 3.0 thing threw me off too.
Not to mention, it's throwing my superiors off. We're still using .Net 1.1 here and I've been doing everything I can to convince them to move to 2.0. Now they see that 3.0 is coming out and no matter how much I try and explain to them that it's just an "expansion" for 2005, they don't want to upgrade from 1.1 until it's released.
Sooooo... Now we get to stay even further behind the tech curve. :sick:
version 2.0 is released and it's better than 1.1Quote:
they don't want to upgrade from 1.1 until it's released.
This thread gets more and more and more surreal. :ehh:
I understand that 2.0 is better then 1.1... And I know it's released, hence the reason I mentioned that i've been pushing so hard for them to upgrade to it. But they don't want to upgrade until 3.0 is released.... Which is 2.0 + the windows fx.
I think you should switch to WinG....just to continue the surreal theme.
The renaming was a bit stupid - it seems that M$ have learnt nothing from the Windows.NET fiasco.
You could always panic your superiors into getting .Net 2.0 by musing aloud about whether there will be an upgrade tool that goes from 1.1 to 3.0 ;)