Rethinking the project principles

[mrlacey]

On the main readme, you'll find the "principles guiding this project"

For easy reference, they are:

• Developers using XAML deserve the best tools possible.
• Doing something is better than doing nothing.
• Everything that is output should be configurable.
• C# and VB.NET are supported equally.
• The toolkit won't do things that Visual Studio can already do. (Without very good reason.)
• The toolkit can't generate the final XAML as every app requires unique customization.
• This toolkit is focused specifically on tooling for working with XAML. It will not include controls, etc.

As I think about reinvesting some time in this project, I feel that revisiting the above is also worthwhile.

I plan to leave the current VS2019 versions as they are and start again without the history of the project controlling what comes next but informing it.

My current thinking is that the Editor Extras and functionality relating to XAML Analysis will come to VS2022, but XAML Generation will come later (if at all). If it does, VB.NET support will also likely be dropped. Sorry VB folks, but I just don't see the usage and demand. If you're willing to spend some money to change this, please get in touch.

I may likely start with some entirely new functionality...

I'm also seeing many potential ways to help developers use XAML and make XAML-based development easier beyond providing isolated tools. Yes, libraries are coming...

The revised project principles will probably be:

• Developers using XAML deserve the best tools possible.
• Doing something is better than doing nothing.
• Don't force developers to work a particular way or use a specific framework.
• Everything that is output should be configurable.
• Don't do things that Visual Studio or other tools, or libraries can already do. (Without very good reason.)

thoughts?

[tomuxmon]

Personally interested in XAML Analysis, and the ability to create custom analyzers. Something similar we have with Roslyn.

[mrlacey]

Custom Analysis is already supported: https://rapidxaml.dev/custom-analysis
It was highly inspired by Roslyn analyzers (& code fixes) but with an aim for increased simplification.

In the rewrite for support of VS2022, I've encountered a possible need to rewrite this though. Or at least to make a big change to extend functionality.
Details are mostly in my head though. Sorry if you want more details. I can document thoughts if/when necessary/appropriate.