Version management

[Jean-Francois Cantin]

Hi ,

we'd like to manage our dll's versions. When we change version in the
assembly file, it looks like if we have to rebuild all dependents files,
even if the modified file still compatible. It seems we have to rebuild all
the dependencies of the modified file, and the dependencies of the
dependencies of the modified file, and so on.

Is that the solution ?!
We don't use the GAC's functionalities, we leave all DLL in the principal
application folder.

Thanks

Jeff

[CJ Taylor]

I'm still confused.... you can get version information out of the
Reflection namespace. but as for recompling, yeah... .NET thinks its a
different version, therefore, needs to rebuild itself to be compatible. Or
something... I'm sick this morning so if I don't make sense, its the
benedryl compiling...

So yeah... wait... I just said benedryl compiling... what a twit I am.. see
what this stuff does. Anyways, yeah, you have to recompile on version
change, this is that whole DLL Hell issue..
"Jean-Francois Cantin" <je*****************@expertisa.com> wrote in message
news:um**************@TK2MSFTNGP11.phx.gbl...

Hi !

We'd like to track all customer's version by using this property.

Jeff
"Jeremy Cowles" <jeremy.cowles[nosp@m]asifl.com> a écrit dans le message de news:bz********************@twister.tampabay.rr.co m...

we'd like to manage our dll's versions. When we change version in the
assembly file, it looks like if we have to rebuild all dependents files, even if the modified file still compatible.

If the code is still compatible, why are you changing the version?
~
Jeremy

[Jeremy Cowles]

> We'd like to track all customer's version by using this property.

Yes, but if the customers version is compatible, what difference does a
number make? Again, the version numeber should only change when
compatiblity is broken, if you are using the version number for some other
reason, then you should be shot, in cold blood while you sleep (j/k).

HTH

~
Jeremy