My co-worker and I are working on a project together. I have some assemblies from her that we are both referencing.
When she doesn’t change any INTERFACE for the methods I want to call, but updates her version number, my code can’t run anymore.
This happens in a Silverlight Xap. When my xap is dynamically loaded, it complains. Because my xap contains assemblies that reference her OLD version. So it complains it can’t find it. Which it CAN’T.
So is there a way that I can NOT have her version referenced, but just reference the DLL? That way, she could just replace her assembly in my xap that she is using without having to pass me her assembly, me rebuild, me rezip, me send to her, she recompiles to include my xap.
As it is now, when I go on vacation, she can’t make a change to her code and change her version number because it would break my code which references the old version.
Why increase the version at all then? There’s a switch on references “any version” but it gives all kinds of problems, I wouldn’t advise using it. We generally use a hardcoded version (7.0.0.142 for some reason) here for all local builds and the build machine which does release builds sets/overrides the version.
Where is the switch? Do you mean the “Ignore Version” option? I tried that option and it looked like the generated assembly still had the version information for the referenced assembly. Maybe I’m not using it right.
How does the release build set/override the version?
Yeah, I think we will have to not change the version number so that it isn’t a problem.
It doesn’t. It emits a bit in the assembly that says “hey, I know I said version 1.2.3.4 but i really don’t care”. But it doesn’t work on all frameworks and has all kinds of problems. so yeah, my earlier advise works a lot better.