Resolve cls-namespace declaration
When you have a custom control in your page, the designer doesn't attempt to resolve the specified assembly. This goes for Xamarin Forms declarations as well.
Make it possible to define an assembly path where Studio will scan for required assemblies. That way we can easily use assets, static resources, controls, etc.
Of course I understand this will be a big challenge with loading and unloading of assemblies. But the lightweight approach of this designer is pretty appealing to me. I'm not able to use the Xamaring Preview in VS2017/2019 for instance, so I hoped this tool would make it easier to get a preview. Without support for custom assemblies in the namespaces I think the scope of the tool is very limited.
Thanks Theo, this isn't something on our roadmap at the moment. As a sandboxed app, we can't load dynamic assemblies. Our solution for this at the moment is to work towards open sourcing the tool. Then you can run it from Visual Studio and add in extra assembly references there.