We’ve heard your feedback that you want the Visual Studio debugger to support child process debugging. Child process debugging means that when the application you are debugging creates another process, Visual Studio will detect this and automatically attach a debugger to the newly created process as well.
If you are using Visual Studio Fakes in your Unit Testing, and you created your test project from any of the below versions of Visual Studio, then if you upgrade to Visual Studio 2013 Update 4, you may start hitting build errors around Microsoft.QualityTools.Testing.Fakes.dll.
[Editor’s note: “Smart Unit Tests” has been renamed to “IntelliTest” with effect from Visual Studio 2015 Release Candidate (RC).]
If you have not already seen the brief video on the Smart Unit Tests feature, I urge you to do so; this feature can help you overcome any inertia in getting started writing unit tests.
While the earlier blog on DevOps style deployment capability touched upon the scenarios for an individual developer, in this blog let’s look at how this experience can be extended to team. You would also want to refer Announcing DevOps style deployments using Visual Studio 2015 Preview and Azure and Brian Keller’s Channel9 Video first.
By now you must be aware about the DevOps style deployment capability that was announced in Visual Studio 2015 preview. If not already, you would want to refer the announcement blog; Announcing DevOps style deployments using Visual Studio 2015 Preview and Azure.
This blog is an introduction to how users can execute Selenium tests using Cloud-based Load Testing from Visual Studio Online.
Let’s get familiar with Cloud-based Load Testing (CLT) from Visual Studio Online (VSO) and Selenium.
Cloud-base Load Testing:
A good introduction to CLT with VSO and key feature can be found here –
Ask a room of developers what is the first concept that they think of when they think about debugging and most of them will say: breakpoints. That is why with Visual Studio 2015 we significantly improved the ability to configure breakpoints with conditions and actions.
29 April, 2015: Updated for the release of Visual Studio 2015 RC
In Visual Studio 2013 we introduced the Memory Usage tool as part of the Performance and Diagnostics hub. This tool, like the rest of the profiling tools in the Performance and Diagnostics hub,
Update: Added a troubleshooting section.
CodeLens is a heads-up display in your Visual Studio Editor where you can find information about your code in-context.
CodeLens has now been enabled in Visual Studio Online for select customers as a Limited CTP.
Last couple of weeks have been pretty crazy; in addition to the launching the new browser based Load Test Authoring experience at TechEd Europe, hosting the MVP summit, getting Update 4 released we have been working on getting Visual Studio 2015 Preview ready for you.