Bastian Schmidt

Indeed. It revert felt right to use the primary screen, regardless of the DPI issue. But i never found a better way to define a reasonable default. Will think about...

I am also encountering this issue. My use case is: I have fixed axes and LineSeries which never change min/max or anything and they are bound to pre-allocated `ObservableValue` arrays...

My current workaround is: ```c# private static readonly FieldInfo? stepCountFieldInfo = typeof(Axis).BaseType!.GetField("_stepCount", BindingFlags.Instance | BindingFlags.NonPublic); ``` and inside my update loop: ```c# ++counter; if (counter % 25 is 0) {...

That's most likely because your dependency is located where your injected dll is so the default assembly probing from .NET does not find it. The default probing looks at the...

Does the installer prompt for elevation when you click "Install" or at which point during the installation does it show that error?

That's strange as it should prompt for elevation. Could you try to run an elevated command prompt and start the MSI from there?

That makes no sense to me. Could you run the installer with verbose logging enabled and attach the log here? You can enable verbose logging by calling the installer from...

That looks like an bug in WiX/MSI itself as it's not even logging what failed during `ValidatePath`. What's also strange is that ValidatePath returns 1 (success) but does not set...

The code behind file does not seem to be generated, can't you just add a Generic.xaml.cs that has the required content?

The Generic.xaml is generated by my tool, but it doesn't know or care about any code files. If you just create a Generic.xaml.cs at the same directory the compiler should...