- files relating to build settings. If the IDE has the ability to version style related artifacts independently of the project configurations, these should be treated as versioned artifacts.
The measure of whether the toolset works is whether the code meets the standards set by the build, and whether people using other tools can work easily with the code. Don't require a specific IDE tool set as long as the core development standards can be supported by the developers tool of choice.
Vendors need to think about the individual and team aspects of IDEs—ensuring that personal SCM tool settings are not checked in for example to make this possible.
The question of tools and standards can be controversial. The simplest solution that balances team and individual joy and productivity is to focus on whether the standard leads to more customer value, and to define standards in terms success criteria (how quickly to set up a workspace, features of the code, etc) rather than mechanisms.
There is a difference between consistency in important things, which is valuable, and conformity, which is often mistaken for consistency. Focus on delivering consistent results, and respect that a team will know how to get there.