Standardize Various Visual Studio File Names #29
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Standardize Various Visual Studio File Names
Symptoms
Within the various independant repositories that are associated with the WinMerge-v2 repo, the file names for build commands (
.cmd
), solution files (.sln
) and project files (.vcxproj
) are not cleanly standardized from one repo to the next. Some aspects of the repos are not really set up to handle multiple versions of VS. This becomes more noticable as we move toward migrating these repos to use the new VS2017 environment.Solution
This Pull Request is one in a collection of three, one Pull Request for each of the repositories:
If any one of these Pull Request are merged, then it is really necessary to merge the other two Pulls as well.
I have replicated this exact explanatory text identically into all three Pull Requests.
The repositories frhed and sevenzip are also components of the overall WinMerge-v2 project, but I have not (yet?) spent any effort to update these two repos to use VS2015. frhed appears to already use VS2015. sevenzip does not have VS solution or project files.
Likewise, I have not yet made any modifications to the Merge7z or ShellExtension solutions within the WinMerge-v2 repo. These were already setup to use VS2015 before I began modernizing the other solutions and projects.
Note
A number of files are committed that simply have changed file names. Git and GitHub handle this correctly, noting that the file name has changed. However, sometimes GitHub's file comparison still presents a full comparison of every line of the file, not simply the very few subsequently changed lines, making it hard to find those few changes. This confusion can be largly eliminated by looking at each single commit. A bit frustrating, sorry...
FreeImage
*.2015.sln
to*.vs2015.sln
*.2015.vcxproj
to*.vs2015.vcxproj
*.2015.vcxproj.filters
to*.vs2015.vcxproj.filters
.sln
and.vcxproj
files are updated appropriatly.Miscellaneous
.pdb
file is now copied into the finalDist\
folder for the two (x32 and x64) Debug builds.WinIMerge
WinIMerge.sln
toWinIMerge.vs2015.sln
*.vcxproj
to*.vs2015.vcxproj
*.vcxproj.filters
to*.vs2015.vcxproj.filters
.sln
and.vcxproj
files are updated appropriatly..sln
and.vcxproj
files of this repo.BuildBin.cmd
file toBuildBin.vs2015.cmd
. Update project references in this file from*.vcxproj
and*.2015.vcxproj
(into the FreeImage repo) to be uniformly to the new*.vs2015.vcxproj
.Miscellaneous
.gitignore
file is added.WinMerge-v2
*_2015.sln
to*.vs2015.sln
.*_2015.vcxproj
to*.vs2015.vcxproj
.sln
and.vcxproj
files are updated appropriatly.*_2015.vcxproj.filters
to *.vs2015.vcxproj.filters`BuildBin.vs2015.cmd
(copied fromBuildBin.cmd
) andBuildAll.vs2015.cmd
(copied fromBuildAll2.cmd
). Add these files to theWinMerge.vs2015.sln
file with previously existing.cmd
files.BuildBin.vs2015.cmd
file to use VisualStudio 14.0 (i.e. VS2015) and to use newWinMerge.vs2015.sln
file.BuildAll.vs2015.cmd
file to call the newBuildBin.vs2015.cmd
file.Miscellaneous
.gitignore
file patterns.