Currently we're using vcxproj files and a Visual Studios sln file to drive the Windows runner and plugin builds. Another option that has come up is using CMake.

Pros:

• It is text-based, making it far easier for someone who doesn't have VS experience (which I expect will be the vast majority of Flutter developers) to understand and edit. Also easier to manage in version control.
• We'll be using it for Linux, so this would slightly reduce the number of build systems a Flutter developer might need to interact with.
• It's used by vcpkg, which may end up be the plugin dependency management system for plugins.
• Visual Studio has CMake integration, so it should still give a reasonable experience in the IDE (we'd want to test that out with a project)

Cons:

• It's an extra dependency (although it can be installed via VS, so this should be straightforward using our existing component check system).
• For people with Windows development experience (e.g., potential plugin authors) it may mean a new build system to learn rather than what they are already comfortable with.