WPF

Dear Richard, many thanks for your help. Now it works. And I think I understand the functionality of DependencyProperty much better now. And sorry for the GitHub & 7z. I'm very new there.

It sounds like you're creating two instances of the viewmodel. What does the PlayerHostView look like? "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Andre Oosthuizen wrote: no, we will not be opening your entire project to try and find a solution. Plenty of others have. In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.

duh. Too many late nights Thanks In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.

You're missing the point. When you buy a third party control, like say from Infragistics, and you use it in your app, when you write your own theme the third party control respects it. I'm trying to understand how to make my control work the same way In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.

OK, I don't get what's wrong here. Here's the CustomerName in my CustomerView Here's the VM private void Customer_PropertyChanged(object sender, PropertyChangedEventArgs e) { IsChanged = true; ValidateCustomerName(); } private void ValidateCustomerName() { ClearErrors(nameof(Customer.CustomerName)); if (string.IsNullOrWhiteSpace(Customer.CustomerName)) { AddError(nameof(Customer.CustomerName), "The Customer Name cannot be empty."); } } When I clear out the CustomerName field, the ValidateCustomerName method fires, and the error is added to the errors collection. I just don't see the error text on the UI. However, if instead of binding to Customer.CustomerName, if I put a string property on the VM called CustomerName and use that, then I see the error text. In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.

Quote: GetErrors method returns an IEnumerable that contains validation errors for the specified property (when the propertyName parameter isn’t equal to null or empty string) or for the entire entity (when the propertyName parameter is equal to null or empty string) If you want to validate multiple properties of your entity, you need to return the errors when the GetErrors method[^] is called with a null property name. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Huh? That's even momre confusing In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.

Breaking change: WinForms and WPF apps use Microsoft.NET.Sdk - .NET | Microsoft Learn[^] Make sure you have the correct Sdk, the correct TargetFramework, and the UseWpf properties in your project file. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

You don't need to change the zorder to put it "on top"; you just span the whole grid and then position it the way you want and add it to the (XAML) visual tree last. Or put a canvas behind it for abolute positioning. The button can be placed anywhere relative to the progress "widget" using the same priciples. As for "hit testable", you can "swallow" clicks anytime it simpifies things. (e.Handled = true or false). (If you can "close" the widget, it begs the question: how do you open it. Maybe the button should be on a top or side "command bar": an enable / disable toggle). "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

It's a dependency, so I'd be inclined to inject the repo rather than the context. :) NB: Entity Framework supports asynchronous database queries, so it would be better to offer a FindAsync method on the repo, and get rid of the Task.Run call. public class ApplicationSecurity : IApplicationSecurity { private AppSecurityRepository _userRepo { get; } public ApplicationSecurity(AppSecurityRepository userRepo) { ArgumentNullException.ThrowIfNull(nameof(userRepo)); \_userRepo = userRepo; } public async Task LoginAsync(CredentialsEntity credentials) { var user = await \_userRepo.FindAsync(x => x.UserName == credentials.UserName); if (user is null) return null; return Cryptography.VerifyHash(credentials.Password, user.Password, user.Hash) ? user : null; } } NB2: Why does your user entity have both a Password and a Hash property? I'd expect to see a "protected password" property, and possibly a "salt" property, depending on whether the salt is stored as a separate column or combined with the password hash. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Wonderful. Thanks In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.