Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Setup / July 2004

Tip: Looking for answers? Try searching our database.

VS fails starting after Office 2003 install

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Matthias Hildebrand - 20 Jul 2004 09:48 GMT
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,
Matthias
Robert Schoen (MSFT) - 22 Jul 2004 20:55 GMT
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)
Signature


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.  
--------------------

>From: hildebrand@uni-kassel.de (Matthias Hildebrand)
>Newsgroups: microsoft.public.vsnet.setup
[quoted text clipped - 45 lines]
>Regards,
>Matthias

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.