Dependency practices

[Earl]

Is it poor practice to have one custom library depend on another custom
library? For example, my data manipulation library depends on my replication
library, which in turn pulls serial data out of an XML file.

 

[Herfried K. Wagner [MVP]]

Is it poor practice to have one custom library depend on another custom
library? For example, my data manipulation library depends on my
replication library, which in turn pulls serial data out of an XML file.

Not necessarily.

 

[Earl]

Thanks Herfried ... that was what I suspected "it depends".

Followup question: if I change the contents of a referenced custom .dll, do
I have to remove and re-add the reference in the referring project or will
it pick up the version change?

 

[Herfried K. Wagner [MVP]]

Followup question: if I change the contents of a referenced custom .dll,
do I have to remove and re-add the reference in the referring project or
will it pick up the version change?

I suggest to add both projects to the same solution and use a project
reference instead of referencing the DLL directly.

 

[Earl]

Thanks for the advice, unfortunately there are business reasons why the .dll
files must be kept separate. It appears right now that I have to remove the
reference and re-reference when I make a change.