Drops gulp for Powershell and applies versioning to csproj files rather than AssemblyInfo.
@benjanderson Please have a look at the "version" elements in the csproj files. I opted to drop the conditional version element and applied the Major.Minor.Patch based on a version.json file I added to the \build solution folder. I felt that keeping the version explicit will likely have benefits in the future as we (between teams) have need of communicating that changes have been made, what type of changes (non-breaking / breaking) and be able to document in release notes what was added to each point version - including patch versions.
From what I could tell the versioning scheme should work with the packing methodology you're introducing and to that end, the Powershell script also updates the nuspec file you added to the API projects root.
The script takes a buildNumber parameter (same process we're currently using in PB and SharedLibraries).
Drops gulp for Powershell and applies versioning to csproj files rather than AssemblyInfo.
@benjanderson Please have a look at the "version" elements in the csproj files. I opted to drop the conditional version element and applied the Major.Minor.Patch based on a
version.jsonfile I added to the \build solution folder. I felt that keeping the version explicit will likely have benefits in the future as we (between teams) have need of communicating that changes have been made, what type of changes (non-breaking / breaking) and be able to document in release notes what was added to each point version - including patch versions.From what I could tell the versioning scheme should work with the packing methodology you're introducing and to that end, the Powershell script also updates the nuspec file you added to the API projects root.
The script takes a buildNumber parameter (same process we're currently using in PB and SharedLibraries).