great stuff as always! Coming from WPF, seeing the new control be a resource dictionary is a bit weird... Doing it this way instead of just implementing a new control is so that the style can be shared with other Button classes, right?
It's more so the fact of inheriting the button so we don't have to lose button functionality, but maintaining the ability to customise the internal (content template) appearance. It's how actual Avalonia controls are made too so clearly just works the best this way
thank you for all !!!
great stuff as always! Coming from WPF, seeing the new control be a resource dictionary is a bit weird... Doing it this way instead of just implementing a new control is so that the style can be shared with other Button classes, right?
It's more so the fact of inheriting the button so we don't have to lose button functionality, but maintaining the ability to customise the internal (content template) appearance. It's how actual Avalonia controls are made too so clearly just works the best this way
Good job man, the thing is I don't mind topics like DI and Factory Pattern, but when i saw Classes.action I'm like dead lol, anyway, thank you.
Quite an OT but I'm really curious, what do you think about Blazor WASM, would you use it in production?
@@patrikbak8161 I already do for my retail business
can you please do a tuto about jetbrain rider + t4 template