When running UITest using MSBuild fails to load. However same test project runs successfully via Visual Studio.
Now i have looked everywhere for last 2-3 days people had similiar issue who have tried to the following:
Make sure CodedUI Test framework is installed
Change the VSToolsVersion to 15.0
I get the following error:
UIMap.Designer.cs(585,29): error CS0246: The type or namespace name 'UITestControl' could not be found (are you missing a using directive or an assembly reference?)
Note:
Migrated from VS2015 to VS2017
EDIT:
Command line for MSBuild:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe";
"$(SolutionDir)\VMSCommsUITests\bin\Release\VMSCommsUITests.dll" /settings:"$(SolutionDir)\VMSCommsUITests\VMSCommsUITests.runsettings";
We pass in the $SolutionDir via arguments
Ok it seems that I had also installed BuildTools after installing VS2017.
So upon further investigating i found that some dependencies were missing.
As a result i mmade sure the MSBuild from C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\MSBuild.exe is being used instead and it seemed to resolve the issue for me.
Related
I cant get this problem to be resolved. I finally have finished my project on my pc. Now the project needs to run on my laptop. So i put the project on github via visual studio community 2019 code and imported it on my laptop also via visual studio community 2019.
Now every time i've tried to to run the program i get this error:
MSB4019 the imported project "c:\Program Files(x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\Micrsoft.Cpp.Default.props" was not found. Confirm that the expression int the import declaration "c:\Program Files(x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\Micrsoft.Cpp.Default.prop" is correct and that the file exists on disk
I've tried many things too solve this problem, I tried to reinstall visual studio. I've Completly removed everthing related to visual studio (the installer and the folder with everything in it) and reinstalling it again. Downloading missing sdk software from microsoft, nothing seems to work.
And if I somehow need to change a path, i also tried that but i could not find anywhere where to edit that
This Project NEEDS to run on my laptop
project link: https://github.com/JarodIking/Game-C-
Guys i fixed my issue finally, I had to set the enviroment variable path for VCtargetsPath, and i then had to fix my debugger
I am trying to evaluate a software SDK for displaying PDF files. It comes with a few sample projects, but I am having problems building the C++ projects. I am pretty sure this is a problem with my local environment, but I have no idea how to fix it:
The projects come as a Visual Studio solution, to be used in Visual Studio 2017. Upon first opening it I was told to install missing features (VS17 was a plain install with no workloads before):
After installing that, and twiddling with platform toolset and the general platform target settings, I could finally build the C++ library part that creates a .dll file to be used by the other 2 C++ projects. (I could also confirm that this works fine, as the also included C# project used the library perfectly fine.)
But for the 2 remaining C++ projects I get this error on build:
The package System.Net.Http with version 4.1.1 could not be found in C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\. Run a NuGet package restore to download the package.
FunctionDemo
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\NuGet\15.0\Microsoft.NuGet.targets
377
Unfortunately I have no idea what "Use NuGet Package Restore to download them." means in that context - both the solution and all the projects have nothing listed when using Manage NuGet Packages... in Visual Studio. So I don't even know where this dependency comes from. (Are those part of the general SDKs I have installed maybe?)
Double clicking the error message opens C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\NuGet\15.0\Microsoft.NuGet.targets with this:
<ResolveNuGetPackageAssets Condition="Exists('$(FrameworkInjectionLockFile)')"
NuGetPackagesDirectory="$(FrameworkInjectionPackagesDirectory)"
RuntimeIdentifier="$(NuGetRuntimeIdentifier)"
TargetMonikers="$(NuGetTargetMonikerToInject)"
ProjectLockFile="$(FrameworkInjectionLockFile)">
But I guess this is pretty standard. Does this tell me something where the error comes from?
On the filesystem C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\System.Net.Http\4.1.1 indeed does not exist. Any tries to fill it manually (download the nuget package manually to a project, and copying the results here, using any solutions or commands to run I can find online) failed.
If found out that C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\ is the package source Microsoft Visual Studio Offline Packages which I can view via Options -> NuGet Package Manager -> Package Sources in Visual Studio 2017, but disabling it there didn't change anything about the error message.
Am I looking in the wrong place?
Is this really my local problem or a project problem?
How can I fix this problem?
I "fixed" this by getting the C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\System.Net.Http\4.1.1 folder from another developer. Then the error message switched to other packages, so in the end he sent me his full C:\Program Files (x86)\Microsoft SDKs\NuGetPackages and I copied folders over until it finally built.
Still not idea what caused this, must have been a missing payload or SDK that Visual Studio thinks was installed but really wasn't :/
Keeping the question unanswered though in the hopes that someone comes along that know the real fix.
This happened to me after upgrading from Visual Studio 2017 to 2019. While not the same file, my error was:
error APPX0702: Payload file 'C:\Program Files (x86)\Microsoft
SDKs\NuGetPackages\System.Private.ServiceModel\4.1.3\runtimes\win7\lib\netcore50\System.Private.ServiceModel.dll'
does not exist.
For whatever reason, after upgrading, both VS 2017 and VS 2019 were looking for this in C:\Program Files (x86)\Microsoft SDKs\NuGetPackages..., but I found it actually existed in the similarly named folder C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages... instead. I assume during the installation of VS 2019 this directory was created?
I manually copied the files over to where it was looking and then the build finally worked. The underlying issue isn't fixed, but maybe somebody smarter than me can explain why this happened in the first place.
For me disabling C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\ didn't work either. But then I had deleted it from Nuget.Config and it had finally solved the problem.
In Visual Studio 2017, I go to the Package Manager to do a dotnet restore.
Then I get an error message
error MSB4019: The imported project "C:\Program
Files\dotnet\sdk\2.1.201\Microsoft\VisualStudio\v15.0\WebApplications\Microsoft.WebApplication.targets"
was not found.
I navigate to
C:\Program Files\dotnet\sdk\2.1.201\Microsoft
and the VisualStudio path is missing and hence the error message. How do I fix this?
If you have a mixed solution that contains both .NET Framework and .NET Core (web) projects, dotnet restore won't be able to build .NET Framework projects and will cause an error in newer versions of the .NET Core SDK, as detailed in NuGet/Home#6665.
If you are experiencing this error from the command line, but not from Visual Studio itself, you might have more luck building the full solution using MSBuild.
I'm going to use the HelixToolkit.SharpDX with VS2017 in my Windows 10 workstation, when I attempt to build the solution, it will prompt the Assertion Failed error with "No fxc.exe found".
I have checked the installation option, Windows SDK has been included, nand I have downloaded and install again, and I can see the fxc.exe in "C:\Program Files (x86)\Windows Kits\10\bin\10.0.16299.0\x64" & "C:\Program Files (x86)\Windows Kits\10\bin\10.0.16299.0\x86" folders, so it should be available for any windows version, but unfortunately, the same error reported.
However, I have also installed VS2017 in another Windows 7 machine, it works fine, and it has the fxc.exe in the same folder as my Windows 10 workstation, but it can be located by VS2017.
Is there any setting in VS2017 to locate the fxc.exe?
Or how can I fix this issue?
Copy fxc.exe in Bin\10.0.xxx\x86 to Bin\x86 to fix this issue. Because the HLSL compile tool hard coded the path.
One can find solution on helix toolkit github page.
Visual Studio 2017. Windows 10 SDK.
Missing fxc.exe issue with newest Windows 10 SDK:
Copy fxc.exe in C:\Program Files (x86)\Windows
Kits\10\Bin\10.0.xxx\x86 to C:\Program Files (x86)\Windows
Kits\10\bin\x86 to fix this issue. Because the HLSL compile tool hard
coded the path.
This seems to have been fixed in Visual Studio 2019 16.0.2, as of writing. Just have to make sure $(WindowsSDK_ExecutablePath) is pointing to the correct SDK directory and the build version that matches with the Targeted Platform in the Project Properties page.
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/a3032567-d8e7-4b01-81b7-0612047a6299/why-do-we-need-to-copypaste-fxcexe-from-bin100xxxxx0x86-to-binx86-directory-in-the?forum=windowssdk
Second post answered:
The executables that the C++ build process uses from the Windows SDK directory are MIDL.exe, MT.exe and RC.exe. If you digitally sign your executables then you will find signtool.exe here too. So I am kind of surprised that it finds some critical build tools correctly but others it fails to find.
My suggestion would be:
1) Verify that you are having this problem with your project in Visual Studio 2019 16.0.2 (the latest version at the time of writing) or Visual Studio 2019 Preview (16.1 Preview 1 at the time of writing). This is to check that if this has been found to be a bug, then it could have been fixed.
2) Create a completely new project. Without touching the project's executable path, try to create a sample that shows this behaviour. It doesn't need to be a full sample, just complete enough to show that Visual Studio fails to find fxc.exe.
3) If doing all of this shows that Visual Studio fails to find fxc.exe, then through Visual Studio 2019, report it as a bug.
But I will mention that a naïve test on my end shows that Visual Studio 2019 can compile HLSL shaders without any issues using the 18362, 17763 and 17134 SDKs. These were tested because these are the versions that I have installed.
I am using VS2008. (C++ code). I am getting the error when compiling:
error PRJ0002 : Error result -1073741515 returned from 'C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\cl.exe'
I tried all the options available in net including one of the stackoverflow link
Visual Studio error confusion + help please
Tried shortening the path of my source solution by placing directly inside C drive.
Tried Removing any VS plugins. Tools -> Addin Manager.
My codebase is fine because the same solution is compiling fine on other machines. When I copied the solution to a particular m/c I am getting this error.
It has custom build steps, post build steps. But they are all correct because its working on other computers.
0xC0000135 (hex -1073741515) can be found in NtStatus.h
Its meaning is STATUS_DLL_NOT_FOUND. Try to look on your cl.exe with Depends
Have you tried resetting your settings of Visual Studio? It is available in Tools->Import and Export Settings. Setting it to Visual C++ Development Settings might do the trick. I know it have helped others with the same problem.
I fixed it by adding this path to the environment PATH variable:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE
some of the dependencies of the cl.exe are lying in this directory, which were unresolved.