Nikita Tsukanov

``` # sudo docker exec -i -t youtrack bash root@aca04681acb8:/home/youtrack# netstat -anp|grep LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN - tcp6 0 0 :::80 :::* LISTEN - tcp6 0 0...

I think replacing _currentAssemblyName with a struct holding individual name parts would be reasonable.

I think said parser could be used for the initial AST parsing in XAML compiler instead of XDocument one https://github.com/kekekeks/XamlX/blob/master/src/XamlX/Parsers/XDocumentXamlParser.cs

Our XAML compiler has quite simple architecture: 1) it converts parsed XML to some really basic AST 2) it resolves CLR types, so AST becomes more like XAML AST than...

The problem with snaps is that they try to isolate the application from the rest of the system (actually, unlike flatpak, snapcraft *does* have a isolationless-mode, but it's still complicated...

Recent Avalonia builds have support for global menu integration. Such menu can be declared like this: https://github.com/AvaloniaUI/Avalonia/blob/7dc95d5644bd3b14d2760cb664599e24fc239344/samples/ControlCatalog/MainWindow.xaml#L12 There is also `NativeMenu.IsMenuExported` attached property that becomes true when there is platform...

Note that this logic effectively skips libclang installed from libclang.runtime.ubuntu.18.04-x64 nuget package rendering said package to be useless.

>Modifying SharpGenOutputDirectory from its default will be deprecated. This is currently required for Rider to work properly

It does the trick for Avalonia solution (or so it seems), but not for an almost "hello world" one. No idea why.

>how to generate the code from the xaml without necessarily having information about the types when reading the xaml Have you considered implementing it as a post-build step? Just get...