software

Microsoft .NET Framework Version 2.0 - Final Released

darkrats   on 28 October 2005 - 18:02 · 32 comments & 3000 views

Advertisement (Why?)
Microsoft has today released the final versions of the Microsoft .Net Framework Version 2.0. The Microsoft .NET Framework version 2.0 redistributable package installs the .NET Framework runtime and associated files required to run applications developed to target the .NET Framework v2.0. The .NET Framework version 2.0 improves scalability and performance of applications with improved caching, application deployment and updating with ClickOnce, support for the broadest array of browsers and devices with ASP.NET 2.0 controls and services.

Download: .NET Framework Version 2.0 Redistributable Package (x86)
News source: ActiveWin.com


According to Download.com, "Version 1.5.990.26 may include unspecified updates, enhancements, or bug fixes".

Post a comment · Send to friend Comments · There are 32 additional comments
(3 replies) #1 Galley on 28 Oct 2005 - 18:20
Dang, I just installed 1.1 on my work PC to run SyncToy.
#1.1 ev0| on 28 Oct 2005 - 20:25
That's not how it works. Apps requiring 1.1 will still need and use 1.1. You can have multiple versions of the framework installed simultaneously.
#1.2 ThunderRiver on 29 Oct 2005 - 04:29
That's a problem.. being a developer I was told that programs written in 1.1 should be able to run on 2.0
I was beta testing for VS.NET 2005..and verified the compatability.
It does appear to me that Microsoft insisted on 1.1 framework in SyncToy. I bet that if they remove the restriction, it will run fine on 2.0
#1.3 ev0| on 29 Oct 2005 - 05:09
some things will run in 2.0 but not everything
#2 Tekmaven on 28 Oct 2005 - 18:26
I've been waiting well over a year for this
#3 MadCap on 28 Oct 2005 - 18:34
I wonder when or if this will hit windows update
(2 replies) #4 insanekiwi on 28 Oct 2005 - 18:35
now i just gotta wait for a localized german version
#4.1 Blackice on 29 Oct 2005 - 02:12
errr... a localised framework doesn't make sense.

A localised version doesn't exist. Download this one.
#4.2 insanekiwi on 29 Oct 2005 - 06:31
this one is in english only. previous version never installed on my system and yes, there were localized .net packs.
#5 no-sweat on 28 Oct 2005 - 18:37
my life is now complete
(3 replies) #6 darkrats on 28 Oct 2005 - 18:52
There's some uncertainty over whether programs written for 1.1 will run under 2.0. You may have to have both installed on your system to take full advantage of this product. Can anyone confirm this?
#6.1 IGx89 on 28 Oct 2005 - 18:58
AFAIK, 1.1 programs require and by default only use 1.1. I've been trying to force a 1.1 application to use 2.0, but don't think I've succeeded yet...
#6.2 greenreaper on 28 Oct 2005 - 21:11
There are very few breaking changes between 1.1 and 2.0. Most apps should run under both. By default they will run under the one they were compiled for, unless that is not available.
#6.3 Blackice on 29 Oct 2005 - 02:23
.NET versioning will stop most 1.1 apps running under 2.0 (for a good reason, too). I don't think apps will change their dependencies just because the version you need isn't on the system. As I understand it, for an app to use 2.0, it must be recompiled (although 1.1 works fine - this is a feature extension, not a performance boost/bugfix as such, and therefore not a neccessary upgrade. Therefore, Microsoft don't care about compatibility with older apps as such).

Remember DLL HELL? Yea, well that's why we have versioning... to allow 1.0,1.1,2.0,x.x framework versions to be installed simultaneously.
#7 niel19_us on 28 Oct 2005 - 18:57
I have been using 1.1 7 2.0 beta 2.0 beta repack for a while now without any problems. I will install 2.0 today see how it works.
(1 reply) #8 antoxicion on 28 Oct 2005 - 19:30
when i try to install this , it says i gotta go uninstall 2.0 beta and when i try to uninstall it wont let me because it says some applications use it and it'll screw them up and just exits
#8.1 Smigit on 28 Oct 2005 - 20:32
follow the link and uninstall all the aps they list there. Furthermore I had to look through and delete Win FX beta and I deleted Microsoft Max for good measure. Took me a bit to work out.
#9 Betaz on 28 Oct 2005 - 20:10
Quick link for those of us on Windows XP x64.

.NET Framework Version 2.0 Redistributable Package (x64)
#10 soldier1st on 28 Oct 2005 - 21:38
well version 2.0 is good to have,along with 1.1 just to be sure there won't be any problems.
#11 TickleOnTheTum on 29 Oct 2005 - 00:53
I still don't see what the point of .NET is for standalone programs. All it does is make little one off utilites require bigger downloads, and bigger programs more complicated. Give me old fashioned Delphi anyday...
(3 replies) #12 StarfireCT on 29 Oct 2005 - 01:58
Delphi has a run time, as did VB6, MFC, OWL, and on down the line. The nice thing about the .NET Framework from an end user point of view is that it's a one time download; all other applications that use it don't have a runtime to download. Case in point: SharpMT is just about a 2MB download - if it was coded without .NET for support it probably would have been 8MB+.

From a developer point of view, you can use a number of languages to code with and always have the same common object model. Also includes things like garbage collection and strong typing and makes using third party controls MUCH easier... oh, and it will probably be included in future releases of Windows.

All that for a 20MB download once every two years or so, usually via Windows Update. Not too much to ask, IMHO.
#12.1 Blackice on 29 Oct 2005 - 02:17
not only will it be included in future versions of windows, but there's a good chance large portions of windows will be converted into managed code. Either that, or the new features will be written in managed code, and the old peices left (like WinFX, for instance).

Another benefit of .NET from a developer PoV are features like generics (2.0) and, most importantly, LINQ (3.0) - fusing SQL and .NET languages. .NET is what's happening today, and as such, is most appropriate for applications running on today's PCs.

.NET is also platform independent... ish.
#12.2 theyarecomingforyou on 29 Oct 2005 - 11:36
QUOTE
.NET is what's happening today, and as such, is most appropriate for applications running on today's PCs.


I disagree. If Windows came with it already then that may be the case but as it stands most users don't need .NET and don't have it installed; when they come across an application that does they need to download the app (2MB) and the framework (22MB) - not so practical.

Also, .NET doesn't exactly have a reputation for the fastest code - a quick look at ATi's Control Center shows a speed problem (I'm not saying one application determines the whole effectiveness of a platform, just an indication). .NET has been very slow to catch on and that doesn't look set to change (unless it is bundled with Windows, and any success from that would be due to logistics, not any strengths of the platform).
#12.3 ev0| on 29 Oct 2005 - 16:37
obviously you're not a programmer.
(2 replies) #13 seta-san on 29 Oct 2005 - 07:29
i never could quite figure out what .NET is... what exactly does it mean?
#13.1 frogworm on 29 Oct 2005 - 15:34
think of it as Microsoft's Java Virtual Machine except that Microsofts .NET framework supports a buttload more programming languages
#13.2 ev0| on 29 Oct 2005 - 16:35
and it is way faster too
#14 Chanser on 29 Oct 2005 - 08:34
If you have the ATI Catalyst 5.10a beta with CCC, the CCC doesn't like v2.0 only as it sometimes give errors or crashes or doesn't load. You must have v1.1 to make it work properly.
#15 nemesizz_ma on 29 Oct 2005 - 08:42
i can confirm it....

norton ghost 9 and 10 needs framework 1.1
catalyst needs 1.1

now i have 1.0 1.1 with sp and 2.0 on my pc *grrrrr*

the redis version is german and english!!!
(2 replies) #16 gregj66 on 29 Oct 2005 - 13:08
why wouldn't v2.0 be backwards compatible?

Last edited by 7885 on 30 Oct 2005 - 03:27
#16.1 Dayon on 29 Oct 2005 - 16:03
Think of it this way: Why does Windows have so many security holes and problems? It mostly stems back to maintaining backwards compatibility. The .NET framework solves this entire issue. While it is mostly backwards compatible, they didn't go so overboard with backwards compatibility that they would eventually compromise the security and effectiveness of the framework. 1.0, 1.1, and 2.0 can all run on the same machine, and they should, if you have the requirement for them.
#16.2 gregj66 on 30 Oct 2005 - 03:29
thx

Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.

Advertisement (Why?)