Replies: 1 comment
-
My solution is add the code to csproj: <ApplicationDefinition Include="App_MakeReshaperHappy.xaml" Condition="false">
<Generator>MSBuild:Compile</Generator>
<SubType>Designer</SubType>
</ApplicationDefinition> And I create the fake App.xaml named You can find all my code in https://github.com/lindexi/lindexi_gd/tree/b771e3f0/HallnebubeaChelnawjecere |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem Description
We have a WPF class library project that loads Fluent Theme at runtime and faces challenges with view references. Our specific constraints are:
Current Challenge
We need a global solution to resolve theme references in our views without:
What We've Tried
Desired Solution
Looking for a "Fake App.xaml" equivalent that provides:
What's the recommended approach for globally registering theme resources in a WPF class library that will be consumed by external applications? Are there alternatives to App.xaml that can provide similar resource resolution capabilities?
Any insights or workarounds would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions