Hey, anyone who's familiar with the visual studio 2008 testing framework and wants to help me solve a problem / check out what I posted on StackOverflow:
« Sweet | Main | Notes on *Portal* and *Mirror's Edge* »
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.



I just posted the same comment over at stackoverflow, but I thought I'd post it here.
You probably have already done this: my initial thought is that perhaps one of the properties on that file might be different. Verify that all the properties are identical to the other files in the project.
Posted by: Jay Kint | April 09, 2009 at 12:55 PM
I have replied. I think something's corrupted a dll somewhere.
On a totally unrelated note, how do you like mstest? I've not used it much but I don't see any reason to use it over nunit. Your thoughts?
Posted by: Jeff Ward | April 10, 2009 at 08:27 AM
Except for this problem I'm having, I like it - I wasn't sure how to go about putting unmanaged code under test with nunit, and this was mostly easy. But the killer app is the "Debug Test" option.
Posted by: Jamie Fristrom | April 10, 2009 at 12:53 PM