visual studio .net setup: VS fails starting after Office 2003 install -- visual studio .net setup

VS fails starting after Office 2003 install

hildebrand NO[at]SPAM uni-kassel.de
7/20/2004 1:48:25 AM

visual studio .net setup:

Hello,

after installing Office 2003 on my windows XP Profesisonal system,
when starting Visual Studio .net 2003, the Windows installer pooped in
and wanted to configure Visio. Since I was not in my office then, I
did not have the Visio Cd avaiable and eventually removed grudgingly
Visio from my notebook.

Then, when starting VS, the Windows installer wanted to configure the
MSDN library. I gave up...

Some days later, back in office, I searched the web for information
and learned that several people experineced similar problems. The
solutions proposed included e.g. removing .../Microsoft
Shared/Ofice10/mso.dll or manually registering one or the other dll.
These approaches changed the picture: Now when starting VS, for a very
short time there was a small dialog "preparing setup" and then VS
closed.

I tried a "repair" from the VS CD setup, but this did not help.

Finally, I downloaded the "Windows Install Clean Up" tool from MS and
cleaned the VS installation. Then I performed a new installation
"which included a complete deinstallation of the existing VS).
This worked; problem seems to be solved! :-)

I wanted ton share this experience with the community, because I think
it might help others. If somebody would be able to explain this odd
behaviour I really would appreciate this...!

Regards,

RE: VS fails starting after Office 2003 install

rschoe NO[at]SPAM online.microsoft.com
7/22/2004 7:55:20 PM

Problem:
The problem you were seeing was due to an issue with darwin I believe. The MSO typelib registration associated with the VS product was blown away by
the second product (Office in this case) and so the first product detects a product issue and tries to fix it by doing repair (which seems to never complete as
you have seen).

The best way that I know to correct this problem is to just go to Add/Remove Programs and complete a "Repair" of VS directly from there. This should of
fixed the problem. No need to run the clean up tool or uninstall.

thanks
Robert Schoen (Microsoft Visual Basic QA)
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
--------------------
[quoted text, click to view]