BUILD FAILS reports issue in Microsoft.Windows.UI.Xaml.Common.targets #8145
Unanswered
ToddGlodek
asked this question in
Q&A
Replies: 2 comments 3 replies
-
Thanks. Can you provide a binlog by following these instructions ? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I think you can't add Core project for Controls project. But you can do it with .Net Standard 2.0. <ItemGroup>
<ProjectReference Include="..\StandardTest\StandardTest.csproj" />
</ItemGroup> But if you need to use only Core project you can try next entry: <ItemGroup Condition=" '$(TargetFramework)' == 'net6.0-android' ">
<ProjectReference Include="..\CoreTest\CoreTest.csproj" />
</ItemGroup> #if NETCOREAPP
using CoreTest;
#endif
namespace UnoTest
{
public class Class1
{
#if NETCOREAPP
ClassTest gasg;
#endif
}
} |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After compiling my UnoPlatform project successfully thousands of times, I have started getting a new compile/build error after splitting some of the project file out into a "Multi-Platform Library". The error is not related to my own code but instead is some kind of "Xaml Internal Error WMC9999" related to the file "Microsoft.Windows.UI.Xaml.Common.targets". Specifically, the error is:
I'm not an expert in this level of build mechanics detail, but this 'common targets file' appears is a file used by all build operations. All my other (non-Uno) projects continue to work - and some of the projects in my Uno solution build successfully - just not this one library project.
As you can see from the attached image, it is the second '.controls' library project that wont compile. The '.controls' library project tries to reference another '.core' library as a project reference - however, it displays a little 'ignored' icon in the Dependencies tree. I read in your online documentation on Working with cross-targeted class libraries that:
Is this the same issue ? I have followed the instructions (even though it was a different error ). Is what I am trying to do supported by Uno at this time. The desire is to split the project up so that different teams can work on different chunks of the application & can test their component independently before they are merged into the application as a whole.
Beta Was this translation helpful? Give feedback.
All reactions