Comment you're replying to
Your name *
Your email *
Your comment *
Please type these numbers *
There was an error submitting your comment, sorry..
If you’re like me you will have a development machine that’s got a bit of power behind it. You might also be a bit keen on new technology. You may have even gone ahead and installed Windows Vista thinking – she’ll be right.
If you’re still like me at this point you’ll be thinking “bugger”.
Visual Studio.NET 2003 is not supported on Vista = but it does work for the most part. The big issue is web development.
What has worked for me, and may well work for you, is installing Windows XP on Virtual PC 2007 (free). I put my web sites on the XP VPC and I can still run the IDE on Vista. While this is a little clunky everything seems to work pretty well.
Then one day… bang! The debugger refused to attach.
Checking the event logs I found a very unhelpful Event ID 10023:
“The application-specific access security descriptor for the COM Server application C:Program FilesCommon FilesMicrosoft SharedVS7Debugmdm.exe is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. The application set this security permission programmatically; to modify this security permission contact the application vendor.”
I have no idea what happened from one minute to the next but it was properly busted. I tried a million things including every known remote debugging setup check. I even reinstalled VS.NET 2003 & VS2005. The thing that eventually did the trick was:
I suspect there was another issue, and in trying to solve it I had added domain accounts to the DCOM config of Machine Debug Manager in “Access Permissions”. Further testing has revealed that this is what has killed it. If you are having this problem now you know why For some reason simply removing the offending accounts doesn’t help you have to perform the steps above.