I have a Visual Studio project that references an assembly that I also created. Below is a screen shot of the properties of my assembly reference in the project. When I update my assembly version to 1.1.0.0
, my project fails, and I am thinking this property is the issue.
Since the Version
attribute says 1.0.0.0
, does this mean it will always look for my assembly that has a version of 1.0.0.0
? And incrementing my version to 1.1.0.0
will cause my project to not see the assembly at all?
You have 2 versions of strongly named assembly. It is by design behavior for other projects that where compiled against one version of such assembly to fail to load assembly with different version. The reasoning is that version change denotes API change. Otherwise it would be in-place update with the same version - so older code may not be able to function correctly with newer DLL.
Options:
Side note: depending on if the assembly in question is for internal (you control all projects using the assembly) or external consumption you may need to do more work on ensuring backward compatibility and proper deprecation policy.
Publisher policy sample: from article linked above: