Richard Bennett
Richard Bennett
I'm unsure if this'll help anyone... but it seems as-if you execute your blazor app using the following command, it fires as you'd expect it to: `electronize start .\source\Your.Host\Your.Host.csproj /PublishSingleFile...
I'm just getting into building the view out, and adopting other values from the ViewModel. Let me see what happens as I continue.
It's looking like it's the button click events that are not binding unless I use the cal:Message.Attach method to bind out. Properties seem to be bound appropriately.
Verbatim from screen: ``` Xaml ```
It is not. I have never done that before, and hadn't realized that the labels had shared a similar convention to the buttons.
Ok... but what does this mean? Do I need to embed the controls within something specific under the base metro dialog control in order to provide the right hierarchy for...
This seems to work. ``` C# public IEnumerable Handle(AggEvents.ShowDialog message) { var screen = _LifetimeScope.Resolve(message.View); if (screen != null) { var view = ViewLocator.LocateForModel(screen, null, null) as BaseMetroDialog; yield return...
Yes, once I rolled over to this new way of building the code, all the x:name="..." works as expected. Now I'm just trying to understand the "why" of it.
I think, at this point, we'll call well-enough alone :) Thanks for being a sounding board @nigel-sampson!
working code - 74 elements. non-working code - 0 elements.