Version Management

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jean-Francois Cantin - 08 Sep 2003 15:32 GMT

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

Reply to this Message

Vince Henderson - 09 Sep 2003 22:31 GMT

Check out using an application config file to redirect your versions if you
don't want to recompile. The information is in the Framework SDK docs (or
on MSDN). See the topic marked Assembly Binding Redirection. That will
give you the information you need to generate a config file.
This technique is particularly useful during the development cycle, but we
do recommend you do the whole stack recompile before shipping your apps.
Experience shows this is easier to understand and debug after the product
has been in the wild for a while.

Vince

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

--------------------

| From: "Jean-Francois Cantin" <jeanfrancois.cantin@expertisa.com>
| Subject: Version Management
[quoted text clipped - 26 lines]
|
| Jeff

Vince
Common Language Runtime

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Phil Wilson - 10 Sep 2003 18:27 GMT

Could use the file version (AssemblyFileVersion) instead of AssemblyVersion for
your management?

Signature

Phil Wilson [MVP Windows Installer]
----

> Hi ,
>
[quoted text clipped - 11 lines]
>
> Jeff

Reply to this Message

PhallGuy - 22 Sep 2003 01:43 GMT

Hi Jean,

We use an AssemblyFileVerison for minor updates so that we don't have to
rebuild all the dependant assemblies. We have our full policy online that
we've suggested that others use at
http://www.xheo.com/Products/FrameworkCompatibility.aspx

- Paul Alexander

> Hi ,
>
[quoted text clipped - 11 lines]
>
> Jeff

Reply to this Message

Version Management

Free Magazines