Eliminate 2013 references in *.2015.vcxproj files

[GreyMerlin]

Eliminate 2013 references in *.2015.vcxproj files

Symptom:

Attempting to compile this FreeImage solution with VS2015 fails because the VS2013 toolset is not installed.

Discussion:

• Three of the projects have direct references to the Visual Studio 2013 toolset (one with WinXP extensions). These were easy to update directly with the VS2015 IDE. After that, all indication on the various project property dialog windows indicates that the projects were correctly configured for VS2015.

• However, the solution still would not compile.

• Seven of projects include various 'Reference Projects', which are additional, internal, linkages to other inter-dependent projects. This is in addition to the normal linkage to the projects that are explicitly part of the solution.

An example of 'Reference Projects' (this is just one of the seven projects) ...

• Within the text of the xxx.2015.vcxproj files, these 'Reference Projects' still refer to the older xxx.2013.vcxproj files, thus requiring the co-existence of the VS2013 compiler.

Solution:

• Three projects were directly updated via the VS2015 IDE to use the VS2015 toolset.

• I could find no way to update the other seven projects' references directly via the IDE. Possibly deleting and re-adding them would have worked, however that seemed tedious and error-prone. By using the NotePad++ text editor on each of the xxx.2015.vcxproj files, I found all literals .2013. and changed them to .2015.

• The entire solution now compiles correctly with the VS2015 compiler, without the existence of the VS2013 toolset.

Testing:

• All configurations of the solution (Win32/x64 and Release/Debug) compile correctly, producing appropriate FreeImageLib.lib or FreeImageLibd.lib files.
• Using these new .lib files, the WinIMerge solution compiles correctly in all configurations, producing (among other things) the proper WinIMerge.dll files.
• The WinMerge-v2 project runs correctly in all configurations using these new WinIMerge.dll files.
• Testing was done on Win10. I have no way to test Windows XP, Vista, 7, 8 or 8.1, but I believe that there are no "breaking changes".

[sdottaka]

Merged. Thank you!

[GreyMerlin]

Thank You !!