question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Microsoft.Windows.UI.Xaml.CSharp.targets was not found - VS17 - Last MRT Build

See original GitHub issue

Hi, I come to you guys for help because I’ve been trying for some time to get the build portal to work at 100% without much success, I don’t know if it’s a bug or something wrong on my side.

I get the following error while MSBuild runs the command "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe" "C:\Users\PROJECTPATH\UWP\PROJECTNAME.sln" /t:Build /p:Configuration=MASTER /p:Platform=x86

During the generation of an APPX from the solution build with the toolkit. I’m suspecting a path issue/something not installed that I missed, but I can’t find it sadly.

EDIT : I should mention that the files actually does not exist, nor it’s parent folder and that my sln file mentions Visual Studio 2015, that surprises me.

Cheers

Here’s the error :

ows.UI.Xaml.CSharp.targets" was not found. Also, tried to find "Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.CSharp.targets" in the fallback search path(s) for $(MSBuildExtensionsPath) - "C:\Program Files (x86)\MSBuild" . These search paths a
re defined in "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe.Config". Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths.
C:\Users\Technoshop_User\Documents\Dev Projects\Unity\GTS_Demo\UWP\GeneratedProjects\UWP\Assembly-CSharp\Assembly-CSharp.csproj(178,11): error MSB4226: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Micros
oft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Also, tried to find "Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.CSharp.targets" in the fallback search path(s) for $(MSBuildExtensionsPath) - "C:\Program Files (
x86)\MSBuild" . These search paths are defined in "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe.Config". Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in o
ne of the search paths.
C:\Users\Technoshop_User\Documents\Dev Projects\Unity\GTS_Demo\UWP\GeneratedProjects\UWP\Assembly-CSharp-firstpass\Assembly-CSharp-firstpass.csproj(183,11): error MSB4226: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\Build
Tools\MSBuild\Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Also, tried to find "Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.CSharp.targets" in the fallback search path(s) for $(MSBuildExtensionsPath) -
 "C:\Program Files (x86)\MSBuild" . These search paths are defined in "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe.Config". Confirm that the path in the <Import> declaration is correct, and that the file
 exists on disk in one of the search paths.```

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:11 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
drenghelcommented, Sep 26, 2017

I’ll be damned, I uninstalled a VS Build Tool version that I installed next to my VS17 installations this morning, and MRTK used VS17 MSBuild ( I just added it too, dunno if related ) and the appx build went AFAIK smoothly. At this point I don’t know if I had very poor look with my environment or if tuts we not explicit enough… But it looks like it’s gonna work. I’ll try to deploy this, I’ll keep you posted.

1reaction
c-trinhcommented, Mar 14, 2019

I’ll be damned, I uninstalled a VS Build Tool version that I installed next to my VS17 installations this morning, and MRTK used VS17 MSBuild ( I just added it too, dunno if related ) and the appx build went AFAIK smoothly. At this point I don’t know if I had very poor look with my environment or if tuts we not explicit enough… But it looks like it’s gonna work. I’ll try to deploy this, I’ll keep you posted.

Thank you so much, this actually works. I have been banging my head on this issue for about a week, only to learn you just have to reinstall the build tool.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Microsoft.Windows.UI.Xaml.CSharp.targets not found
I've opened a solution that workes fine with VS2017 in VS2019 preview 1.1 When trying to compile, I get the following exception:
Read more >
nuget - Microsoft.Windows.UI.Xaml.CSharp.targets was not ...
I have a UWP library project, compiled to target Creators Update, and I am trying to publish it to nuget. Using the command...
Read more >
MSBuild Error when I create a UWP solution in rider
My environment: VS not installed. Only Rider. ... In the `File | Settings | Build, Execution, Deployment | Toolset and Build' Setting. The...
Read more >
Category: Cross-Platform from Visual Studio Blog
In today's blog post, we will cover prerequisites, how to create the custom connector from within Visual Studio and how to quickly build...
Read more >
C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v1.0 ...
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v1.0\Microsoft.Windows.UI.Xaml.CSharp.targets" was not found.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found