I can't open any VB projects after uninstalling the add-in.
Of course, I have no 100% proof that this is directly caused by uninstalling the add-in, however it's the only explanation, because I haven't done anything else other than rebooting.
When I try to open a solution I get "Project 'XYZ' could not be opened because the Microsoft Visual
Basic .NET compiler could not be created. Please re-install Visual Studio."
I don't want to re-install VS, because I tried this in another case 8 weeks ago and it ended with re-installing Windows. So I'm looking for a smarter solution.
Any idea what to do?
How can I find out what the uninstaller did?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2005-02-18
If the author is reading this: I didn't issue a bug report yet. Probably you should verify what the uninstaller is doing. Of course, it may also be a bug in Visual Studio, not cleaning up stuff after uninstalling add-ins.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Some users experienced this problem, so it seems to be related to the vb.doc addin. However, I'm not able to reproduce the behaviour on my machine which means that it's rather difficult to help you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't open any VB projects after uninstalling the add-in.
Of course, I have no 100% proof that this is directly caused by uninstalling the add-in, however it's the only explanation, because I haven't done anything else other than rebooting.
When I try to open a solution I get "Project 'XYZ' could not be opened because the Microsoft Visual
Basic .NET compiler could not be created. Please re-install Visual Studio."
I don't want to re-install VS, because I tried this in another case 8 weeks ago and it ended with re-installing Windows. So I'm looking for a smarter solution.
Any idea what to do?
How can I find out what the uninstaller did?
If the author is reading this: I didn't issue a bug report yet. Probably you should verify what the uninstaller is doing. Of course, it may also be a bug in Visual Studio, not cleaning up stuff after uninstalling add-ins.
Some users experienced this problem, so it seems to be related to the vb.doc addin. However, I'm not able to reproduce the behaviour on my machine which means that it's rather difficult to help you.