Hi Dave,
You are welcome and glad it helped.
FYI, I need the extra script debug info from time to time while I'm testing my applications, so I keep two BAT files handy for each version of Visual Studio (VS2008 and VS2010) and turn this debug info on and off as required. It's a simple registry change, and on Win7 64bit, these are the commands I use:
- VS2008 turn debug ON: C:\windows\syswow64\cmd.exe /k "reg add HKLM\SOFTWARE\Microsoft\VisualStudio\9.0\AD7Metrics\Engine\{F200A7E7-DEA5-11D0-B854-00A0244A1DE2} /v ProgramProvider /d {170EC3FC-4E80-40AB-A85A-55900C7C70DE} /f"
- VS2008 turn debug OFF: C:\windows\syswow64\cmd.exe /k "reg add HKLM\SOFTWARE\Microsoft\VisualStudio\9.0\AD7Metrics\Engine\{F200A7E7-DEA5-11D0-B854-00A0244A1DE2} /v ProgramProvider /d {4FF9DEF4-8922-4D02-9379-3FFA64D1D639} /f"
- VS2010 turn debug ON: C:\windows\syswow64\cmd.exe /k "reg add HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\AD7Metrics\Engine\{F200A7E7-DEA5-11D0-B854-00A0244A1DE2} /v ProgramProvider /d {170EC3FC-4E80-40AB-A85A-55900C7C70DE} /f"
- VS2010 turn debug OFF: C:\windows\syswow64\cmd.exe /k "reg add HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\AD7Metrics\Engine\{F200A7E7-DEA5-11D0-B854-00A0244A1DE2} /v ProgramProvider /d {4FF9DEF4-8922-4D02-9379-3FFA64D1D639} /f"
You will need to run each command as an administrator, and you will have to close down VS and open again for it to be effective.
Be warned, those are registry changes, so please make sure the command lines appear on this post as they should, with no vital characters removed, by comparing with the articles I referenced before.... should you decide to use them.
For me, they do their job perfectly and as they should.
Palli