DLL versioning

  • Thread starter Thread starter Tony Johansson
  • Start date Start date
T

Tony Johansson

Hi!

Here is a text.
"With private assemblies you can still have versioning problem during
development time. For example if a component you use in your application
references version 1 of assemply x, and you use version 2 of assembly x in
your application, which version of the assembly is copied to your
application directoty. The answer depends on what assembly you have
referenced first."

I want to create my application in such a way that I can see that versioning
problem indeed can arise even in .NET and in my application according to the
text above.

I'm not sure I fully understand the text above.
What I know is that a create one assembly which is the exe file.
But how many dll assembly files does the text mean that must use to.

The text says *if a component you use in your application references version
1 of assemply x* does this mean that
the term a componenet here is an assembly dll which is using another
assembly dll which in this case is called assembly x.

//Tony
 
Hi Tony,

I simply write a small story, what could happen.

First you like a 3rd Party Assembly called ThirdParty.

You write a nice component called "MyDll" for which you are using
ThirdParty (in Version 1.0.0.0). So you have a dependency from MyDll to
ThirdParty 1.0.0.0 (it does not matter, what you used your component for
in this szenario.)

Some time later, you write a new Program. The Assembly is called MyEXE.
Because you like ThirdParty, you are using that (of course in the
lastest version, so you use ThirdyParty v2.0.0.0!)
Now you also find, that your old component MyDll is required.

So now you have dependencies to ThridPart 2.0.0.0 (from MyExe) and
ThridParty 1.0.0.0 (from MyDll).

==> You need 4 assemblies: MyEXE, MyDll, ThirdParty 1.0.0.0 and
ThirdParty 2.0.0.0

That is what I understood.

Konrad
 
Back
Top