If I understand these changes correctly, you can't use Noesis for more than 10 minutes at a time without buying a license -- even if you hadn't yet released your project? The thing is, even if you don't release your game, we need to support your development. There are other alternatives, like going...

I don't think you need the dictionary. Just set the JsonObject instance as the DataContext of the tree (setting the DataContext property) and bind it like this: <Button x:Name="button1" Content="{Binding Path=Name}" Width="100" Height="50"> <TextBlock Text=&qu...

The easiest way, if there are non conflicting resource keys, is putting everything in the same global resource dictionary (maybe splitting into several XAMLs that are merged together) and using a single set of providers. Providers can also be installed per assembly or scheme: void SetXamlProvider(Xa...

Could you please create a ticket for this?

It is possible to create new classes dynamically. This is what we are doing for C# and Blueprints in Unreal, we register new types in the reflection. Let me explain this a bit more, unfortunately this is a part not clearly documented and the API is a bit obscure at some points (this is probably the ...

Could you please create a ticket about this? I will find time to investigate what's going on.

This has been fixed today.

Thanks, please next time do not reopen closed threads.

I am not sure your fix makes sense. For example, NoesisXamlEditor is already unregistering views in OnDisable() method.

Unregistering a view before rendering with it seems suspicious to me.

Thanks for the ticket (#3278)!