(Starring this question because I’m going to need this answer for the next release of Visual Studio, I bet… And I forget this every time I set up a new machine. I cobbled this together last time from a bunch of different sites, but unfortunately my google-fu cannot find them again, so my sincerest gratitude … Read more
A couple of options to investigate. Check the language standard. You need C++17 or above: If your version of visual studio doesn’t support std::filesystem yet, you can try std::experimental::filesystem. I have the following version and std::filesystem works (with the C++17 language selection shown above): Microsoft Visual Studio Community 2017 Preview Version 15.8.0 Preview 1.1 VisualStudio.15.Preview/15.8.0-pre.1.1+27705.2000
To summarize, sth along the lines of “C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat” x64 or “C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\vsdevcmd” -arch=x64 (try running it with -help) My environment: ** Visual Studio 2017 Developer Command Prompt v15.0.26403.7 on Win10 x64
I’m using it successfully with the following options enabled. In Visual Studio go to: Tools -> Options -> Debugging -> General Enable JavaScript debugging for Asp.Net (Chrome, Edge and IE) Enable Legacy Chrome JavaScript debugger for ASP.NET
As the message implies, you need to install some NuGet packages, one for the testing framework and one for the visual studio test runner. If you are upgrading an old solution using MSTest, you first need to remove the reference to Microsoft.VisualStudio.QualityTools.UnitTestFramework. Then you need to open the Package Manager Console (under Tools-> Nuget Package … Read more
Open Visual Studio Installer Note down which edition of Visual Studio you have installed (eg Professional or Community) Click Modify Click Individual Components Locate the Development activities heading Check the Visual Studio C++ core features component: Click Modify Spy++ might now reside in the following paths, once you substitute the {edition} placeholder with your Visual … Read more
Just open task manager and kill any instances of VBCSCompiler.exe. You don’t even need to close Visual Studio.
In this case you need to go to Control Panel => Programs and Features and choose Visual Studio and update it.
In the project file of your solution you can edit or add an <ItemGroup> element within the <Project> element. This worked for me: <ItemGroup> <Content Include=”appsettings.json”> <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory> </Content> <Content Include=”appsettings.*.json”> <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory> <DependentUpon>appsettings.json</DependentUpon> </Content> </ItemGroup> Please Note that my console project targets .Net Core 2.0 and is running in Visual Studio Pro 2017 Version 15.7.5. Also, … Read more
It might be the case that you have opened your project using File->Open->Folder Use the right method to open your project using File->Open->Project/Solution or File->Open->Website