Avalonia.FuncUI v1.0 release

Opening this issue to track the work needed before we release the non-pre-release version of v0.6

Before release

• Wait for Avalonia v11 to be released (duh!)
• Adapt to “The Great Interface Removal” introduced in https://github.com/AvaloniaUI/Avalonia/pull/9553 (Addressed in #246)
• Remove mention to old docs site in README and point all of them to the docs site under Avalonia’s domain
• Create a Migration Guide in the docs
  • Interface removals (#246)
  • Changes for Elmish v4 (#248)
  • Package name changes (#242)
• Migrate templates to new version (includes adding dependency of the newly separated Avalonia.Themes.Fluent)
• Deprecate Avalonia.FuncUI.DSL package from Nuget. See here. I believe this can only be done by you @JaggerJo?

Since 4564a6d98c55e3b9e0437e4d8aecfb41bfed9b5b the DSL project lives inside of the main FuncUI package and upgrading from a previous version that has the a package reference to the DSL makes all this funky errors where half of the imports seem unused and all the controls stop working:

The fix is, of course, to remove the package reference to the DSL but I think we should make this clearer to the user.

After release

• Create documentation for new inline components
• Party? 🎉

[JaggerJo]

I guess it’s time to ship it 🚀

[sleepyfran]

fyi, the Avalonia change at https://github.com/AvaloniaUI/Avalonia/pull/9553 has removed a load of interfaces that FuncUI uses, apparently in favour of just using the base classes instead, which is an ever so slightly breaking change over here.

I had a quick go at changing the lib to just use the base clases instead of interfaces and the control catalogue seems to still run, but I didn’t check anything beyond that

Oh, boy. Thanks for the heads up! I guess a search and replace of I.* should do the trick 😆 Adding that to the checklist