R
RichW
I suddenly started having this problem as well - and could not figure
it out. MSDN stated you simply had to re-install VS.NET, which I did.
However, the same problem persisted.
It appears I finally figured it out. I had loaded the Office XP PIA -
but stupidly neglected to do this from the Visual Studio .NET 2003
CommandPrompt. I created 'unregister.bat' from register.bat by simply
replacing the "-i" with "/u" for the gacutil statements. As in:
gacutil /u assembly_display_name
After running 'unregister.bat' from the VS.NET CommandPrompt I then
ran 'register.bat' from the VS.NET CommandPrompt and - voila! -
everything miraculously worked again.
I added this post because I imagine erroneously adding anything from
the regular DOS command prompt instead of correctly through the VS.NET
CommandPrompt may well have the same - or at least similarly annoying
- result. This had me pulling my hair out - so I hope this helps at
least one other person out there.
Best,
- Rich
it out. MSDN stated you simply had to re-install VS.NET, which I did.
However, the same problem persisted.
It appears I finally figured it out. I had loaded the Office XP PIA -
but stupidly neglected to do this from the Visual Studio .NET 2003
CommandPrompt. I created 'unregister.bat' from register.bat by simply
replacing the "-i" with "/u" for the gacutil statements. As in:
gacutil /u assembly_display_name
After running 'unregister.bat' from the VS.NET CommandPrompt I then
ran 'register.bat' from the VS.NET CommandPrompt and - voila! -
everything miraculously worked again.
I added this post because I imagine erroneously adding anything from
the regular DOS command prompt instead of correctly through the VS.NET
CommandPrompt may well have the same - or at least similarly annoying
- result. This had me pulling my hair out - so I hope this helps at
least one other person out there.
Best,
- Rich