A project that uses two versions of Visual Studio (2013 e 2015)
can happen conflicts, for example, with file .csproj
or any other?
Note: I do not want to ignore this file in versioning.
A project that uses two versions of Visual Studio (2013 e 2015)
can happen conflicts, for example, with file .csproj
or any other?
Note: I do not want to ignore this file in versioning.
There is a question about differences in files . The 2015 files may contain information about things not recognized in 2013. So if you use specific things that can only be used in the 2015 project, it will contain things that may not be in the 2013 archive.
It is common for a 2015 user to make use of these commit features without much concern of what was added. It does the normal merge and may eventually have to do manually. Then a user takes this version and puts it in 2013 and tries to use it. Okay, you have a file with invalid information.
I can not say all the consequences of this. But it's a problem. It may be that VS 2013 removes this information, then when commitar goes without information that was needed in 2015. The 2015 user picks up and needs to clean the file. And you'll always stay at it.
Note that it may be that this extra information is not required in certain scenarios, so it may work OK. So it depends on the scenario.
It depends. If the project was created in VS 2013, there will be no issues with opening and editing in VS 2015 and maintaining versioning. Compatibility with Framework 4.5 is complete. However, if the project was created in VS 2015 .NET Framework 4.6, compatibility issues will exist.