Closed gitauto-ai[bot] closed 1 month ago
:white_check_mark: Build MSBuild.Version.Target 4.0.94 completed (commit https://github.com/guibranco/MSBuild.Version.Target/commit/b94e9a4553 by @gitauto-ai[bot])
:white_check_mark: Build MSBuild.Version.Target 4.0.102 completed (commit https://github.com/guibranco/MSBuild.Version.Target/commit/ff349636d6 by @gstraccini[bot])
:white_check_mark: Build MSBuild.Version.Target 4.0.107 completed (commit https://github.com/guibranco/MSBuild.Version.Target/commit/7d8194a5e7 by @gstraccini[bot])
Original issue: #12
What is the feature
Add support to use a single version file at the solution level instead of having separate version files for each project.
Why we need the feature
Managing version numbers across multiple projects within a solution can be cumbersome and error-prone. By centralizing the version information in a single file, we can ensure consistency and simplify the version management process. This will also reduce the overhead of updating version numbers in multiple places, thereby minimizing the risk of discrepancies.
How to implement and why
Create a Central Version File:
SolutionVersion.txt
.Modify Build Scripts:
SolutionVersion.txt
.Update Project Files:
Testing:
Documentation:
By following these steps, we can streamline the version management process and ensure consistency across all projects within the solution. """
Files to be modified:
SolutionVersion.txt
at the root level.build/MSBuild.Version.Target.targets
to read fromSolutionVersion.txt
.ContentFiles/Properties/Version.txt
andcontent/Properties/Version.txt
to use the central version file.README.md
to include instructions for the new versioning process.Test these changes locally