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

references adding themselves based on references from other projects referenced

P: n/a
My main project really only has one reference in it that is needed outside
of the System references. It references a DLL Class Library which has
references in that DLL library to other references like crystal reports and
such... I have noticed that my main project though randomly adds copies of
the referenced items in the DLL to the exe's reference list... why is it
doing this? it doesn't need the references, so why would it copy the
referenced project's references into itself?
Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Brian Henry" <no****@nospam.microsoft.com> schrieb:
My main project really only has one reference in it that is needed outside
of the System references. It references a DLL Class Library which has
references in that DLL library to other references like crystal reports
and such... I have noticed that my main project though randomly adds
copies of the referenced items in the DLL to the exe's reference list...
why is it doing this? it doesn't need the references, so why would it copy
the referenced project's references into itself?


Imagine two libraries (assemblies) 'A' and 'B'. Assembly 'A' exposes a
class 'Bar', and assembly 'B' references 'A' and contains a class named
'FooBar' which inherits from 'Bar'. When referencing 'B' both the type
'FooBar' and 'Bar' need to be made available, because 'FooBar' inherits
'Bar'.

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

Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.