Consider incrementing the assembly version for source generator with each build

[sharwell]

It appears that the version number of this assembly is locked at 6.0.0.0. This can be problematic for VBCSCompiler during reference package updates, leading to dramatic reduction in compiler throughput (for Roslyn.sln, builds are about 3x slower). The fix for this solution is ensuring the assembly version number increases with each build for analyzer and source generator packages.

Originally posted by @sharwell in #58175 (comment)

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[sharwell]

See also microsoft/vs-threading#279

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

---

It appears that the version number of this assembly is locked at 6.0.0.0. This can be problematic for VBCSCompiler during reference package updates, leading to dramatic reduction in compiler throughput (for Roslyn.sln, builds are about 3x slower). The fix for this solution is ensuring the assembly version number increases with each build for analyzer and source generator packages.

Originally posted by @sharwell in #58175 (comment)

Author:	sharwell
Assignees:	-
Labels:	area-Infrastructure-libraries, untriaged
Milestone:	-

[ericstj]

@sharwell we should already have unique assembly versions for publicly shipping GA releases, including servicing. I've made ensuring this part of our servicing readiness plan: #58042.

It seems like you're suggesting that even for nightly builds we increment though. Let's consider that.

I can see an issue during previews when mixing / matching preview assets. This shouldn't be possible with ref-packs, but could be with the nuget package. For example: if someone has the Preview7 SDK installed, but then has one project where they reference the RC1 (or daily build) NuGet package: those would have the same assembly version but different content.

What does https://github.com/dotnet/roslyn-analyzers do? They should have a similar issue (inbox + nuget package). Maybe we can just follow their lead.

cc @eerhardt