Assemblies referenced in namespaceresolver that are not included in build #17050
Unanswered
Justin113D
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Diagnose package adds these references for DevTools. If you build it for release, these are not included unless you install them via nuget explicitly. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I've had testers run a desktop app i made on their linux systems, and while it worked for some, it didn't work for the one using Fedora.
I received the following stack trace:
(Collapsible due to size)
I looked into it by debugging the decompiled avalonia code, and after reaching the namespace resolve, i found these entries in the list:
As you can see, the app references
Avalonia.Controls.ColorPicker
,Avalonia.Controls.DataGrid
orAvalonia.Themes.Simple
, which is correct here, as they are transitive packages fromAvalonia.Diagnostics
. But the diagnostics package does not get included in release builds, and so its transitive packages don't get included either, yet somehow the namespace references do.The dump seems to originate from my external class library, which provides a custom avalonia theme i made. There i also include the package reference
<PackageReference Condition="'$(Configuration)' == 'Debug'" Include="Avalonia.Diagnostics" Version="11.1.3" />
to allow for debugging (not including this line and instead just including it in the app project "works" too, but all controls start glitching out when opening the debug window).To Reproduce
NA
Expected behavior
The app should not try to look up nonexistent assembly references.
Avalonia version
11.1.3, 11.2.0-beta1
OS
Linux
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions