Documentation VS ikvm

There is the current docs, and the v11 docs

I assumed you were building your project using the Avalonia template which would set you up for creating an MVVM project. If you were following the tutorial in your original post then it should be set up as MVVM. Try running some of the tutorials in the Avalonia Documentation to get a better feel for building in Avalonia.

There were no docs on the MaskedTextBox, only some of WPF so I decided to be a good boy scout and write them myself with my second PR on AvaloniaDoc.

Docs content are huge help for maintainers, mostly because they are developers, they are not interested in writing docs, but fixing bugs. Even Avalonia which is great project on itself, suffer from lack of docs. For example https://github.com/AvaloniaUI/Documentation/issues/304 where they have functionality which is supported, but it is not documented anywhere. If you novice, Avalonia hard to get started, if you know WPF already, that's relatively easy.

If it's written on Java or any JVM language it might be easier to use ikvm.net and use the library directly from C#. It even supports using maven libraries out of the box by simply adding to your csproj or even jar files if needed.

This reminded me of the IKVM project: https://github.com/ikvm-revived/ikvm

This is a converter that allows Java bytecode to run on the .NET Framework.

It allows horrific, unnatural things such as a C# class that is a derived type from a Java class!

One of my more advanced build systems: https://github.com/ikvm-revived/ikvm/blob/develop/IKVM.dist.msbuildproj