DLL Versioning - can it be independent????

[Alex Stevens]

Hi All,

I'm trying to get around a problem that I'm having with versioning.

I have a DLL called Control.dll and it is at version 1.0.
I choose to inherit from one of the controls, and build my own control -
MyControl.dll and it is at version 1.0 also.

MyControl.dll is then used in MyApplication project.
Control.dll is also used in My Application project.

The original control is then modified very slightly and is incremented to
version 1.1.
Now I have to copy in the new reference to MyControl project, and recompile
the MyControl.dll and then copy them both to the application directory and
re-reference them, haveing deleted the old dll files.

This becomes very complicated, when you have other dll's which reference the
original Control.dll aswell, like the application!
Is there anyway that you can force a DLL (in this case MyControl.dll) to use
whatever version it finds in it's execution directory???

Thanks

Alex

 

[One Handed Man \( OHM - Terry Burns \)]

in the config file, set the version to 1.0.0.0 instead of 1.0.* etc

--
OHM ( Terry Burns ) * Use the following to email me *

Dim ch() As Char = "ufssz/cvsotAhsfbuTpmvujpotXjui/OFU".ToCharArray()
For i As Int32 = 0 To ch.Length - 1
ch(i) = Convert.ToChar(Convert.ToInt16(ch(i)) - 1)
Next
Process.Start("mailto:" & New String(ch))

 

[Guest]

Is the project MyControl.dll contained in your solution? The Visual Studio
IDE will keep everything synchronized. Since MyControl is part of the
solution it will recompile it recompile as needed and since it is part of the
solution any other project that references it will automatically "point" to
the correct version.

Try to keep all your projects that relate to a solution in the same
"Solution" and you should have few if any versioning issues.

HTH
Rob

 

[David Browne]

Hi All,

I'm trying to get around a problem that I'm having with versioning.

I have a DLL called Control.dll and it is at version 1.0.
I choose to inherit from one of the controls, and build my own control -
MyControl.dll and it is at version 1.0 also.

MyControl.dll is then used in MyApplication project.
Control.dll is also used in My Application project.

The original control is then modified very slightly and is incremented to
version 1.1.
Now I have to copy in the new reference to MyControl project, and
recompile
the MyControl.dll and then copy them both to the application directory and
re-reference them, haveing deleted the old dll files.

This becomes very complicated, when you have other dll's which reference
the
original Control.dll aswell, like the application!
Is there anyway that you can force a DLL (in this case MyControl.dll) to
use
whatever version it finds in it's execution directory???

You are incrementing the AssemblyVersion. The AssemblyVersion is not for
keeping track of your changes and fixes. The AssemblyVersion is _only_ for
controling assembly binding behavior. You increment the AssemblyVersion
_only_ when you want to force referencing assemblies to use the old version
side-by-side or recompile against the new version.

For tracking your changes independant of the binding behavior use
AssemblyFileVersion.

David