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 / IDE / November 2005

Tip: Looking for answers? Try searching our database.

Visual Studio 2005 RTM macros no longer work

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
weigeltro - 02 Nov 2005 10:48 GMT
Whenever I want to run a macro inside VS2005, I get a runtime error in
"vsmsvr.exe". Neither a repair installation nor a complete
uninstall/install solved the problem.

The problem started after I accidently removed the VSMacros80 folder
(my fault); but now that everything is restored (complete reinstall,
see above), I guess that the problem is some registry setting or a
config file or whatever that didn't get fully initialized to "factory
settings".

Any idea what I can do?
weigeltro - 02 Nov 2005 17:01 GMT
> Whenever I want to run a macro inside VS2005, I get a runtime error in
> "vsmsvr.exe". Neither a repair installation nor a complete
> uninstall/install solved the problem.

I did yet another reinstall, this time uninstalling using the removal
tool that was intended for removing the Betas (hoping it would clean up
a bit more). In addition to that, I tried to remove virtually
everything that looked like configuration data somewhat related to
vsmsvr.exe, from the registry (HKLM and HKCU) and from the Application
Data folders (VSA\8.0). Unfortunately, after installing VS2005, the
problem occurred again.

"Just for fun" I removed vsmsvr.exe and vsmsvr.exe.config , hoping I
would trigger some kind of repair mechanism of VS. Funny thing, I can
now record a macro, enter the macro IDE and leave it again without
getting an exception, but of course I cannot play back any macros
(d'oh).

I then copied both files back to their original place, but the
exception is there again.

Just to give as much information as possible, there are two occasions
when I get an execption:

1. Record a (temporary) macro in Visual Studio, then try to play it
back -> Exception
2. Enter the macro IDE, edit some macro (maybe just change a comment)
and save it. Leave the macro IDE -> Exception

The exception is in vsmsvr.exe, "unknown software exception
(0x40000015) occurred in the application at location 0x7813461a."
weigeltro - 02 Nov 2005 23:45 GMT
Ok, another update that may be helpful for other people:

I finally got it working by using a repair installation, but
unfortunately I'm not quite sure what *exactly* made the difference.

My theory was that I had to "break" Visual Studio enough to really
trigger a repair during repair installation, so I deleted vsmsvr.exe
and vsmsvr.exe.config (as described in my second post) and *then* ran
another repair installation - after which everything worked fine.

I'm saying I'm not exactly sure because before deleting the files and
running the repair install, I somehow (e.g. by deleting macro files and
then recording a macro) managed to get to a "catastrophic failure" and
the macro IDE complaining that MyMacros.vsmacros wasn't a valid
assembly (keep in mind I really wanted to break stuff ;-). Maybe this
also contributed to the success of the repair install.

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.