This is now working, under the following conditions (there are plenty of bugs in it):
1. Update VS2015 to the latest version (Update 2 as of this post). 2. Update the Azure SDK to the latest version, if installed. (2.9 as of this post) 3. Update all of your VS addons to the latest, especially those from Mads. 4. In MVC 5 or earlier projects, ensure that the "webpages:Version" appSetting is set to "126.96.36.199", or completely remove it and the "webpages:Enabled" setting.
If you have done all of the above, then you should be able to work with .cshtml views.
if you have same issue like William Bosacker. I have offer for you; 1 - Download IObit Uninstaller as free 2 - Find Microsoft ASP.NET and Web Tools Update 1 and uninstall it 3 - Open vs2015 setup exe click modify then select Microsoft Web Developer Tools under Microsoft and Web Development click update Your issue must be fix. Don't update Microsoft ASP.NET and Web Tools İ'm sorry my English
I am in the same boat as William Bosacker. I cannot open or edit any .cshtml files in VS 2015 Community Edition after the ASP.NET 5 RC1 Update 1 installation. I also am 100% unable to UNINSTALL the update in any way. (AND, there are two of them listed in control panel's uninstall list; neither work.)
Couldn´t debug after the install. Uninstalled the update then Visual Studio said my project was incompatible with this version of Visual Studio, only an uninstall of VS and then reinstall made everything working again.
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.
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.
I concur with @Opus The Krokus for the same reasons he outlined in his Feb 09, 2016 comment. I would *really* like to know what was added or modified before applying any updates.
- Thank you for your support, I home the team will strongly consider this feature.
Is this for 2013 as well? All quests for ASP.NET and Web Tools 2013 point here? If not where is the 2013 version? I am having issues with Page Inspector and Browser Link (posted in the Visual Studio set up & installation forum) and am hoping to find a fix.
I am trying to uninstall Visual Studio 2015 and since there are a lot of components to uninstall separately i started off at the top of the list in the program manager. Now when i came to Microsoft ASP.NET RC1 update 1 i get a error message saying "The user account already exists". I have tried to restart the computer, still same message. I've tried a with a clean start up, same thing.
when i installed this update ,there is no difference between eariler in the code of ManageController.cs of the action RemovePhoneNumber().it is still no [HttpPost] and [ValidateAntiForgeryToken] Attribute for this action! who can tell me why?
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.