The "CompileXaml" task returned false but did not log an error?

Markus Schertler 41

Hello,

i have a UWP Project with 2 DLLs. This did compile without problems. Now i copied the code to reuse it for a new project. But wenn i try to compile the message The "CompileXaml" task returned false but did not log an error comes. What can be the reason?

Fay Wang - MSFT 5,191 Reputation points

2020-09-09T01:39:40.343+00:00

Have you also copied the two dlls into the new project? Did you do anything different in it? In addition, could you please provide us a simple repo code by using OneDrive or Github?
Gavin Williams 761 Reputation points

2020-09-15T04:39:12.423+00:00

I'm getting this same error today - single project - it was working last night. No copying, or anything. I added some pages to a Views folder before I logged off but never wired them up. This is the same project that was working previously.

I've restarted VS, didn't help. A very, very simple project, I've been working on it for 2 days.
Alex Earley 1 Reputation point

2020-09-15T19:39:58.287+00:00

Getting the same thing. I am using Microsoft Toolkit from nuget and it is bombing on any reference to those controls.
I notice a few errors show up, then they disappear. I am left with: The "CompileXaml" task returned false but did not log an error.
I have tried deleting bin and obj folders and restarting VS2019. (It only fails if I am trying to create an App Package.)
Fay Wang - MSFT 5,191 Reputation points

2020-09-17T07:57:20.327+00:00

If you try to delete bin and obj folders and clean the project, can it build successfully? In addition, may I know the version of your visual studio?
Alex Earley 1 Reputation point

2020-09-18T16:37:29.523+00:00

I deleted bin and obj , it built successfully. but I still get: The "CompileXaml" task returned false but did not log an error.
I created a new solution and copied everything over. It rebuilds without any errors. It still throws that error when I try to publish. Easy to replicate the issue.
Microsoft Visual Studio Enterprise 2019 Version 16.7.1
Targeting Windows 10 v2004 (minimum v1809)
Microsoft.NETCore.UniversalWindowsPlatform 6.2.10

I finally got it to work! I deleted bin and obj, restarted my PC, I had to delete all of the images referenced in my Package.appxmanifest and re-generate them. It stopped throwing CompileXaml and started to throw errors because some of the images were too large. I reduced the file size of all my images and tried publishing again and it worked!

I think the underlying issue is that the images were not ready for publishing and VS was throwing unrelated errors because it didn't finish building or something like that.
Gavin Williams 761 Reputation points

2020-09-20T01:03:45.777+00:00

Similar to my experience, I removed work I'd done until some errors showed up, fixed those errors, then added stuff back in slowly, fixing namespace errors I think it was for me. Then eventually it worked. So VS seems confused about what's going on. And it's just not reporting the errors that are in the code.
Bob 6 Reputation points

2020-12-03T13:22:21.223+00:00

I too had the CompileXaml error. Shutting down VS, deleting bin, obj and cleaning the project fixed the error for me.

2 answers

Slion 41 Reputation points

2021-02-25T15:02:22.36+00:00

Starting from a clean repository fixed it for me. Close visual studio, delete all files generated by visual studio, bin folder, obj folder, .vs folder, BundleArtifacts folder, AppPackages folder. Open your solution again, compiling, building and publishing should work now.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment
Jussi Palo 6 Reputation points

2021-03-12T13:35:52.877+00:00

Just deleting the bin and obj folders was enough for me. No need to restart anything.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment