I would like to echo the sentiments of the previous commenters. DO NOT INSTALL! At least not if you would like to build/debug ASP.NET applications. I have no idea why this ever made it to the RC stage, nor why it is proposed as an update by Visual Studio 2015.
FOR SURE DO NOT INSTALL. I'm also having this issue after installing Update 1 RC 1 but follow instructions of PilotC150 at "github.com/aspnet/Tooling/issues/390" everything appears to be working. (note: I installed (from CD) ASP.NET and Web Tools package again) 8) well in time (life is not easy) I removed/installed VS 2015 Enterprise for no more problems. :D
There is something wrong with this release candidate (not sure why it is being automatically installed by Azure tools or by the Extensions & Updates section in VS2013/2015). After numerous tests (uninstalls, reinstalls, and a full system restoration), I have determined that this was the culprit causing the Browser Link function to not work in VS2013 & VS2015 (and possibly causing VS to crash when adding service references). I had to uninstall the ASP.NET and Web Tools for both of them from Programs and Features (Add/Remove Programs), and then use the installation media to reinstall the original web tools to get it fully functioning again.
This update is not working. It appears to fail trying to download DnxNetFx-v1-rc1-x64_rc1.msi from https://go.microsoft.com/fwlink/?LinkId=708525 (that fails on direct downloads, too) BTW, it does manage to download v1.0.11123.0\DotNetVersionManager-x64_rc1.msi from https://go.microsoft.com/fwlink/?LinkId=708515, so it's not a connectivity thing: the file just appears to not be available.
This was updated again today, and I would like to request (as they did in previous comments from 2012) that at least a link to the changelog (blog or whatever) be put in the description. That is much easier than having to come to click the Q and A or Reviews tab and copy and paste a URL into the address bar of my browser.
The more you make your potential user do to get the info they need, the less likely they are to use your product.
You do realize that your reply was the exact opposite of what we asked for, correct? Why is it so hard to put that URL in a link on the description? You can obviously link stuff there as there is a link to a KB article dealing with addressed security issues. That's cool and all, but is that all this update addresses? I ask because one of the comments on the reviews tab says this update breaks CSHTML editing. Well... That and there is no change log link in the description (like we keep asking for). finally, a blog != change log.
Here is the break down of what is being requested.
1. Create a clickable link to the changelog.
2. Place it in the Description tab
3. If the change log has been classified by the US government as Top Secret, then at least a clickable link to leading to the page discussing the latest changes. The markup link might look like this: <a href='http://blogs.msdn.com/b/webdev/archive/2016/02/09/bloginsteadofachangelog.aspx'>Learn more...</a>
I apologize for ranting, but your reply almost feels deliberately disrespectful considering my original post.
And now, you have this still being the RC1. I am petrified trying to use this update less it cause all the same problems it did before the update was released? Why is the RC1 not a RTM? I lost a total of two days trying to repair VS2015 from this debacle.
Where are previous versions of the tools? The current update (11/30/2015) is crashing VS2015 and causing severe slowdown of VS2015 (constantly getting not responding). I uninstalled this update only to discover that the web tools is uninstalled as well and VS2015 now crashing upon entry into my projects. The RC1 has serious flaws in it and I get back to the previous state of VS2015 before the update.
Sorry to hear about that. Have you looked at the activity log of VS to see why it's crashing? If you launch VS from the commandline, e.g. devenv.exe /log, it should create a file called ActivityLog.xml in your roaming profile, %userprofile%\appdata\roaming\Microsoft\VisualStudio\14.0.
If you want to return to the version of Web Tools that shipped with VS 2015 RTM, you can just repair VS. In Add/Remove Programs, right click on the Visual Studio 2015 entry, select change and then modify and select the Web Tools option
That didn't work very well and was not intuitive. If you can uninstall through control panel, it should be following your (MS) rules for roll backs of installations.
Also, this update caused crashes to VS2015 when editing HTML files.
And now, you have this still being the RC1. I am petrified trying to use this update less it cause all the same problems it did before the update was released? Why is the RC1 not a RTM? I lost a total of two days trying to repair VS2015 from this debacle. This roll out was not smooth at all and the actual repair was not clear or intuitive.