I'm looking at figuring out how to deal with C# projects in open source sanely.
Visual Studio is both backwards and forwards incompatible, so everybody in the project has to use the same version, if somebody uses a newer version, it breaks support in the project file for everybody else on older versions. The project file generally has to be included in the repository under (a)GPL, because it almost always includes build info, settings, etc., so it counts as a build script or configuration file.
Are there other viable IDEs that can manage building and installer bundling and the whole nine yards?
Is there a way to make Visual Studio less of a pain and more compatible with older/newer versions of Visual Studio as well as other operating systems?
Is there is a way to decouple the build chain from Visual Studio to make it easier for developers in other toolkits or older versions of Visual Studio to develop and build and even package test installers?
In general, I'm looking to reduce how dependent a few C# projects I have management over are on certain development workflows. In my mind, an open source project should be accessible to anybody able to write code. How they write it, what program they write it in, should not be relevant, but C# and the Microsoft way seems to be running counter to this.