First of all, thanks for a great build task! I use it a LOT!
I recently had a situation where the path to some of my AssemblyInfo.cs files changed, and as a result, they no longer fell under the Root folder that I had configured, and thus were not updated. I didn't realize that this was a problem until I noticed in production that my assemblies had incorrect versions. It seems that versioning is important enough that I would want the build to fail if it didn't version things the way I anticipated.
It would be awesome if there was an (opt-in) feature that would allow the user to define a number of expected updates (not sure if this should be exact match, min, max, etc). If this criteria is not met, then the build should fail.
First of all, thanks for a great build task! I use it a LOT!
I recently had a situation where the path to some of my AssemblyInfo.cs files changed, and as a result, they no longer fell under the Root folder that I had configured, and thus were not updated. I didn't realize that this was a problem until I noticed in production that my assemblies had incorrect versions. It seems that versioning is important enough that I would want the build to fail if it didn't version things the way I anticipated.
It would be awesome if there was an (opt-in) feature that would allow the user to define a number of expected updates (not sure if this should be exact match, min, max, etc). If this criteria is not met, then the build should fail.