Downgrade from .Net 2.0 with sp1 to .Net 2.0 without sp1

[incrediblesuperdude]

Hi everybody,

I have a problem with a bug in the sp1 of .Net 2.0 which is reported
on this page:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=318620

Because of this a program I am using is not functioning well because
of it:
mscorlib.dll 2.0.50727.832 on the system without the service pack is
working correctly.
mscorlib.dll 2.0.50727.1433 on the system with service pack 1 is not
working correctly.

I now would like to downgrade my version of .Net 2.0 to the 832 dll,
but how do i do this?
I have already tried the following:
1. Uninstall .Net framework 2.0 sp1 from my machine to install .Net
2.0 without sp1 failed, because i could not uninstall .net 2.0 sp1
because of dependencies
2. I tried overcopying mscorlib.dll in C:\WINDOWS\Microsoft.NET
\Framework\v2.0.50727 with the previous version, which I copied from
another pc. The mscorlib.dll was actually not replaced, I got the same
problem.

Does anyone have an idea how to do this?

Kind regards,
Gerben

 

[Mike Powell]

Hi,
Have you tried activating the "administrator" user account and uninstalling
from there. For some reason installing and uninstalling certain VS products
requires more than just an administrator account with admin privileges
granted.
Otherwise, the reason your mscorlib.dll isn't replacing correctly is because
the CLR doesn't link to the DLLs stored in the
\WINDOWS\Microsoft.NET\Framework\ folder but to those stored in the GAC.

Michael Powell
Ramuseco ltd .NET consulting

 

[Mike Powell]

Hi,
Have you tried activating the "administrator" user account and uninstalling
from there. For some reason installing and uninstalling certain VS products
requires more than just an administrator account with admin privileges
granted.
Otherwise, the reason your mscorlib.dll isn't replacing correctly is because
the CLR doesn't link to the DLLs stored in the
\WINDOWS\Microsoft.NET\Framework\ folder but to those stored in the GAC.

Michael Powell
Ramuseco ltd .NET consulting

 

[incrediblesuperdude]

Hi,

Found the problem: .Net 3.0 and 3.5 are dependent on 2.0, so removing
3.0 and 3.5 allowed me to remove .net 2.0 sp1 and install .net 2.0
without sp1.
Everything is fine now..

regards,
g