It has been a busy two days here at Build 2015 in San Francisco. Lots of announcements by Microsoft overall, and lots of great stuff for developers (across all platforms). Oh, and if you didn’t feel a little giddy after seeing the HoloLens demo,
What an amazing day. Today we announced the release candidate to Visual Studio 2015..and it has a ton of new features.
If you haven’t already seen the news make sure and check out the following resources:
Introducing Visual Studio Code, Visual Studio 2015 RC,
Today Soma announced the Release Candidate of Visual Studio 2015. It adds two useful improvements to the Code Maps feature, which can make it easier to create better designs and architectures for your applications. The first improvement is in the way that code maps display and interpret test assets within solutions.
On April 17, 2015, we announced the General Availability of CodeLens in Visual Studio Online. However, the biggest news by far is that, in addition to Visual Studio Enterprise, CodeLens is now available in Visual Studio Professional 2015.
This is one of the top requests we’ve had from customers.
Since our initial launch of the Visual Studio Emulator for Android, we’ve worked quickly to deliver on top feature requests, adding in support for hot-ticket items such as OpenGL ES 2.0, Lollipop, multi-touch, and advanced camera simulation. Today we’re announcing two more features to help you debug and test your Android apps on our fast,
In this blog post I am going to walk you through fixing a bug using IntelliTrace in Visual Studio 2015. If you haven’t done so already, check out the announcement of IntelliTrace in Visual Studio 2015 which gives you an overview of IntelliTrace and its UI.
Memory Usage tool in the Diagnostics Tool window
In Visual Studio 2015 CTP 6 we introduced the new debugger-integrated diagnostics tools, including the Memory Usage tool. For the first time, you could investigate memory growth on the managed heap without leaving everyone’s favorite tool,
By now you have hopefully heard that in Visual Studio 2015 we are introducing a new Breakpoint configuration experience. It features a Breakpoint Settings peek window that allows you to easily configure Conditions and Actions for a breakpoint by specifying a Conditional Expression,
Hopefully you saw our previous post covering newly supported edit types added in our previous CTP of Visual Studio 2015 (if not, I’d recommend looking at that post first). Now, we are pleased to announce that Visual Studio 2015 RC contains even further Edit and Continue (Enc) improvements when debugging .NET applications.
One of the most useful features of the Visual Studio debugger is Edit and Continue (EnC), which works for both managed and native code (where native admittedly had some significant limitations in previous versions of Visual Studio through 2013). In this post I want to share some changes to EnC for C++ developers with Visual Studio RC,