More Visual Studio pain

I conceded to use VSTS testing instead of NUnit in order to enjoy the tests running under the ASP.NET runtime, but now I can't debug. This page describes how you should be doing it, but it doesn't work. First of all, it wasn't obvious (and why would it be?) that running tests with debug didn't actually work. If it's not going to work, then why the hell would you not tell the user this?

In fact, the first time I did this, VS spawned two WebDev server instances, then a third where the tests were actually run. The other two remained active when the tests ended. The one that appeared then disappeared was for the Web project (file-based with testing code), while the second one pointed the same place, and the third pointed to the production Web project (also file-based). Needless to say, it's the one that appeared then disappeared that you have to attach to, as that's the one that is acting as the environment for the tests.

Why is it that with every step forward, we take a step back?

1 Comment

  • We have received customer feedback surrounding this issue and do plan on improving the experience significantly with vNext.

    Let us know if the updated article helps and if you have more feedback.

    Sonal Pardeshi, Product Manager, Microsoft

Comments have been disabled for this content.