Old Dot Net programs

[Guest]

In Control Panel/Add-Remove Programs I have listed:

MS .Net Framework Engl.v.1.0.3705
MS .Net Framework 1.0 Hotfix (KB886906)
MS .Net Framework 1,1
MS .Net Framework 1.1 Hotfix (KB886903)
MS .Net Framework 2.0

May I safely remove the first 4 on the list and if I do so will that also
remove MS .Net Framework SDK v.1.1 which is listed in Start/Programs?

Thank you for any assistance given.

Mary

 

[Michael Nemtsev]

Hello sweeneysmsm,

No. What's the reason doing this? There are a lot of apps that requires .NET
1.1 (several 1.0)

s> In Control Panel/Add-Remove Programs I have listed:
s> MS .Net Framework Engl.v.1.0.3705
s> MS .Net Framework 1.0 Hotfix (KB886906)
s> MS .Net Framework 1,1
s> MS .Net Framework 1.1 Hotfix (KB886903)
s> MS .Net Framework 2.0
s> May I safely remove the first 4 on the list and if I do so will that
s> also remove MS .Net Framework SDK v.1.1 which is listed in
s> Start/Programs?

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

 

[Guest]

I thought that .Net 2.0 would meet the needs of those applications. I spoke
of only removing the first 4 .Net programs. Are you saying that I have to
have a multitude of .Net Frameworks as new ones come out?

Mary

 

[Michael Nemtsev]

Hello sweeneysmsm,

s> I thought that .Net 2.0 would meet the needs of those applications. I
s> spoke of only removing the first 4 .Net programs.

No .NET 2.0 doesn't meet needs of previous .net's apps. You have no reasons
to remove previous versions because they works together without problems.

s> Are you saying that
s> I have to have a multitude of .Net Frameworks as new ones come out?

Indeed. Besause, afther u have unistalled .NET 1.x frameworks the first apps
that was builded with .net 1.x requires u to install it


---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch

 

[Jon Skeet [C# MVP]]

I thought that .Net 2.0 would meet the needs of those applications. I spoke
of only removing the first 4 .Net programs. Are you saying that I have to
have a multitude of .Net Frameworks as new ones come out?

Although (most) programs which were compiled to run on .NET 1.1 will
run on .NET 2.0 if 1.1 isn't available, there are a few
incompatibilities between the two versions. It's probably better to
keep 1.1 around to ensure that the 1.1 apps run in the environment
they're likely to have had most testing in.

 

[John Bailo]

You should be able to run and keep multiple versions.

You may acquire programs that need the earlier CLRs.

It's just like Java -- there are apps that need 1.2, 1.3, 1.4 JREs and
there are systems for managing those...

 

[Cor Ligthert [MVP]]

Jon,

Although (most) programs which were compiled to run on .NET 1.1 will
run on .NET 2.0 if 1.1 isn't available, there are a few
incompatibilities between the two versions. It's probably better to
keep 1.1 around to ensure that the 1.1 apps run in the environment
they're likely to have had most testing in.

I am in doubt if this is the best advice. I agree with what you write,
however the consequence from such a policy is that you should forever should
install all old versions on old computers.

Because of know problems I think that this should be limited in this Net 2.0
case because of known problems to the next servicepack.

Hoping that the job with that is done well.

Just my opinion.

Cor

 

[Cor Ligthert [MVP]]

John,

If I understand you well is what you write only for developing, have a look
to my other message to Jon about at the moment known problems.

Cor

 

[Jon Skeet [C# MVP]]

I am in doubt if this is the best advice. I agree with what you write,
however the consequence from such a policy is that you should forever should
install all old versions on old computers.

Well, only as long as you have programs which were developed on
..NET 1.1. That certainly won't be forever.

Because of know problems I think that this should be limited in this Net 2.0
case because of known problems to the next servicepack.

Not all the backwards incompatibilities are bugs, however. Some are
*fixes* to bugs in 1.1 which unfortunately change the behaviour. Some
are pieces of unspecified behaviour which were (incorrectly) relied
upon by the other pieces of software.