Tuesday, 22 July 2008

MS Test is hurting

Normally I try not 'me-too' post but I had to link to this. A friend of mine has just written an interesting post about how difficult he finds MS Test. Mentioning this to a colleague resulted in a link to Jeff Atwood's Coding Horror 'Why Can't Microsoft Ship Open Source Software?' post basically going further and trying to understand the reasons behind this.

I'm actually fed up with littering my tests with [DeploymentItem] attributes, having to hack around virtually opaque XML files, and bending over to assume the god forsaken position that MS Test wants me in. Yes I've tried to get change implemented - but some arguments I lose and some I win!!!

Sorry - rant over.

Tuesday, 1 July 2008

Access Denied Error when attaching to process

I've had this problem the that I've been trying to solve over the last few days and its stopped me from debugging into services (remoting and WCF) in other processes. Every time I went into (in VS2K8)  Tools|Attach to Process, and I selected a one of our processes, I got an Access Denied error. There was nothing in the event log, so I really didn't know what to try - except perhaps to reinstall VS, which hasn't worked.

The solution is actually very mundane and is related to the fact the I was attempting, not to do managed code debugging, but something called 'workflow debugging'. I'm not sure what this is but VS tells me it incompatible with managed debugging. I suspect that its TFS related and I was basically attempting to attach the wrong kind of debugger, and since I'm no longer a TFS admin, I suspect this is why I'm getting access denied messages.

To fix this all I had to do was to specify the correct debugger in the attach dialog, by clicking on the Select button and and changing the debugger type.

Before:

attach

After:

debugger

debugger