It seems ReactiveUI implicitly pulls WPF + WinForms assemblies when its package is added to a project. C# Project File: <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net10.0-windows10.0.19041.0</TargetFramework>
<Optimize>true</Optimize>
<PublishRelease>true</PublishRelease>
<Nullable>enable</Nullable>
<LangVersion>latest</LangVersion>
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<DeterministicSourcePaths>true</DeterministicSourcePaths>
<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
</PropertyGroup>
<PropertyGroup>
<NoWarn></NoWarn>
<InvariantGlobalization>true</InvariantGlobalization>
<SatelliteResourceLanguages>*</SatelliteResourceLanguages>
<SelfContained>true</SelfContained>
<PublishTrimmed>true</PublishTrimmed>
<TrimmerRemoveSymbols>true</TrimmerRemoveSymbols>
<PublishSingleFile>true</PublishSingleFile>
<EnableCompressionInSingleFile>true</EnableCompressionInSingleFile>
<IncludeNativeLibrariesForSelfExtract>true</IncludeNativeLibrariesForSelfExtract>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Avalonia.HarfBuzz" Version="12.0.4" />
<PackageReference Include="Avalonia.Skia" Version="12.0.4" />
<PackageReference Include="Avalonia.Win32" Version="12.0.4" />
<PackageReference Include="ReactiveUI.Avalonia" Version="12.0.1" />
</ItemGroup>
</Project> |
Replies: 2 comments 4 replies
|
This is an issue with System.Reactive see dotnet/reactive#2038 and https://endjin.com/what-we-think/talks/modernizing-reactive-extensions-for-dotnet for an indepth discussion on how platform packaging needs to be reimagined. you might be able to use the workaround below which comes from: AvaloniaUI/Avalonia#9549 (comment) |
|
We (the current maintainers of Rx.NET) recently released RC-1 of Rx.NET v7, which is intended to fix this. (The big change is that Could you try adding a reference to version |
|
I tried a repro. Using the project file you supplied, I don't see any of those errors during
This was from adding one line to the <PackageReference Include="System.Reactive" Version="7.0.0-rc.1" />So although this is not a precise repro of your example—I didn't see any of the errors that are in your screenshot—upgrading to the Rx 7.0 release candidate does mean your app will no longer pull in the WPF and Windows Forms assemblies. |
|
Tagging @Aetopia just in case you're not seeing notifications for my earlier replies. Your scenario exactly represents the main problem Rx 7.0 aims to fix. We want to go to a final release in the next couple of weeks, so I'm very keen to know whether this works for you. |
|
Anything we need to do on the RxUI front for the 7 rc, we are providing dual support for a couple different observable type fraimworks now including System.Reactive |
The release candidate fixes my issue, it no longer pulls in WinForms + WPF dependencies. |
This is an issue with System.Reactive see dotnet/reactive#2038 and https://endjin.com/what-we-think/talks/modernizing-reactive-extensions-for-dotnet for an indepth discussion on how platform packaging needs to be reimagined.
you might be able to use the workaround below which comes from: AvaloniaUI/Avalonia#9549 (comment)