I have a dev machine and a build machine, both of which have Visual Studio 2012 Premium Update 3 installed (Version 11.0.60610.01). Both machines are 64 bit and are running Windows Server 2012 Version 6.2 (Build 9200)
The Dev machine has the following folder which contains MSTest.exe
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE
On the build machine, that folder doesn't exist and searching for mstest.exe shows that it isn't on the build server anywhere.
Opening Control Panel > Programs and trying the Change operation doesn't provide any option to install mstest. All options shown in that Change window are identical on each machine.
The build server is also installed as a TFS agent
I've tried re-installing VS but no change.
Why isn't MStest.exe installed on the build machine and how can I get it installed?
I am using VS2017 and I was facing the same issue and I found it in here.
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\Common7\IDE
Anybody using the VS2017 and facing the same issue can search the directory I have mentioned above to search MSTest.exe
Problem solved - the test components were on the F drive for some reason
This sounds like you did what I did.
If you install the update "2012.3" it will only install minimal components and not the full IDE. Try installing Visual Studio from the ISO (~2GB) and then apply the Update...
I found on a different directory:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\MSTest.exe
EDIT: I came upon this page because I am trying to make the transition from Visual Studio to the Jetbrains Rider IDE and they assisted with some other questions on where to find dependencies for their command line Justmock runner here
Related
I have a problem when trying to install apache 2.4 on my windows 10. It always shows the error that VCRUNTIME140.dll is missing. I have checked other threads and found out that installing the 2015 Visual c++ Redistributables x64/x86 always solves the problem but I have both installed and I still have this problem. Are there any other solutions?
You need to install Microsoft Visual C++ 2015 Redistributable Update 3 RC, please find the link here, choose between the 32bit or the 64bit.
Reinstall the apache 2.4 and error should gone.
I had the same issue after installing wamp on windows 10.This worked for me.
Download VCRUNTIME140.DLL
Copy the dll file to C:\Windows\System32 using administrative privileges.
Try reinstalling apache.
Download and install the proper version of Microsoft Visual C++ 2015 Redistributable Update 3 RC regarding your hardware architecture (x86 / x64). Use the link below:
Microsoft Visual C++ 2015 Redistributable Update 3 RC
On Windows 6 X64, got an error 500 on any PHP files,
installing the 2015 Visual c++ Redistributables x64 solved my problem.
I'v already had VC 2015 Redist on my PC but files were not copied into Windows\System32.
So I copied missing files directly to this folder. A thing that I should mention is since I compiled my application in X86 mode I copied them from
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\redist\x86
not
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\redist\x64
I know that this solution is not the ideal one, but it was a workaround for my case.
If you are using Microsoft Visual C/C++ and you have already downloaded VCRUNTIME140.DLL, Go to Project Properties->Configuration Properties-> C/C++ -> Code Generation, Set Runtime Library Multi-threaded (/MT)
Remove apache 2.4 from your pc
Download VCRUNTIME140.dll from this link
Copy VCRUNTIME140.dll file and paste it inside to Windows/System32
Finally reinstall apache and run
After windows update to 1909, getting this error while building my solution in VS Studio 2019
Error Details
Could not run the "GenerateResource" task because MSBuild could not
create or connect to a task host with runtime "CLR4" and architecture
"x64". Please ensure that (1) the requested runtime and/or
architecture are available on the machine, and (2) that the required
executable "C:\Program Files (x86)\Microsoft Visual
Studio\2019\Professional\MSBuild\Current\Bin\amd64\MSBuild.exe" exists
and can be run.
Windows version: 1909
Upgraded from 1803
Visual Studio version: Visual Studio Professional 2019 version 16.7.5
Please let me know anyone encountered this issue earlier, any help will be appreciated.
Try to add these node in xxx.csproj file:
<PropertyGroup>
<GenerateResourceMSBuildArchitecture>CurrentArchitecture</GenerateResourceMSBuildArchitecture>
<GenerateResourceMSBuildRuntime>CurrentRuntime</GenerateResourceMSBuildRuntime>
</PropertyGroup>
More steps about this issue, you can refer to this similar issue.
To be more specific, set an system environment variable DisableOutOfProcTaskHost to true.
Or DISABLEOUTOFPROCTASKHOST to 1.
as I said in here
I had the same Error (in version 16.9.3) but By Repairing Visual Studio 2019, Updating last version of windows 10, close VS, delete .vs hidden folder (under solution folder) ,bin and obj folder then restart your VS . Fortunately My problem was solved.
I already have Visual Studio 2017 professional with Desktop Development with C++ installed.
I am trying to build the Virtual Serial project found here:
https://github.com/Microsoft/Windows-driver-samples/tree/master/serial/VirtualSerial
When I try to build it, I get the error:
Severity Code Description Project File Line Suppression State
Error MSB8020 The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found. To build using the WindowsUserModeDriver10.0 build tools, please install WindowsUserModeDriver10.0 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 "Retarget solution". virtualserial C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets
I cannot find any instructions on installation aside from this website.
https://learn.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk
I downloaded the WDK for Windows 10, version 1803.
I closed VS2017 and ran the installer.
When running the installer I got the message in the screenshot below, I clicked Next to continue installing
After running the installer, the project still does not build, with the same error: WindowsUserModeDriver10.0 is not installed.
What am I missing during installation? Is this the correct installer for regular VS2017 (not community edition)?
Thanks,
I know this is old, but I recently fell into this rabbit hole. What worked for me was uninstalling all of the WDKs, rebooting, and installing WDK 1803 (the wdksetup.exe program downloaded from Other WDK downloads shows version 10.0.17134.1 in properties). That WDK installer specifically calls out VS 2017 when you add the Visual Studio integration at the end of the install process.
In my situation, I installed vs2022 with SDK 19041 and WDK 19041.
After some testing, I realized that VS2022 only supports WDK 22621(so on this date). So I installed WDK 22621 and SDK 22621, and problem solved.
If you still can't find Kernel Driver Build option, try run this file C:\Program Files (x86)\Windows Kits\10\Vsix\VS2022\10.0.22621.0\WDK.vsix(WDK 19041 only has VS2019). It's a Visual Studio's extension.
According to this: https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/windows-wdk-on-visual-studio-2017-community/fdbd2b44-e57a-4849-903d-04001205a764
WDK is not currently supported by visual studio 2017.
This is ridiculous
I have a problem with autocompletion in VS 2017 Community.
Previously I had VS 2017 Enterprise from school, but the key expired so I moved to Community.
Before, everything works great, but now it doesn't work at all.
I found a solution on Stack Overflow here but it doesn't work, so found another solution at GitHub here.
And I got this:
Build FAILED.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1601,5): error MSB4036:
The "GetReferenceNearestTargetFrameworkTask" task was not found. Check the following:
1.) The name of the task in the project file is the same as the name of the task class.
2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface.
3.) The task is correctly declared with in the project file, or in the *.tasks files located in the
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin" directory.
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:00.11
Do you know what to do next?
I had the same error message but for a different problem.
So, I'm using MSBuild to automate build/deploy process for Azure Functions. Everything was working fine until I updated both Visual Studio 2017 and Visual Studio Build Tools 2017 at which point I started getting this error. To be precise I got this error only when using MSBuild, building project manually from VS was working fine.
In my case I already had everything set as per #Programmer's answer.
But as I was using MSBuild it turned out that I also had to install NuGet targets and build tasks which are part of Visual Studio Build Tools.
Follow these to fix that error. This applies to VS 2017:
Fix 1:
1.Install Nuget PackageManager from here.
2.Restart Visual Studio.
If the problem is still there, continue below
Fix 2:
1.Download and start/run the Visual Studio Installer again.
2.While the Visual Studio Installer is still running, go to the "Individual Components" tab
3.Tick the "NuGet package manager" check-box that is under "Code tools" option.
4.Click Install to install it.
Screenshot of where this is located:
That should fix the error you see in this question. Restart Visual Studio and test the auto-completion function. If it's not working, see the answers from this question as that is a whole different issue.
I was seeing this issue with msbuild 15.6.82 on a build environment that does not have VisualStudio 2017, only VS Build Tools.
Here's a PowerShell script that resolves this issue, it pretty much does the equivalent of previous answers in the VS Installer, but silently and waiting for completion.
Start-Process "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" -ArgumentList 'modify --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools" --quiet --add Microsoft.VisualStudio.Component.NuGet.BuildTools --add Microsoft.Net.Component.4.5.TargetingPack --norestart --force' -Wait -PassThru
I'm working with a headless build server on server core, resolved by installing chocolatey package choco install visualstudio2017-workload-webbuildtools from here:
https://chocolatey.org/packages?q=msbuild
I'm reporting an answer from a Microsoft techician
This usually indicates one of two things:
A failed VS installation. If that's the case, I would recommend running a repair on your VS install.
You have msbuild assemblies in the GAC. If that's the case, please ungac them.
Livar Cunha [MSFT]
I got the same problem in Visual Studio 2019, I solved it by simply install unity package
I'm using Windows 7 SP1 and Visual studio Ultimate 2013. TFS server 2013 is installed in Windows Server 2008.
Below error occurred while trying to build one solution which supports multilingual resx files:
C:\Program Files
(x86)\MSBuild\12.0\bin\amd64\Microsoft.Common.CurrentVersion.targets
(3001): Task could not find "AL.exe" using the SdkToolsPath "" or the
registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SDKs\Windows\v8.1A\WinSDK-NetFx40Tools-x86". Make sure the
SdkToolsPath is set and the tool exists in the correct processor
specific location under the SdkToolsPath and that the Microsoft
Windows SDK is installed
I have gone through similar questions, but those solutions didn't work. Few are given below:
Install Windows SDK
Windows SDK is already installed
al.exe is present in C:\Program Files\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools
al.exe is present in \Windows\v7.0A\bin and v8.0A\bin\NETFX 4.0 Tools
Remove resx files and build
Resx files are part of the project and I want them to be in my build.
Any idea to fix this issue?
Thanks for your comments. I installed Windows SDK in server machine, where TFS is installed. It solved my problem.