Unable to attach remote debugger after Visual Studio 2015 Update 2

As the title states: I was unable to attach the remote debugger (for instance to an Azure Web App) after installing Visual Studio 2015 Update 2. I got an error with something about invalid memory access or something like that.

The solution is simple: install Remote Tools for Visual Studio 2015 Update 2. Go to the webite, pick your machine’s architecture (the x86 install won’t run on a x64 machine) and click download. After installing, you’re good to go!

Hope this helps.

PS: There’s a list of Related releases on the Visual Studio 2015 Update 2 page. Have a look, it’s helpful ;)

Unable to find specific NuGet packages after update

After updating Visual Studio 2015 (there was an update for GitHub Extensions, one for the NuGet Package Manager and, of course, there was Visual Studio 2015 Update 2) I tried to add the WindowsAzure.Storage NuGet package to a project I started about a month ago. I opened NuGet Package Manager, went to the Browse tab and typed WindowsAzure.Storage. The result: No Packages Found. OK, so then I’ll just….

Wait… WHAT?

No Packages Found

After doing all sorts of things, including looking for other NuGet packages with the same result, I found what the issue seemed to be: the Package Sources weren’t up to par, since the Official feed had vannished. I fixed them to look like this:

NuGet Package Sources

And then set the’Package source’ to be ‘All’ in the upper right corner of the NuGet Package Manager. Fixed it for me!

Hope this helps.

 

Running Visual Studio as an administrator causes ‘Save changes to devenv.sln’ when double clicking solutions

After making sure my Visual Studio always ran as an administrator by following my own post HowTo: Have Visual Studio always run as administrator on Windows 8, I got a message if I wanted to save changes to devenv.sln each and every time I double clicked a Solution. Since the problem kept occuring after installing Visual Studio 2015 CTP6, I wanted to solve it. So here we go!

Double clicking a Solution file doesn’t start devenv.exe (which is set to be run as an administrator) but will cause the Microsoft Visual Studio Version Selector (VSLauncher.exe) to be run. This tool selects the right version of Visual Studio to open the Solution. Because VSLauncher.exe is not being run as an administrator, the error occurs.

The Solution

Find VSLauncher.exe, which is typically located at ‘C:\Program Files (x86)\Common Files\Microsoft Shared\MSEnv’ and make sure it runs as an administrator too. This will cause the Version Selector to be started with the correct privileges, helping it start devenv.exe with the right privileges. Problem solved ;)

Hope this helps