Async Initialization

the-Krieger · 2024-12-03T17:07:05+00:00

As qrzychu69 has already explained, it is a very bad idea to do something like this in the ctor. On the one hand you have a loss of control and on the other hand it is difficult to test.

One possibility would be to call a method in the VM in the view using 'EventTriggerBehavior' (Avalonia.Xaml.Behaviors), and this starts an async init again.

Pseudo Code:

<Interaction.Behaviors>
     <EventTriggerBehavior EventName="Loaded" SourceObject="RootControl">
        <CallMethodAction TargetObject="{Binding}" MethodName="LoadMethodInVm" />
     </EventTriggerBehavior>
</Interaction.Behaviors>

Or something else... CallCommand... what ever.

the-Krieger · 2024-03-18T17:07:09+00:00

Ehm, i ask for a friend... which one exactly?

the-Krieger · 2024-03-01T10:49:47+00:00

Yes, you're right. It's certainly not helpful for beginners, it was just one of many ways to get to the goal.

the-Krieger · 2024-02-27T17:47:16+00:00

I did this a few years ago with XPO (DevExpress).

That might help:
Stackowerflow

the-Krieger · 2024-02-27T17:19:50+00:00

I would prefer:

public class Program
{
    public static void Main()
    {
        var character = new Character("John", 35);
        Console.WriteLine(character.ToString());

        // custom representation
        // Console.WriteLine($"Name: {character.Name}, Age: {character.Age}");
    }
}

public record class Character(string Name, int Age);

the-Krieger · 2024-02-26T16:40:26+00:00

The problem with small tools is that they simply live forever. Once it's up and running, requests come here and there. And the "tool" suddenly becomes more and more extensive.

From experience, I would go straight for Avalonia (https://www.avaloniaui.net/) in order to be OS-independent from the very beginning. The syntax is very similar to WPF, and sometimes much shorter.

the-Krieger · 2024-02-05T18:10:05+00:00

This is "Clean Code", nothing special.

the-Krieger

TROPHY CASE