Microsoft ASP.NET and Web Tools

Microsoft Free

Provides web tooling updates for ASP.NET as well as Preview 2 tooling for Microsoft .NET Core 1.0.0

(60) Review
Visual Studio
Download (316,843)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (60)
Q and A (22)
Sign in to write a review
Sort by:

by Philip Holly | August 18 2016

Installed fine for me.
Edit: Make sure you're not running Kestrel server in the background or else actions like Add Controller will not work.

by John B. (Pittsburgh) | August 16 2016

by Demented Devil | August 16 2016

So far so good - installed on three different machines without any problem...

by aserraric | August 16 2016

As buggy as the 2.0.0 version.
After installation, MVC5 projects no longer build.

by Li Key | August 16 2016

Installation Completed Successfully.

Thank you, really like the 2015/Core changes to date.

by dinotom | August 11 2016

So everyone is clear, you install with this command line FROM THE DIRECTORY YOU DOWNLOADED THE FILE TO. DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1

by AndrewTatham | August 09 2016

requires SKIP_VSU_CHECK=1 to install

Whoever is responsible should be made to do the walk of shame.

by Ricardo Brea | August 09 2016

Poor testing, tools of this importance must be tested more. Please improve your testing procedures. Thanks

by Frank Loizzi | August 07 2016

This is one more defective update for a Visual Studio 2015 component. I'm very thankful because Visual Studio 2015 Community is free but I'm not sure why in the last month so many extension updates with installation bugs were released? This extension update is not the only one with problems of this kind.

by Trent Apple | August 04 2016

Thank you for figuring that out. I recommend that the author of this extension add a note regarding "setup failure message" because I guarantee I am not the only developer who has wasted time repairing their Visual Studio to no avail.

Make sure Visual Studio instances are closed and run the following:

DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1

by Tortuga Design Inc_ | August 02 2016

I'm glad someone figured that out.

Welcome to Yet -another flaming bag of sh&$ from Microsoft.

I've only been at it 6 hours or so now, but hey...What do you expect from a company run by kids?

by stinkyjak | August 01 2016

Thanks for the help Elger.

Run the installer from the command line like this:

DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1

by SaranGraviton | August 01 2016

Always show

"Setup has detected that Visual Studio 2015 Update 3 may not be completely installed. Please repair Visual Studio 2015 Update 3, then install this product again."

I successfully update VS2015 U3 without error but still can't install this update.

by Andre P L | July 30 2016

Elger, thanks for the work around, that worked.

by Baldsh | July 29 2016

Same as everyone else, this "update" does not install, repairing does squat.

by Elger Mensonides | July 29 2016

Workaround for the setup failed problem:

Run the installer from the command line like this:

DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1

And it will install.

by Jerzy Doskocz (pen_2) | July 29 2016

As most of ppl here...setup failed. Good thing is that after seeing these comments I don't have to even bother and try to repair VS.

by Saluda | July 28 2016

Work many hours trying to get this update to work. Attempted to install update on three different machines with no luck. Ran the SKIP_VSU_CHECK=1 to get it installed on my Surface. Will wait for the next update for my Desktop and Work laptop.

by kishore1 | July 28 2016

Very bad experience. I have to retry repairs more than 4 times with out any result.I couldnt able to update VS2015 which has update 3 version.

by Jamie_D_ | July 27 2016

I'm just seriously confused right now. I mean, I read some of the reviews and it just seems that the qc is just not up to any standards. So avoid the updates that cause problems and the ones I do install work great. Until now. Can't even install and looks like I'm not the only one.

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

  • What changed with August release
    4 Posts | Last post August 18, 2016
    • It seems that on August 15th, a new version was released. (The previous version was 14.1.20624.0, released in June, but now it's 14.1.20810.0.) As I write this there isn't any description of what changed.
    • Looks like a minor version bump - presumably to resolve installer related issues some folk had with the previous build.
    • The June release was Preview 1, the August 15th release is Preview 2.
    • Actually, this time, they have a release note.
      I think it will be greate if they provide a link in the Description page.
  • What did /layout do?
    1 Posts | Last post August 09, 2016
    • I run the installer with /layout. I downloaded stuff for a while. But now, where are they? I assumed they must be right besides the exe file. But they aren't.
  • Install fails to detect VS 2015 Update 3
    20 Posts | Last post August 08, 2016
    • Installation is be blocked because the install is not properly detecting that I have VS 2015 Update 3.  Anyone getting this or can help I would appreciate it.
      Version of VS 2015: 14.0.25421.03 Update 3
      Logs from install:
      [2010:160C][2016-06-30T09:13:15]i052: Condition 'WixBundleInstalled OR NOT(NetFx45Release < 378675) OR (WixBundleAction=2)' evaluates to true.
      [2010:160C][2016-06-30T09:13:15]i052: Condition 'WixBundleInstalled OR VS2015DevEnvExists OR VS2015WebExpressExists OR (WixBundleAction=2)' evaluates to true.
      [2010:160C][2016-06-30T09:13:15]i052: Condition 'WixBundleInstalled OR (((VS2015CommunityUpdateVersion >= v14.0.25420) OR (VS2015ProfessionalUpdateVersion >= v14.0.25420) OR (VS2015EnterpriseUpdateVersion >= v14.0.25420)) OR (VS2015WebExpressUpdateVersion >= v14.0.25420)) OR (SKIP_VSU_CHECK=1) OR (WixBundleAction=2)' evaluates to false.
      [2010:160C][2016-06-30T09:13:15]e000: This product requires Visual Studio 2015 Update 3 or later. Please install Visual Studio 2015 Update 3 or later, then install this product again.
      [2010:160C][2016-06-30T09:13:15]e000: Error 0x81f40001: Bundle condition evaluated to false: WixBundleInstalled OR (((VS2015CommunityUpdateVersion >= v14.0.25420) OR (VS2015ProfessionalUpdateVersion >= v14.0.25420) OR (VS2015EnterpriseUpdateVersion >= v14.0.25420)) OR (VS2015WebExpressUpdateVersion >= v14.0.25420)) OR (SKIP_VSU_CHECK=1) OR (WixBundleAction=2)
      [2010:160C][2016-06-30T09:13:15]i199: Detect complete, result: 0x0
    • I got the exact same thing.  Waiting for the VS 2015 update first now.
    • @schardag/@YsFred4, this is a known issue with Visual Studio Update 3. The issue is that the underlying feed that drives the update is not being updated. Other customers who reported the same issue said that the feed got updated eventually but might take several trials. Our setup team is looking into this and I am following up to see when they will have the issue fixed and whether there is a workaround.
    • Here is a workaround that worked for some users - Go to a command prompt and type ipconfig /flushdns then reboot.
    • I have installed update 3 but I'm still getting this error. Log file says VS2015CommunityUpdateVersion is 14.0.25123 but help window says Visual Studio 2015 with Update 3.
    • I too receive this. ipconfig work around didn't work.
    • Check this thread
      TL-DR: install it by running with SKIP_VSU_CHECK parameter
      DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1
    • Excelent solution Zeratul Works fine.
    • Zeratul's solution worked for me as well. 
    • Yes...solution is working for me too
    • Thanks Zeratul!! Your solution worked for me too! 
      I thought I was doing something wrong, but when the same thing happens in two completely separate environments I figured there was something wrong!
    • Same here. Thanks Zeratul :)
    • You're the man, Zuratul.
    • Same here. Thanks Zeratul :)
    • Same here!
      apparently this condition fails:
      OR NOT(
          (VS2015CommunityUpdateVersion <> VS2015UpdateVersion) 
          AND (VS2015CommunityExists) 
          AND (VS2015UpdateVersionExists)
        OR (
          (VS2015ProfessionalUpdateVersion <> VS2015UpdateVersion) 
          AND (VS2015ProfessionalExists) 
          AND (VS2015UpdateVersionExists)
        OR (
          (VS2015EnterpriseUpdateVersion <> VS2015UpdateVersion) 
          AND (VS2015EnterpriseExists) 
          AND (VS2015UpdateVersionExists)
        OR (
          (VS2015WebExpressUpdateVersion <> VS2015UpdateVersion) 
          AND (VS2015WebExpressExists) 
          AND (VS2015UpdateVersionExists))
      OR (SKIP_VSU_CHECK=1) 
      OR (WixBundleAction=2)' evaluates to false.
      Dunno if related but i installed an update to the WIX Toolset before i tried the update...
    • Thanks, Zeratul. :)
    • Help me, I am a beginner, i would like who anyone explain  me, step by step, how I do the solution of Zeratul. Thanks!
    • See the discussion here:
      The solution, as @BadEnuf mentioned, is to run the installer with the command line argument (setup directive) SKIP_VSU_CHECK=1
      So just open a command prompt (or PowerShell prompt) in the directory where you downloaded the file and type DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1 (for PowerShell write .\DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1)
    • Hi ApoFelipe, for a step by step follow below
      Rather than running the update, you have the option to download the App (DotNetCore.1.0.0-VS2015Tools.Preview2.exe) onto your hard drive.
      Step 1: Dowload the App onto your C: Drive.
      Step 2: Open the Command Prompt with Admin priviledges.
      Step 3: Change the directory from C:\Windows\System32> to C: by typing in cd/
      Step 4: Copy and paste DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1 
      Step 5: Press Enter
    • Thanks too much!!! I've been hearing some people saying: "run the installer from the commandline", but i did not know how I would complete this. Thanks Roger P England and Mavaddat!
  • Version 14.1.20624 installed ok, but Visual Studio still shows the update and version 14.1.20203
    5 Posts | Last post August 07, 2016
    • Version 14.1.20624 installed ok, but Visual Studio still shows the update and version 14.1.20203
      I completely uninstalled 14.1.20624, rebooted, and reinstalled it succesfully. VS still shows the update and the old version.
      Same problem for Tools for Universal Windows Apps 1.4.1, it still shows v1.3.0. Tap update result in this error:
      Microsoft Visual Studio
      The selected Visual Studio item 'Tools for Universal Windows Apps (1.4.1) and Windows SDK (10.0.14393)' failed to install.  Check the %TEMP% directory for VS install logs.
      WTF ?
    • Ok fixed it by relaunching the vs installer, selecting all required items (including these ones) and manually copying a missing package 
      EspC from E:\packages\EspC to the correct windows package cache folder.
    • By vs installer, i mean the real vs pro installer from the iso DVD.
    • Ouuups, in fact no. It didn't worked. Same problem.
    • It only fixed Tools for universal windows apps 1.4.1 which installed successfully. and web tools say it is already installed.
  • Setup Fail
    3 Posts | Last post August 02, 2016
    • Setup has detected that Visual Studio 2015 Update 3 may not be completely installed. Please repair Visual Studio 2015 Update 3, then install this product again.
      Version of VS 2015 Enterprise: 14.0.25424.00 Update 3
    • I am having exactly this problem; same version of Enterprise as well. 
    • Note: The solution stated elsewhere on this page seemed to work OK.
      DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1
  • Install Error with Hash mismatch
    4 Posts | Last post July 19, 2016
    • I tried for 3 times for installing the DotNetCore.1.0.0-VS2015Tools.Preview2.exe, but all of were failed and show same error "Hash mismatch".
      Is any one can help to fix this problem?
      Here is the error log:
      Error 0x80091007: Hash mismatch for path: C:\ProgramData\Package Cache\.unverified\WebToolsExtensionsVS14, expected: F752395980A6E1BB22418B359BB959EDA4564228, actual: 4EEA4284E7F482D551EF2681C0279CBD2FEF60E5
      [1A00:0E8C][2016-07-13T13:52:27]e000: Error 0x80091007: Failed to verify hash of payload: WebToolsExtensionsVS14
      [1A00:0E8C][2016-07-13T13:52:27]e310: Failed to verify payload: WebToolsExtensionsVS14 at path: C:\ProgramData\Package Cache\.unverified\WebToolsExtensionsVS14, error: 0x80091007. Deleting file.
      [1A00:0E8C][2016-07-13T13:52:27]e000: Error 0x80091007: Failed to cache payload: WebToolsExtensionsVS14
      [1844:0864][2016-07-13T13:52:27]e314: Failed to cache payload: WebToolsExtensionsVS14 from working path: C:\Users\top_d\AppData\Local\Temp\{1DD8A883-3241-44BF-A405-CB44A7FCD336}\WebToolsExtensionsVS14, error: 0x80091007.
      [1844:0864][2016-07-13T13:52:27]e349: Application requested retry of payload: WebToolsExtensionsVS14, encountered error: 0x80091007. Retrying...
      [1844:0864][2016-07-13T13:52:27]w343: Prompt for source of package: WebToolsExtensionsVS14, payload: WebToolsExtensionsVS14, path: D:\top_d\Downloads\packages\WebToolsExtensionsVS14_rc2_39.msi
      [1844:0864][2016-07-13T13:52:30]i338: Acquiring package: WebToolsExtensionsVS14, payload: WebToolsExtensionsVS14, download from:
      [1A00:0E8C][2016-07-13T13:53:54]e000: Error 0x80091007: Hash mismatch for path: C:\ProgramData\Package Cache\.unverified\WebToolsExtensionsVS14, expected: F752395980A6E1BB22418B359BB959EDA4564228, actual: 4EEA4284E7F482D551EF2681C0279CBD2FEF60E5
      [1A00:0E8C][2016-07-13T13:53:54]e000: Error 0x80091007: Failed to verify hash of payload: WebToolsEx
    • Hello, this problem has been solved? Please share it with me.
      I've had the same problem.
      WebToolsExtensionsVS14_rc2_39.msi This file is corrupted.
    • Hi DLDJL
      Sorry , it's not solved.  
    • Does your computer use 3rd party disk encryption?  I had issues with Dell's encryption messing up MD5s on MSDN ISOs.
  • Missing nuget packages
    1 Posts | Last post July 14, 2016
    • I am installing this but I always get stucked close to the end because of missing package for nuget tools. I think I have the latest version installed separately but this NetCore installer looks for the specific version.
      I have VS 2015 Ent update 3 installed
      > I search and I cant find a way to download the version directly, failed.
      > I tried to hack the package cache by creating the folder and copy the new MSI, failed.
      > I copy my colleague package package but the specific version is not listed there either.
      C:\ProgramData\Package Cache\{E57FDCC5-5E29-3BDE-B24F-0031FDD2D6EE}v3.1.60717.741\packages\WPT\
  • Configure ESLint
    2 Posts | Last post July 08, 2016
    • Hi, how do I configure eslint? Usually one can just drop an .eslint.json file into their project folder but that doesn't work. I also tried the solution folder.
      I get a zillion compiler errors due to white-space which doesn't matter so why is it a compiler error by default?!
    • Hi @CarlinScott, can you post your question on Thanks!
  • install offline
    2 Posts | Last post July 06, 2016
    • I have run into issue when I tried instal this extension machine without internet.
      Is there any possible way to do it ?
      Thank you in advance,
      Martin Bodocky
    • Hi Martin
      The EXE is just a bootstrapper that downloads everything it needs. You can create an offline install, e.g. if you wanted to have it staged on a server, but it would need to download everything at least once.
      For example, if you take the EXE and then from a commandline run: <EXE> /layout C:\NetCoreTools, it will download all the individual MSIs in the bootstrapper and place them under C:\NetCoreTools\packages, including the EXE itself. At this point you can run the EXE locally and it will try to resolve the packages locally from that folder before trying to go online.
      We didn't create a static image because the bootstrapper actually wraps other bootstrappers, e.g. .NET Core SDK that in turn would try to pull down other dependencies such as the C++ redists. A static image is also quite large ( > 500MB). We've seen some issues in the past where a single large file like that can get corrupted.
  • Why is this update happening?
    7 Posts | Last post July 06, 2016
    • Why is this extension getting updated for users who are not using .NET Core? This is a RC release, seems like this update shouldn't be getting pushed to everyone.
      After installing this update (14.1.20512.0), NPM is installing packages that were not previously getting installed and this initially broke our front-end build process.
      I've tried rolling back(unsuccessfully) by repairing VS and by modifying the installation. The previous version was 14.1.11106.0 - if anyone knows how to rollback to that version, let me know. Also, thoughts on why a RC update is getting pushed to everyone, including non-Core users, would be helpful.
    • I've just uninstalled and reinstalled VS Community 2015 and my project still will not load and it says it's incompatible. Thanks Microsoft for breaking my program. It worked fine before the updates but now will not work. I guess that now the software is free and open source, the quality is going down.
    • I've managed to revert update. You need to uninstall this update, and then install WebToolsExtensionsVS14.msi from here -> It's previous version - 14.1.11106.0. 
      After that delete {your_solution}\.vs\config\applicationhost.config file.
    • Yes, I think Microsoft shouldn't "push" users either to the new technology (even when I love it). It's something that it is discouraging many developers around the globe, specially when this break things that were working just fine minutes ago (like other developers said). 
      Again, I love the idea of Universal app, I really do. But for everyone's sake -including Microsoft's reputation and sales- please put emphasis on marketing and evangelize more.
    • required update 3?
    • @mpavkov, the update is for both web tooling in general and .NET Core tooling. The bits for web tooling is RTM quality whereas NET Core tooling is Preview quality. If you are not interested in .NET Core tooling, it shouldn't affect your web tooling in general.
      In general, if you run into issues, please open them on as it has richer support for discussions like this.
      Thanks and sorry for the inconvenience.
    • @regal60740, please open an issue on and we will follow up with you there. Thanks and sorry for the inconvenience.
1 - 10 of 22 Items