By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,168 Members | 2,511 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,168 IT Pros & Developers. It's quick & easy.

Uninstallation of VS.NET causing unknown problems

P: n/a
Hi there,

I have a small question regarding the uninstallation of VS.NET 2003/2005
and it's impact on the system. I have an application that functions as
desired on all freshly installed systems that match the correct requirements
for the application. Unfortunately there have been a couple of times where
an "Out Of Memory" exception has been reported when attempting to run the
application on certain systems, the only thing in common with these systems
is the installation and uninstallation of VS.NET 2003/2005.

All exceptions in the application are handled upon entry using our own
custom dialog and this exception is displayed before that is even
initialised which makes me very suspicious of the integrity of the .net
framework, so I have a few questions regarding this,

A) Is there any way to confirm the integrity of the framework?
B) Has anyone else experienced these anomalies?
C) Is there any correct way to get the .NET framework installation
back upto scratch, I'm presuming the following,

1) Uninstall all frameworks, newest to oldest
2) Reinstall all required frameworks, oldest to newest
3) Pray to which ever god you believe in

Thanks loads in advance, I'd love to get around this problem but the
only way I can think of is by freshly installing a system with .NET 2.0 on,
saving the registry, installing VS.NET 2005 then uninstalling it, saving the
registry again and comparing it to the original one and seeing if anything
was removed / changed that shouldn't have been. Even then I can't be sure
that it wasnt related to a file on the local system.

Hmm!

Nick.
Mar 31 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.