I'm switching to visual studio 2017. The clang-format plugin does not seem to be compatible with this version yet.
Is there a way to force visual studio to use the old plugin anyway ? Is it compatible ?
Is there a not yet released version of the plugin that I can find somewhere or build myself ?
I checked the clang mailing list and it looks like Hugo Puhlmann's already done the changes but hasn't submitted a patch yet:
http://lists.llvm.org/pipermail/cfe-dev/2017-January/052243.html
http://lists.llvm.org/pipermail/cfe-dev/2017-January/052251.html
http://lists.llvm.org/pipermail/cfe-dev/2017-January/052253.html
http://lists.llvm.org/pipermail/cfe-dev/2017-January/052484.html
Update: Just sent him a message on Twitter. He responded:
"I'll have a look at it today and submit an updated build, since there
seems to be more interest on it."
Update (again): Hugo's posted a link to his build below.
Actually, you can
Download the latest Clang-format for visual studio 2013 and then
Unpackage the *.vsix file with 7-zip
Add one section like the section in the "extension.vsixmanifest" xml file to suuport VS2013 and change the version to "15.0"
Then re-package all the files to a zip archive with 7-zip and rename its extension to *.vsix.
Now you have a clang-format extension installation package supports VS2017.
Related
There are some bugs introduced in 16.7 that affect me, and I would like to use 16.6.
Most of the questions I found refer to using VS2017 compiler, I want to use VS 2019 compiler, just an older version.
Best I found in official docs is to remove VS and reinstall, but I would like to avoid that.
I found solution of such problem for myself in following way.
You should locate MSVC build tools of chosen version in your folder like "Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC XX.YY.ZZZZ. If you just upgraded your VS it didn't remove old build tools (I hope). If it did or you just installed newer versions you can use VS Installer to add/download MSVC Build Tools of one of previous version.
You should change links to VCTools of previous version for Toolset v142 (that is 2019). To do his you can change text files located at something like "2019\Enterprise\VC\Auxiliary\Build". Files of our interest are "Microsoft.VCToolsVersion.v142.default.txt" and "Microsoft.VCToolsVersion.v142.default.props".
That simple files just contains names of MSVC Tool version to use for Toolset v142
These changes will affect building of all you projects using toolset v142 (that is VC2019 Compiler)
I am sorry that VS does not currently support the ability to roll back a Visual Studio Update, you can only follow the method in the link. Luckily, Microsoft have already understood this issue and rolling back updates is certainly in their backlog. You could vote on this issue and express your demands.
I've created a small text adventure. I've built the solution with Visual Studio Community 2019 using Release and x64 settings. I've zipped up the *.exe file along with the other generated files and sent them to another pc that doesn't have VS installed and the error you see in the image came up. I've searched my pc and the file exists in a couple of different folders, one of them being system32 so i don't know where to place the file on the new pc.
Any help would be appreciated. Thank you
Per #user4581301's comment, the answer is to download a current Microsoft Visual C++ redistributable for the appropriate architecture (i.e. x64).
As I already had a 2019 of the redestributable installed, I had to install the corresponding 2015-2019 x64 distributable.
I have tried the most voted solution and was still missing it. Found out that MS actually has a different version of VC redist inside Visual Studio download page. Look inside the Other Tools section. After installing that, one missing DLL was added.
I was getting the same error and installed VCRUNTIME140_1.dll file and put it in the MySQL Shell 8.0 bin file.
Problem solved.
I was also facing this issue. The below solution worked for me.
Solution:
Download the VCRUNTIME140_1.dll file
Place it in the path - C:\Windows\System32
Check if it solves your problem.
Download and install both the x86 and x64 versions of the Microsoft Visual C++ 2015 - 2019 Redistributable here
I wiped out an old Windows 10 and replaced it with a new Windows 10 by ISO image.
Before wiping out, I copied the folder of Microsoft Visual Studio 2017 Community Edition on old Windows to an external hard disk:
xcopy /E "C:\Program Files (x86)\Microsoft Visual Studio" D:\
Now after reinstalling Windows 10, I copied the VS 2017 folder from external the hard disk to the C:\Program Files (x86)\ folder of new operating system.
I did so to avoid having to download VS 2017 again on new OS.
The problem is other software, like Qt Creator, cannot auto-detect the VS C/C++ compilers. I guess that's because the VS 2017 isn't added to path.
The questions are:
What path should I add to system path in order to VS 2017 to be auto-detected by other software like Qt Creator?
Is there any script which I can run to automatically integrate the VS 2017 to the rest of the operating system.
To answer the questions in your issue:
Copying the content of C:\Program Files (x86)\Microsoft Visual Studio folder is not a recommended way to install VS.
(The complete installation will not only set the Environment variables but also set the related registry keys and values. A simple copy may break this process)
So we always suggest that users install the VS by vs-installer or offline installation package. (Same like what Zlatomir suggests.)
To your actual requirements:
It seems you're just trying to use VC++ compiler in QT Creator instead of developing QT projects in Visual Studio. So build tools for VS package is enough for you.
See this related issue, if we download Build Tools for VS package with corresponding C++ workload, then we can get the compiler the QT needs. There's no need to install the VS IDE for this situation.
And if we need C++ compiler from VS2017, download the Build Tools for VS2017, if we need C++ compiler from VS2015, download the Build Tools for VS2015 Update3. Link of old version about VS Tools see here.
Update:
From the the link older downloads we can see:
Choose the download button according to which version we need. We can find both VS2017 build tools package and VS2015's there.
Usually programs on Windows don't work after you just copy the installation folder.
So right now there is little you can do to fix it, even if you partially fix, you have no way to know if something else will be broken in the future.
So the recommended solution is to download the installer again and create an offline installer for the next time this happens, you can do that by running the online installer with the following parameters: vs_community.exe --layout c:\vslayout --lang en-US (replace vs_community.exe with the actual name of the online installer file, or rename it), for more options, that might require a smaller download (example if you only need native and don't need .net) check the documentation here for the full set of options you have.
At the start I'd like to note that I've spent some time researching this issue and suggested solutions for similar questions like this one didn't help me.
Problem background
I need to migrate a Firebreath plugin project (which I haven't worked on previously) from PC_1 to PC_2.
As far as I'm aware the project was started on PC_1 on Visual Studio 2010 and later moved to Visual Studio 2013 Pro. There's one solution consisting of 19 projects. I have an instruction which says that in order to get the plugin installer I should first Build project_x and after that Build project_y_WiXInstall. Both steps work without any issues on this machine.
Then there's PC_2 which had Visual Studio 2015 Community installed before I started working on it. I've removed it, installed Visual Studio 2013 Pro (version 12.0.21005.1 REL - exactly the same as on PC_1), moved all of the needed files and I'm trying to get rid of all of the compilation errors. So far I figured out I had to install Cmake 2.8, Windows Driver Toolkit 7.1 and manually override an incorrect VCTargetsPath MSBuild variable
Problem description
Currently when I try to compile the project on the new machine I get these two errors (this is an image link since I can't embed images yet on this account). I'm not sure what's going on with the first error message since it looks incomplete and the file CUSTOMBUILD doesn't exist, but I'm not bothered by it too much since the previous compilation error I fixed also had a similar "artifact" as the first error and it disappeared after fixing the second one.
The covered part of the second error message is the project path. The error origin (Microsoft.Cpp.Platform.targets file, line 64) looks like this:
<!-- Error out if toolset does not exists in Visual Studio 2010 or 2012 -->
<VCMessage Code="MSB8020" Type="Error" Arguments="$(_CurrentPlatformToolsetShortName);$(PlatformToolset)" Condition="'$(ToolsetTargetsFound)' != 'true'" />
What didn't help
The error description suggests using an Upgrade Solution... option, but there's no such thing when I right-click the solution
As an accepted answer for the question I've posted at the start of my post suggests, I've checked the Properties of all 19 of my projects (including the project ZERO_CHECK) but their Platform Toolset is already set to Visual Studio 2013 (v120).
I've also tried changing the Platform Toolset to inherit from parent or project defaults for all of the projects. This resulted in it switching to Visual Studio 2010 (v100) (not installed) and after that I've right-clicked on the projects and chose Upgrade VC++ compiler and libraries. After this the Platform Toolset was back to the Visual Studio 2013 (v120) but it didn't help with the compilation error.
As a NON-accepted answer for the question I've posted at the start of my post suggests, I've tried searching for all of the occurrences of 10.0 and V100 in all of my .vcxproj files to replace them but I haven't found any occurrences of them.
[EDIT]
I just got an idea to try building the project with MSBuild from the command line. There's a bit more info compared to errors inside Visual Studio, so maybe it will help with resolving the issue: https://pastebin.com/JhN3dXM3
So the thing you're missing here is that FireBreath projects are built using CMake -- the actual contents of the build directory should always be completely temporary and never stored in source control. To build the project on a new computer you need to run the prep command again from scratch.
If the previous maintainer changed the build files manually and/or migrated it to a newer version of visual studio without using cmake to do it then they did some very ugly things and all bets are off... good luck.
This is why all the firebreath documentation (I wrote most of it) strongly urges that the build directory be transient and you always do project file updates in cmake.
Hope that helps!
Well i downloaded the newest version, then installed, checked to instal entire files on local drive. I restarted Visual Studio 2017 Community and rerun it. Unfortunatelly i can't find in menu > tools anything with should be connected with stylecop ( as in tutorial "how to use stylecop"). I am using x64 Windows7. I really really don't know how to to use it.
Go to extensions and updates and search for stylecop in the online area.
Choose the one by Chris Dahlberg.
Close VS and it will install.
open your project up and make sure you have a settings.stylecop file in there.
right click on the project in the solution explorer and you will see a run stylecop option
After reading a comment from the extension creator, it appears that future development is targeted for the SytleCopAnalyzers NuGet package. Using VS 2017, this was easy to get running. Instructions here -> https://github.com/DotNetAnalyzers/StyleCopAnalyzers.