UPDATE (2017-02) Node Tools for Visual Studio (NTVS) has been using the Salsa analysis engine since v1.2 and using NTVS is likely the path of least resistance for JSX support. https://github.com/Microsoft/nodejstools Read (and upvote) this answer for more details: https://stackoverflow.com/a/41996170/9324 ORIGINAL ANSWER I ran into the same issue and found two solutions – one using … Read more
For me I didn’t have any uncommitted changes or any untracked files, and Visual Studio 2015 still presented the warning. Close the solution in Visual Studio, exit Visual Studio. Open Git Bash (or your favorite Git UI) Navigate to your repository (or open the repository with the Git UI) git pull (or perform pull on the Git … Read more
For Visual Studio 2017 I had to: Run Visual Studio Installer. Select Modify button. Go to “Individual Components” tab. Scroll down to “Compilers, build tools and runtimes”. Tick “Windows Universal CRT SDK”. Install.
I was able to install it by running with SKIP_VSU_CHECK parameter DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1
You can check Visual Studio Downloads for available Visual Studio Community, Visual Studio Professional, Visual Studio Enterprise and Visual Studio Code download links. Update! There is no direct links of Visual Studio 2015 at Visual Studio Downloads anymore. but the below links still works. Visual Studio 2015 direct download links (.iso): Visual Studio Enterprise 2015 … Read more
You need use the NuGet command line in the Package Manager Console: Update-Package -reinstall to force reinstall the package references into project. NuGet Restore only restores files in the packages directory (\packages folder ), but does not restore files inside your project or otherwise modify your project. For example, if a package has added some … Read more
The Update tab is geared to display packages which have updates available while the consolidation tab is geared to display discrepancies between projects where both consume the same nuget package but are targeting different versions.
Although this question has already been answered. I recently came across the same issue. The more specific answer is that you need to install the Visual Studio 2015 Tools (Preview 2): https://www.microsoft.com/net/download/core Direct Download: https://go.microsoft.com/fwlink/?LinkId=827546 Because this wasn’t straight forward and I was working on a 1.1 dotnet core project, I accidentally skipped this step … Read more
The word from Microsoft is that this is a known issue (it originally went to the Debugger team, but was determined it was a build issue, and is now in the Project system team’s hands. There are other bugs open on this issue, and it’s rated Priority 1, so should be on track for the … Read more
I was running in to the same issue, but have just managed a full uninstall by means of trusty old CMD: D:\vs_ultimate.exe /uninstall /force Where D: is the location of your installation media (mounted iso, etc). You could also pass /passive (no user input required – just progress displayed) or /quiet to the above command … Read more