WPF

There are a number of tools you can use to convert PNG/JPEG images to XAML. For example, Inkscape[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

LOL - I knew that. Wow, I need to take a break. Thanks If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.

Thanks, that did it. I always thought using that would cause the child style to based off WPF's base style If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.

Instead of a DataTable, deserialize the XMl into a collection of classes, that implement INotifyPropertyChanged, and bind to that. [Details of XML serialization | Microsoft Learn](https://learn.microsoft.com/en-us/dotnet/standard/serialization/introducing-xml-serialization) [https://stackoverflow.com/questions/4203540/generate-c-sharp-class-from-xml\](https://stackoverflow.com/questions/4203540/generate-c-sharp-class-from-xml) "Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

You should be able to use the "live visual tree" and "live property explorer" tools, which are built in to Visual Studio: Inspect XAML properties while debugging - Visual Studio (Windows) | Microsoft Learn[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Just found out we already have an in-house style for that in one of our dependency. :-D Thanks. CI/CD = Continuous Impediment/Continuous Despair

Awesome, it's working. :rose: CI/CD = Continuous Impediment/Continuous Despair

Both. Your app should anticipate the user's intention by the parts they're accessing and start asynchronous loads into observable collections that get bound when a particular user control ("view") gets loaded. And / or you need revised stored procs / data views / filtering. "Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

Adding background as Transparent for WindowsFormsHost worked for me.

it looks nice, even if it is a little bit "in your face". Will experiment with look and feel. Thanks again CI/CD = Continuous Impediment/Continuous Despair

It looks like that's related to "conditions" in the csproj referring to configuration profiles that don't exist in the solution. Look for things like: Debug and check that the configuration value matches an existing build configuration for your solution: Understand build configurations - Visual Studio (Windows) | Microsoft Learn[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Adding the datacontext does not change anything. The menu loads correctly the first when I right click on the button; after that it loads correctly on the left click. It's not urgent for now, I'm prototyping a UI. , but slightly annoying. Thanks. CI/CD = Continuous Impediment/Continuous Despair

You're actually creating a user control; and not a "custom control". The "simplest" way to create a user control is to add properties {get;set;} to the UC in the .cs; bind the controls in the .xaml to the properties in the .cs; and implement INotifyPropertyChanged (which for a "few" controls, can be issued with "no contol name" without any hit on performance). The DataContext of the UC is the UC; i.e. "this". Any time there is new data, you load the properties and call "property changed" which updates the UI. If it's a two-way UI, data moves to the properties and events on the controls get invoked (e.g. text changed). That's the pattern, and most everything else has a "smell". X| :-\ Anything else that happens is a function of what events the user control wants to "surface" (e.g. a request queued to an observable collection or file watcher). "Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

Spot on, sometimes its the wood for the trees. thanks a bunch Madaxe

It has been so long away from the P&P camp that Microsoft's influence on it has long been expunged. The simple fact is, Microsoft has their own MVVM offering which has nothing to do with Prism. Your statement implied that Prism was a Microsoft offering and it hasn't been for a long time so if you are pushing someone to Microsoft's offering, at least make sure it is Microsoft that is offering it. Advanced TypeScript Programming Projects

View models are about "data"; not "behavior". [mvc - Should MVVM models have behaviour? - Software Engineering Stack Exchange](https://softwareengineering.stackexchange.com/questions/294377/should-mvvm-models-have-behaviour) "Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

Reading DICOM file tags has nothing to do with WPF or the OpenFile dialog. WPF is a presentation (UI) framework, and an OpenFile dialog just gets a filepath from the user. Reading the tag data is just straight up reading a file. There's plenty of info on the web on it. You just have to search for "C# read DICOM tags[^]" and start reading. Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak