user control library causing UNOB0017

[dwrainman]

I have a library with user controls in it, i want to use it in another project but keep getting the following error

A reference to either Uno.WinUI.Runtime.WebAssembly or Uno.WinUI.WebAssembly has been detected. See more information at https://aka.platform.uno/UNOB0017

This is the library project file


net9.0-browserwasm;net9.0-desktop
true
Library

true
enable
enable

	<!--
  UnoFeatures let's you quickly add and manage implicit package references based on the features you want to use.
  https://aka.platform.uno/singleproject-features
-->
	<!--
<UnoFeatures></UnoFeatures>
-->
</PropertyGroup>

<ItemGroup Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'">
	<!--
If you encounter this error message:

  error NETSDK1148: A referenced assembly was compiled using a newer version of Microsoft.Windows.SDK.NET.dll.
  Please update to a newer .NET SDK in order to reference this assembly.

This means that the two packages below must be aligned with the "build" version number of
the "Microsoft.Windows.SDK.BuildTools" package above, and the "revision" version number
must be the highest found in https://www.nuget.org/packages/Microsoft.Windows.SDK.NET.Ref.
-->
	<!-- <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref" RuntimeFrameworkVersion="10.0.22621.28" />
<FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref" TargetingPackVersion="10.0.22621.28" /> -->
</ItemGroup>

<ItemGroup>
  <Compile Remove="base\nxShellBase.cs" />
  <Compile Remove="base\nxWindowBase.cs" />
</ItemGroup>

<ItemGroup>
  <PackageReference Include="CommunityToolkit.Mvvm" Version="8.4.0" />
  <PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="10.0.0-preview.5.25277.114" />
</ItemGroup>

<ItemGroup>
  <ProjectReference Include="..\nexus.common\nexus.common.csproj" />
</ItemGroup>

and this is the project that gets the error

net9.0-browserwasm;net9.0-desktop

<OutputType>Exe</OutputType>
<UnoSingleProject>true</UnoSingleProject>

<!-- Display name -->
<ApplicationTitle>nexus.plugins.floor</ApplicationTitle>
<!-- App Identifier -->
<ApplicationId>com.companyname.nexus.plugins.floor</ApplicationId>
<!-- Versions -->
<ApplicationDisplayVersion>1.0</ApplicationDisplayVersion>
<ApplicationVersion>1</ApplicationVersion>
<!-- Package Publisher -->
<ApplicationPublisher>davew</ApplicationPublisher>
<!-- Package Description -->
<Description>nexus.plugins.floor powered by Uno Platform.</Description>

<!--
  UnoFeatures let's you quickly add and manage implicit package references based on the features you want to use.
  https://aka.platform.uno/singleproject-features
-->
<UnoFeatures>
  Material;
  Hosting;
  Toolkit;
  Logging;
  LoggingSerilog;
  MVUX;
  Configuration;
  HttpKiota;
  Serialization;
  Localization;
  Navigation;
  SkiaRenderer;
</UnoFeatures>

[jeromelaban]

Thanks for the question. When using the SkiaRenderer in the project head, the library must also contain the SkiaRenderer uno feature to avoid issues. We'll update the documentation to make this clearer.

[SongOfYouth]

Thanks for the question. When using the SkiaRenderer in the project head, the library must also contain the SkiaRenderer uno feature to avoid issues. We'll update the documentation to make this clearer.

Why can a pure winui package be used by SkiaRenderer or native, but an uno package or assembly must contain the SkiaRenderer uno feature? In some scenarios SkiaRenderer has issue, some scenarios the native has , sometimes we need to change the uno feature to another until the issus was solved.

[kazo0]

We are also in the process of updating the default templates for library projects to avoid this in the future: unoplatform/uno.templates#1614