"Stephanie" <St*******@discussions.microsoft.com> wrote in message
news:74**********************************@microsof t.com...
I have VB.NET 2003 installed that I used in a recent college course. It
worked fine. This week I started another class and when I went to open a
project, I got a fatal error.
I tried to reinstall VB.NET and got the same error.
I tried to UNINSTALL VB.NET and got the same error.
At the moment, I'm not at home so I can't tell you what the error is. How
can I uninstall this thing and reinstall when I get this error?
--
Steph
What changed between the time "it worked" and when it "didn't work"? Windows
Updates?
Not being a ".Net" guy, the only suggestion I can make is.... uninstall the
whole shabang. Run your favorite registry cleaner, reboot and run it again.
Reboot and reinstall Visual Studio. Cleaning the registry is an important
step that's often overlooked. This is especially important for any MS
installer that shows a dialog that reads "looking for installed components".
Sometimes, the registry is the only place that installer looks for these
components. I know this from experience (specifically, problems related to
installing MS Office)
If you don't have a registry cleaner, grab one. Every developer should have
one they feel comfortable with. The one I use is System Mechanic
(
www.iolo.com). For VB6 stuff (since that's what I know), MS's RegClean is
usually "good enough" but I don't have a clue about how it works with .Net
registry entries.
--
Ken Halter - MS-MVP-VB (visiting from VB6 world) -
http://www.vbsight.com
Please keep all discussions in the groups..
