Microsoft ASP.NET and Web Tools

Microsoft Free

Provides Preview 1 tooling for Microsoft .NET Core 1.0.0 RC2

Microsoft
(31) Review
Visual Studio
2015
Download (240,985)
5/18/2016
14.1.20512.0
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (31)
Q and A (12)
Sign in to write a review
Sort by:

by Almir Vuk | Sun 11:14 AM

Happy about this tool!

by barrytang | Wed 10:52 PM

On William Bosacker's issue, like he said, we got to the bottom of it. It turned out webpages:Version is set to 4.0.0.0 instead of 3.0.0.0 in web.config. We also filed a bug to make sure we give the proper error message when the wrong version of webpages:Version is in web.config. More details on https://github.com/aspnet/Tooling/issues/390#issuecomment-216945279

For other instances of "Operation could not be completed" or can't open cshtml files, so far deleting the VS MEF cache resolved the issue. You can do so by deleting %userprofile%\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache and restart VS. The VS MEF cache corruption issue is actively being investigated by the VS MEF team and some fixes have been made to VS2015 Update 2 already.

As for the debugging issue, if it doesn't get addressed by deleting the MEF cache, please file a bug via https://connect.microsoft.com/visualstudio.

Thanks!
Barry

by cafalier | May 16 2016

before setup this, close your antivirus

by William Bosacker | May 03 2016

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 "3.0.0.0", 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.

by 逐梦诛仙_ | April 26 2016

run the exe with visual studio closing

by Jukka Hyvärinen | April 10 2016

Got the "Operation could not be completed" error after installing the latest version. RedByron's suggestion to delete MEF files helped though.

by mitras | April 07 2016

by ArgeKumandan | April 04 2016

i've installed the update and it works fine on vs 2015 update 2. Haven't seen the problems others mentioned

by Abdelkrim BOUJRAF | March 15 2016

opening *.cshtml files generate the "object reference not set to an instance of an object"

by Humaira Syed | March 10 2016

by RedByron | March 08 2016

I confirm that clearing The MEF cache at:
%userprofile%\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
fixed the issue

by kor_molayo | March 03 2016

이거 깔고 이상해졌어요.

by giraffeboy | February 22 2016

Works perfectly for VS2015 Pro MSDN Edition. Installer takes a long time though.

by tsw | February 18 2016

I was in the same situation as Josh Horner, unable to uninstall this.

I actually ended up having to rebuild my workstation, and reinstall Visual Studio 2015 to get rid of this.. which was, totally beyond acceptable.

by Joshua Horner | February 18 2016

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.)

by ncilmsdn | February 18 2016

I have four updates here and everyone of the reviews on them says to ... run for the hills ... is no one checking these anymore?

by Petra Liljecrantz (private) | February 15 2016

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.

by Aown Muhammad | February 12 2016

by Eugene Lishnevsky | February 12 2016

No problems whatsoever.

by Mads Kristensen | February 11 2016

1 - 20 of 31 Items   
Sign in to start a discussion


  • Fantastic
    4 Posts | Last post Sun 10:59 AM
    • I love web forms!
    • what about mvc?and show your reason?
    • Mvc doesn't have the fantastic world of the "event handler", "autopostback" and "binding". Every time you have to do something with mvc you have to write some cryptic javascript and lose a lot of debug time.
      
      mvc files: controller / js (every time a lot) / css / cshtml / viewmodel + (business + model)
      
      webform files: aspx + (code behind) / css + .. some time a little js + (business + model)
      
      - 5 files to switch to write vs 3,5 file
      - a lot of js to eventhandler/binding etc...
      
      
      Webforms optimized (asp:linkbutton + asp:ddl + asp:repeater + asp:button + viewstatemode=disabled + autoeventwireup=disabled + ashx) vs mvc = (development time) 1 : 100
    • @Bertsoft I'm sorry but you're way wrong,,,
      I'd the honor of working on ASP.NET WEB FORMS and MVC with entity framework, not only that I also had worked on CLASSIC ASP and my opinion is web development has never been easier with MVC...
      Actually I don't write any java script more than what I usually did with web forms, Of course there are new libraries and framework but hey that's evolution after all...
      FINALLY: I'm really sorry for my bad English,,, see English is not my first language...
  • Uninstall
    2 Posts | Last post Fri 7:22 PM
    • After installing that "update" I can't develop on my ASP5-project any longer. I get thousands of errors.
      What can I do to revert the update?
    • RC2 is essentially the move from DNX (ASP.NET 5) to .NET Core and ASP.NET Core.
      
      I'd suggest taking a look at https://github.com/aspnet/Home/issues and maybe posting questions there
  • Setup failed
    3 Posts | Last post Fri 6:30 PM
    • I try to install Core 1.0.0 RC 2 Tooling Preview 1. I have the latest Visual Studio Entreprise 14.0.25029.00 Update 2 RC.
      Setup failed - this product requires Visual Studio 2015 Update 2 or later. Help needed...
    • @domenichH. This update requires the RTM version of Visual Studio 2015 Update 2. The version for that is 14.0.25123.00
    • Apologies @Paul_DK, the reply was intended for you.
  • Changelong Link Request
    7 Posts | Last post Wed 10:58 PM
    • 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.
    • Thumbs up for this, still struggling to find the changelog... it should be very easy to see it.
    • Hi
      
      You can find more details about the changes in RC1 at http://blogs.msdn.com/b/webdev/archive/2015/11/18/announcing-asp-net-5-release-candidate-1.aspx
    • 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.
    • haha,but microsoft still didn`t consider this feature.we all are confused!
    • We now added a link like you suggested. Thanks for your feedback!
  • Is this also for VS2013?
    2 Posts | Last post April 15, 2016
    • 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.
      
      Thank you!
    • this update`s description indicate that it support vs2015 version.
  • Uninstalling ASP.NET
    2 Posts | Last post April 15, 2016
    • 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. 
    • uninstalling visual studio  always to be an confused work!
  • this update doesnot work !
    1 Posts | Last post April 15, 2016
    • 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?
  • What are the changes in the latest version?
    4 Posts | Last post February 06, 2016
    • Could you please update the description with a changelog?
    • agreed!
    • I have blogged about the details of the update at http://blogs.msdn.com/b/webdevtools/archive/2012/07/12/visual-studio-2012-rc-web-tooling-extensions-update.aspx.
    • 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. 
      Thanks
      http://www.fixithere.net/sky-customer-service/
  • Page Inspector?
    2 Posts | Last post December 15, 2015
    • This update stated that the Page Inspector was going to be added, but I can't find out how to get access to it...  Where is the Page Inspector?
    • I installed this for the page inspector and can not see it anywhere. My developers keep moaning about it being missing from VS2015 and I thought it was finally getting added.
  • Previous versions of tools?
    3 Posts | Last post December 15, 2015
    • 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. 
1 - 10 of 12 Items