feat: Avalonia Properties Page

[workgroupengineering]

What does the pull request do?

Add Properties Page to project properties in VS.

• Compiling
  • EnableAvaloniaXamlCompilation
  • AvaloniaXamlIlVerifyIl
  • AvaloniaUseExternalMSBuild
  • AvaloniaUseCompiledBindingsByDefault
  • AvaloniaAccessUnstablePrivateApis
• Debug
  • AvaloniaXamlIlDebuggerLaunch
  • AvaloniaXamlReportImportance
• Name Genenrator
  • AvaloniaNameGeneratorIsEnabled
  • AvaloniaNameGeneratorDefaultFieldModifier
  • AvaloniaNameGeneratorFilterByPath
  • AvaloniaNameGeneratorFilterByNamespace
  • AvaloniaNameGeneratorViewFileNamingStrategy

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

• Added unit tests (if possible)?
• Added XML documentation to any related classes?
• Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

[robloo]

This is really neat! I never knew this could be done

[workgroupengineering]

This is really neat! I never knew this could be done

You are right, and it is possible to add the controls to the Toolbox but currently only Winform and WPF are supported.

I'd like to try to implement the Toolbox for the VS Avalonia extension, but I'm waiting for the VS Code extension to be made public.

[avaloniaui-team]

You can test this PR using the following package version. 11.0.999-cibuild0038502-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

[avaloniaui-team]

You can test this PR using the following package version. 11.0.999-cibuild0038534-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

[avaloniaui-team]

You can test this PR using the following package version. 11.0.999-cibuild0038593-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

[workgroupengineering]

@maxkatz6 Should i made other changes?

[maxkatz6]

LGTM, but I don't know if we want to merge it now or later for 11.1 or to a special 11.1 branch
@kekekeks

[cesarchefinho]

LGTM, but I don't know if we want to merge it now or later for 11.1 or to a special 11.1 branch @kekekeks

better merge now and provide better tooling for users on 11.0 too

[robloo]

I realize the focus is on bug-fixes and stabilization only for now. But this PR doesn't change anything code-related and only makes these project properties easier to discover and configure. There should be no ill-effect and will even help new users. Seems like a good candidate to merge sooner rather than later.

[avaloniaui-team]

You can test this PR using the following package version. 11.0.999-cibuild0038882-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

[avaloniaui-team]

You can test this PR using the following package version. 11.0.999-cibuild0038894-beta. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

[TomEdwardsEnscape]

When I try out the latest nightly build, which contains these changes, I get an endless parade of binding errors. It turns out that in each project, the new property page has AvaloniaUseCompiledBindingsByDefault checked.

This feature isn't enabled by default in 11.0.4. This seems like an unintentional change.

[workgroupengineering]

@TomEdwardsEnscape Thanks for the feedback, I'll look into it.