Vusual Studio 2017 installed. After install Microsoft SQL Server Management Studio 2017 (together with her install Visual Studio 2015 shell (isolated)) and build project, project could not load file or assembly Microsoft.VisualStudio.Diagnostics.PerformanceProvider, Version=14.0.0.0.
After remove Visual Studio 2015 shell (isolated) and rebuild, project work. How can I fix this?
Related
I migrate Visual Studio 2013 project to visual studio 2019 and recompiler my all dlls and other files using visual studio 2019. But when I run my application, it still requires msvcr120d.dll in release mode.
Anyone help me out to fix this.
Go to settings and select proper Platform Toolset
for vs2019 select v142
Visual studio 2017 community is installed on my PC along with Visual Studio Build Tools 2017. I am using Windows 10.
Is it still necessary to install Visual C++ Build Tools? Is there a possibility that there will be some packages that cannot be compiled if Visual C++ Build Tools is not available even though Visual Studio Build Tools 2017 is there?
I installed visual studio 2015 and able to compile and run c++ test application within the IDE.
My npm installer is throwing the error
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
When I install visual studio 2013, I don't get this error. The libraries this npm project uses is based on visual studio 2015.
Is there something extra I need to do after the Visual studio 2015 install that I don't need to do in visual studio 2013?
Microsoft provides an npm package that solves all these native build issues without the need to install visual studio.
"windows-build-tools": "^1.3.2"
I Have VS 2015 only installed on my TFS 2013 build server, and get the following error:
TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid ''.
Other sites say to install VS 2013, but why would I have to install VS 2013 on the build server to run unit tests when I have VS 2015 installed?
I have the following switches on my build:
/p:VisualStudioVersion=14.0 /tv:14.0
(This is not a duplicate question as I am using TFS 2013 and am trying to use the Agile Test Runner not MS Test)
Check the solution in this case:
Install VS 2015 or Microsoft Build Tools 2015.
Edit build to use a build process template called TfvcTemplate.12.xaml.
Set MSBuild arguments to /tv:14.0.
But this setting only works for build, not test. As there is no way to set the tool version or tool path for "Run VS Test Runner" activity, installing VS 2013 should be the only way to get rid of this error.
I had a similar problem - was getting the error
TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid 'D:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow'.
It ended up being that even though Visual Studio 2015 was installed on the build agent, the user that the Build Agent was running as didn't have read/execute permissions to that folder.
I am using Visual Studio 2013 community and created C++ project.
I want to share the project with a colleague working with Visual Studio 2012 professional.
Once he took the project he had to change the toolset to v110 and it worked just fine for him.
When he shared it back with me I got the message:
error MSB8020: The build tools for Visual Studio 2012 (Platform Toolset = 'v110') cannot be found.
To build using the v110 build tools, please install Visual Studio 2012 build tools.
Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Upgrade Solution...".
I do not want to upgrade the solution, as that will cause us each time to change the project, but I couldn't find anywhere to download the VS2012 build tools.
Where can I find Visual Studio 2012 build tools?
You can have both Visual Studio 2012 and Visual Studio 2013 installed on the same machine. Once you have both installed you can use the Visual Studio 2012 compiler in Visual Studio 2013.
So I suggest you install Visual Studio 2012. I think Express edition should be enough.
Alternatively, your colleague can install Visual Studio 2013 Community Edition alongside his existing Visual Studio 2012 Professional Edition. I think the features are roughly equivalent the only question is if they are breaking the license terms.