This project is read-only.

Versioning

Sep 26, 2013 at 10:24 AM
Asked by sdsmith
Moved from here.

It would be really helpful for me and the projects I have been working on if the SimpleInjector DLLs were also versioned, and possibly even strongly named. Each time we've downloaded a new version of the kit, the DLLs seem to have the version number 1.0.0.0 on them. This can make it tricky to chase down version-dependent behaviour when performing automated regression tests, for example, as well as knowing which versions to build against for particular releases of software. Please could the releases have versioning applied to the DLLs, preferably so that three of the four values in the .NET assembly version match the release number? Thanks!
Sep 26, 2013 at 10:25 AM
Hi sdsmith.

Where are you downloading the Simple Injector binaries from? All Simple Injector assemblies are always signed and versioned from day one. Both the NuGet packages and Codeplex download contain signed versions. You might not be using the official binaries that we ship.
Sep 26, 2013 at 1:22 PM
Actually on discussion, it turns out it is the file version that is remaining at 1.0.0.0 rather than the assembly version.
Sep 26, 2013 at 2:34 PM
That's true. File version is always 1.0.0.0. Is that a problem for you and why is that causing you trouble?
Mar 2, 2014 at 6:57 PM
Since Simple Injector v2.4 the Assembly File Version of the assemblies will always be in sync with the Assembly Version. So the problem should be resolved.
Marked as answer by dot_NET_Junkie on 3/2/2014 at 10:57 AM