Stop putting VS Version number in .sln file
Baking the VS Version number, especially when it's functionally insignificant like between Updates & CTPs of the same VS edition, causes nothing but headaches for teams with SCC.
Please stop doing this. If the schema of the SLN file changes in a way that's significant, use schema versioning or naming to handle it instead of baking the software version that last touched it in to the file.
@Costas apparently not: https://stackoverflow.com/questions/1033809/should-a-sln-be-committed-to-source-control
Couldn't this go into one of the files ignored by source control?
Mattias Flodin commented
This is low-hanging fruit. Come on, you guys at Microsoft must also be suffering from this. Aren't you using version control?
At least give me an option to stop this action. My version control history for the solution file is a ping-pong between developers with different VS versions. Tis a bit stupid that VS 2017 can open an old version and work with it, but it changes the SLN file. This is obviously an SLN file from an older version of VS... you're not adding value by changing the number.