Cannot run any macros through Visual Studio 2003

[BuddyWork]

Hello,

Does anyone have the solution for the following issue?

I cannot run any macros (include the samples) from the Macro Explorer
using Visual Studio 2003. I've tried creating my own using the Recorder
and then trying to run it and it just does nothing. I have also
reinstalled VS 2003 and no joy.

Please help,

 

[Michael Rodriguez]

Hello,

Does anyone have the solution for the following issue?

I cannot run any macros (include the samples) from the Macro Explorer
using Visual Studio 2003. I've tried creating my own using the Recorder
and then trying to run it and it just does nothing. I have also
reinstalled VS 2003 and no joy.

Please help,

I had this same problem. Go to the VS command prompt and look at the
various command-line options for devenv.exe. I think the one I used was
devenv /reset or devenv /resetusersettings.

HTH,

Mike Rodriguez

 

[BuddyWork]

Hello Michael,

Thank you for the quick reply, I've tried both options and they errored
with 'Invalid Command Line. Unknown switch: reset' and 'Invalid
Command Line. Unknown switch: resetusersettings'

 

[Michael Rodriguez]

Hello Michael,

Thank you for the quick reply, I've tried both options and they errored
with 'Invalid Command Line. Unknown switch: reset' and 'Invalid
Command Line. Unknown switch: resetusersettings'

That switch must be new to Whidbey. Try deleting all of your local VS
settings manually. I believe the folder is C:\Documents and
Settings\MYUSERNAME\Application Data\Microsoft\VisualStudio\7.1.

HTH,

Mike Rodriguez

 

[BuddyWork]

Thanks for the reply, tried it but no luck, I've noticed that when
building the macros nothing appears on the output window. Any clue why?

 

[Michael Rodriguez]

Thanks for the reply, tried it but no luck, I've noticed that when
building the macros nothing appears on the output window. Any clue why?

No clue, unfortunately. It's got to be in your user settings somewhere. I
would try uninstalling, deleting all VS registry entries (and any user
directories), then re-installing.

 

[BuddyWork]

Found the solution, contacted Microsoft and they said by reinstalling
the Framework will solve the problem, and it did.