Und am Ende werden sie doch zustimmen (wie immer und wie es andere auch schon getan haben), weil es ja gar „nicht anders geht“ und man sich ungern den schwarzen Peter zuschieben lassen will. #my2cent

Wenn wir jetzt doch nur die Wahlversprechen der letzten xy Jahre umgesetzt hätten, Stichwort Digitalisierung 🤪
In Verbindung mit dem für was der Personalausweis alles so gedacht ist, hätte das ja eigentlich kein Problem sein dürfen.

So was ist einmal als Funktion erstellt und kann immer wieder genutzt werden 🙃

In a normal .net application you would put the styles in extra xaml so that you only have one starting point for customization and that is not so easy to do was what currently bothers me.

Yes, web based was/is under consideration, but it was decided against it because the GUI is quite simple. The gui it self has a few buttons, which called individual functions and then displayed the results in a datagrid, these grids are exported as csv (for documentation purposes).

Cool, it would be good if this were supplied as an internal function or similar with #powershell.

Thanks for the input, I'll take a look and see what I can find. The multiple UserControls in MainWindow is not the problem, I'm trying to figure out how to deal with the resources so I don't have to write the same style for a button or DataGrid x times.

Yes, that's how I do it too, but nowadays it almost seems to me that nobody wants to deal with the cli anymore, or they are afraid of it. That's why I do it just like you, GUI only when necessary.
Thanks for the Discord link, I'll have a look around there.

I tried this a long time ago, but it only worked with the absolute path in the “MainWindow” and that ruins the actual functionality/flexibility, plus it only worked in the “MainWindow” which was/is basically a first step. Thanks for the answer so far.

This is how I currently do it. In a classic .net + WPF app, I integrate the e.g. Colors.xaml via the app.xaml and it works how do I do this in connection with powershell?