Matt Lacey

> After having added the RapidXaml.BuildAnalysis nuget package to the project which contains the xaml files, it does not produce any warnings when the project is built in VisualStudio 19...

Unfortunately, WPF with .Net Core 3.1 also uses an SDK style project format and so the BuildAnalysis doesn't know which files to check. This is why it is not reporting...

There's potential for performance issues here as may need to visit every attribute to look for such problems. Alternatively, may need - very generic rules - lots and lots of...

Doing this in the editor may be more efficient than doing it in an every element analyzer

Need to consider how to add these in ways that support localization too. From elsewhere: > "Support for the Windows Narrator is quite a job for adding ControlName.[using:Windows.UI.Xaml.Automation]AutomationProperties for each...

X-Ref: https://github.com/microsoft/axe-windows/blob/7e01ebfc1d74b8c72ebcc7894b43988a5421023f/docs/RulesDescription.md

X-Ref #242

I'm unaware of any VS extension APIs that will enable you to do what you described above. Even it if were possible to host arbitrary windows from other applications inside...

Do this for VSCT files only (at least initially) Note that this will impact build scripts that customize names for different build versions

As build script will now append a bracketed item to the end of some entries for some build scenarios, the localization tool & Resourcecs.resx file should also be updated appropriately.