« previous next »
Pages: [1]   Go Down
Share this topic on AskShare this topic on Del.icio.usShare this topic on DiggShare this topic on FacebookShare this topic on GoogleShare this topic on LiveShare this topic on MagnoliaShare this topic on MySpaceShare this topic on RedditShare this topic on SlashdotShare this topic on StumbleUponShare this topic on TechnoratiShare this topic on TwitterShare this topic on YahooShare this topic on Google buzz

Author Topic: MS .NET Framework: I have 3.5, can I delete these other ones?  (Read 630 times)

0 Members and 1 Guest are viewing this topic.

Offline PCAddict

  • New Member
  • *
  • Posts: 1
MS .NET Framework: I have 3.5, can I delete these other ones?
« on: November 22, 2009, 10:55:49 PM »
Hi,

I am looking in Add/Remove Programs and I see:

MS .NET Compact Framework 2.0 SP2
MS .NET Compact Framework 3.5
MS .NET Framework 1.1
MS .NET Framework 2.0 Service Pack 2
MS .NET Framework 3.0 Service Pack 2
MS .NET Framework 3.5 SP1

Do I need ALL of these for 3.5 to work correctly? Or can I delete some of them?
I tried to decipher everyone's opinions on the net, but it got a bit confusing.
Logged

Offline Just Rachel

  • Premium Member
  • *****
  • Posts: 359
  • Always learning
Re: MS .NET Framework: I have 3.5, can I delete these other ones?
« Reply #1 on: November 23, 2009, 12:06:01 AM »
No.  One does not replace another.  One program may use 3.5, one program may want 1.2.  Annoying, isn't it??  ;D
Logged

Offline couttsj

  • Hero Member
  • *****
  • Posts: 516
Re: MS .NET Framework: I have 3.5, can I delete these other ones?
« Reply #2 on: November 23, 2009, 09:13:34 AM »
If you understand what Microsoft is attempting to do with .NET, then you might understand why all these different versions MAY be necessary. I say may, because it depends entirely on what software you are running. With the original Visual Studio 6.0, a programmer had to distribute the various library files needed for the program to run. These sometimes became quite large, and conflicting DLL files created what was known as DLL Hell.

With .NET, Microsoft introduced a new interface that combined all these library files into a single install. That meant that a program distribution did not have to include all the various library files that might be needed; it just needed a particular version of the .NET interface installed. Unfortunately, the various .NET interfaces are not backwards compatible.

J.A. Coutts
Logged
Pages: [1]   Go Up
« previous next »