Thanks all for the positivity! It's so encouraging!
@Amy: Thanks and sorry about not including more! I didn't mean for the description to be misleading! A few things actually got into 15.8 that I wasn't sure would. So, the "preview" features just became the 15.8 features. XD
@Doctor Who: If you have any more issues you can check what shortcut it is set to in Tools > Options > Environment > Keyboard. In the search box that says "Show commands containing" search for "caret". That will list the commands and shortcuts they are set to.
@dvded: You should be able to debug any selected tests through either the Live Unit Testing glyphs, the right-click menu, or through the Test Explorer without needing to stop Live Unit Testing at all. You certainly should not need to restart Visual Studio. Would you mind filing a bug on developer community? A repro solution or steps would be very helpful!
The StackTrace that appears when hovering over the Live Unit Testing glyph doesn't list line numbers, but if you wanted to investigate a test, you can view the results in the test explorer where the StackTrace is actually an active link to the line of code it lists. If you wanted to know the line number without navigating there you can hover over the link.
@Bleak Morn: Yes, that's the one! Though, your link was broken for me. The whole series really gets you on the right track for TDD. If you want further reading they mention a few books that go more in depth. As to asking if there is more recent content, in my own opinion, I appreciate content that captures the basics and gives good advice while avoiding the many industry fads in this area. Is there some crucial content you feel is missing? I'd love to hear it!
@LarsH: You can check your Nuget Package Manager in Visual Studio to see what you have installed. The MStest.TestAdapter and MSTest v2 nuget packages have the latest performance improvements and I recommend using them. You might still have the old MSTest adapter extension installed instead of nuget packages. I'd also recommend using the nuget packages instead of the older extension for better performance. (We recommend moving off the older .NET test adapter extensions if you are still using them due to performance gains you can get with using the nuget package test adapters instead. Read more.)
@LarsH: We won't auto-update the nuget references in someone's project to the latest when they update Visual Studio. You can imagine, that could cause issues for people who may not always be able to update to the latest because they rely functionality that may have changed in recent versions.
You can look up the current version of your MSTest.TestAdapter in a few places: in your csproj, the Nuget Package Manager for Solution, or you can double-click on your reference under the "References" node in the Solution Explorer which opens it in the Object Browser.
@daveparvin: If you'd like to email me about what pains you are running into and your scenario I'd be happy to learn and share them with Kathleen Dollard. My email is kehavens @ microsoft. com (without the spaces.) I know a lot of asks are catalogued on developer community or user voice to improve VB support, but sometimes it helps to share the whole picture of what is getting in the way of your day-to-day development. Please reach out if you are interested!