Using AssemblyFileVersion To Filter Builds
martincostello
Posts: 21
We are looking at versioning our .NET assemblies in the same way as the .NET Framework assemblies are versioned. Therefore this would mean:
where X is the build number.
This allows us to track our builds changing via the AssemblyFileVersion attribute, but means that the assembly's strong name doesn't change between builds so we don't need to worry about continuously updating configuration files (e.g. that reference full type names with version strings in them) for every build during development.
However, it appears that SmartAssembly is using the AssemblyVersion attribute to group together the builds, meaning that all error reports for every build appear to come from the same build, even though they didn't.
Is there a way to get SmartAssembly to report the build number from the AssemblyFileVersion attribute (or even AssemblyInformationalVersion), rather than the AssemblyVersion attribute?
Thanks,
Martin
[assembly: AssemblyVersion("1.0.0.0")] [assembly: AssemblyFileVersion("1.0.0.X")] [assembly: AssemblyInformationalVersion("1.0.0.X")]
where X is the build number.
This allows us to track our builds changing via the AssemblyFileVersion attribute, but means that the assembly's strong name doesn't change between builds so we don't need to worry about continuously updating configuration files (e.g. that reference full type names with version strings in them) for every build during development.
However, it appears that SmartAssembly is using the AssemblyVersion attribute to group together the builds, meaning that all error reports for every build appear to come from the same build, even though they didn't.
Is there a way to get SmartAssembly to report the build number from the AssemblyFileVersion attribute (or even AssemblyInformationalVersion), rather than the AssemblyVersion attribute?
Thanks,
Martin
Comments
Nope, it's always going to use the AssemblyVersion attribute when it rebuilds the assembly. I suppose there is an assumption that all three of these things would match.
I believe we have a feature request in about changing this.