By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,694 Members | 1,304 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,694 IT Pros & Developers. It's quick & easy.

Dependency practices

P: n/a
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.
Nov 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
"Earl" <br******@newsgroups.nospam> schrieb:
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.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

Nov 21 '05 #2

P: n/a
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]" <hi***************@gmx.at> wrote in message
news:eS**************@tk2msftngp13.phx.gbl...
"Earl" <br******@newsgroups.nospam> schrieb:
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.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

Nov 21 '05 #3

P: n/a
"Earl" <br******@newsgroups.nospam> schrieb:
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.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

Nov 21 '05 #4

P: n/a
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.

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...
"Earl" <br******@newsgroups.nospam> schrieb:
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.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

Nov 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.