Microsoft .NET Framework 1.1 vs v1.0.3705

[CTMax]

Hi,

On Win XP, Control Panel, Add or Remove programs

I have entries for both the following:

Microsoft .NET Framework (English) v1.0.3705 size 1,008.00MB
and
Microsoft .NET Framework 1.1 size 36.15MB

Do I need both or can I delete the v1.0.3705 ?

Thanks,

..... tom ..

 

[Matt Berther]

Hello CTMax,

There was a lot of efforts made to keep .NET 1.1 backwards compatible with
1.0.

You might review some of the changes at http://www.gotdotnet.com/team/changeinfo/default.aspx
to see if they break your applications. If not, you should be good to uninstall.

Do keep in mind though that VS.NET 2002 only works with .NET 1.0, so you
wont be able to use it if you uninstall.

 

[Sahil Malik]

Just keep both.

Certain programs could rely on it's existence.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik

 

[BBFrost]

We have a very large (20+ custom user controls / 100,000 lines of code) data
entry program developed in .Net 1.0 (v1.0.3705 ). Its run flawlessly for
over 2 years now.

A few monthis after Net 1.1 was released we successfully upgraded the app to
Net 1.1 tested it and rolled it into production. About 4 or 5 days after the
production rollout the Data Entry people began to run into very strange /
insidious bugs the worst being that dropdown combobox behaviour changed very
subtly when a non-combobox list entry was retrieved from the database. The
change caused data corruption in some instances. MS Tech support created a
'private build' to correct this problem. Unfortunately, the build caused
another set of problems when installed.

We also had Alt A (add), Alt D (delete) and Alt U (update) buttons on most
of the 20+ user controls. We found that on most of the user controls that
pressing Alt A to activate the 'add' command button worked as before but on
one or two of the less used controls Alt A actually triggered the add button
on another non-visible / non-active user control. Microsoft tech support
sent software patch that I added to each user control to correct this
problem.

At that point we decided that to simply install Net 1.0 and Net 1.1 on all
our workstations until we had the time & resources to properly upgrade the
Net 1.0 app. At this point we'll probably wait until Net 2.0. We currently
have Net 1.0 and Net 1.1 apps running side by side on our machines with no
major problems.

Hope this helps.

Barry
in Oregon

 

[nikko]

We have a very large (20+ custom user controls / 100,000 lines of code) data
entry program developed in .Net 1.0 (v1.0.3705 ). Its run flawlessly for
over 2 years now.

A few monthis after Net 1.1 was released we successfully upgraded the app to
Net 1.1 tested it and rolled it into production. About 4 or 5 days after the
production rollout the Data Entry people began to run into very strange /
insidious bugs the worst being that dropdown combobox behaviour changed very
subtly when a non-combobox list entry was retrieved from the database. The
change caused data corruption in some instances. MS Tech support created a
'private build' to correct this problem. Unfortunately, the build caused
another set of problems when installed.

OMG, sounds like the dreaded "DLL HELL" that .Net was suposedto
eliminate. Thanks there, MS. You fixed it once and for all!