AssemblyInfo generation skipped on incremental build even if Version/VersionSuffix changes #967
Steps to reproduce:
detailed log contains:
The assembly info is generated only once and only contains
Since the inputs of
I think you're thinking in the right direction, though there's no easy way to deal with property changes from the command line in MSBuild in general. We added some things for MSBuild 15 that could probably be assembled in a reasonable way, mostly in microsoft/msbuild#1328.
Some context: this is nasty when building twice per CI build (one "CI drop" with a suffix and one "potentially releasable" package without suffix so a chained release definition might publish the suffix-less build).
I'm wondering if
String.GetHashCode is not good enough, https://msdn.microsoft.com/en-us/library/jj152924(v=vs.110).aspx is on by default in CoreCLR.
In general, an incremental build with different properties is risky, every target is potentially vulnerable to bugs like this.
We should fix this, but I would still caution against a CI setup as described where RTM packages (and only RTM packages!) are shipped from incremental builds.
I've had some success prototyping the hash approach by creating a
If that is the way forward, I'd be happy to contribute it in a proper PR. Just have the following design questions: