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

File Reference / Project Reference

P: n/a
Hello Everyone,

I am having an issue with my solution and hoping that you all can suggest a
resolution. I have a common library that (A) that three other projects make
reference of (B,C,D). Project B is the windows forms application that also
references C and D. Additionally, C references D and D references C.

What is occurring is that project B cannot build telling me that a read-only
property is declared in project A which is not referenced in project B and
that I need to add a reference to project A in project B. Finally the error
states that this could be due to mixing a file reference with a project
reference and that I should try replacing the file reference with a project
reference.

After searching the web for answers, I have determined to individually build
each of projects (A, C and D) and reference the DLL's as a file reference.
This works great while I am only developing against the windows forms
application. Debugging the underlying projects now is difficult. I think
the issue really stems from the nested references, perhaps it is the build
order (even perhaps I should merge projects D and C).

I really do not see how I can change the make-up of my solution to avoid
this issue. Anyone have anything to add to this quandary?
TIA
Nov 1 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I stand corrected,

Project D references project C and project C doesn't reference project D. I
apologize for the confusion.

"AMDRIT" <am****@hotmail.comwrote in message
news:u1**************@TK2MSFTNGP04.phx.gbl...
Hello Everyone,

I am having an issue with my solution and hoping that you all can suggest
a resolution. I have a common library that (A) that three other projects
make reference of (B,C,D). Project B is the windows forms application
that also references C and D. Additionally, C references D and D
references C.

What is occurring is that project B cannot build telling me that a
read-only property is declared in project A which is not referenced in
project B and that I need to add a reference to project A in project B.
Finally the error states that this could be due to mixing a file reference
with a project reference and that I should try replacing the file
reference with a project reference.

After searching the web for answers, I have determined to individually
build each of projects (A, C and D) and reference the DLL's as a file
reference. This works great while I am only developing against the windows
forms application. Debugging the underlying projects now is difficult. I
think the issue really stems from the nested references, perhaps it is the
build order (even perhaps I should merge projects D and C).

I really do not see how I can change the make-up of my solution to avoid
this issue. Anyone have anything to add to this quandary?
TIA

Nov 1 '06 #2

P: n/a
I have resolved my conflict. It appears more coffee is required prior to me
going to work.

In solution properties, under dependencies; I was able to specify the inner
dependancies, low and behold, project B was not depending on project A even
though the reference was there as a project reference.

"AMDRIT" <am****@hotmail.comwrote in message
news:uw**************@TK2MSFTNGP02.phx.gbl...
>I stand corrected,

Project D references project C and project C doesn't reference project D.
I apologize for the confusion.

"AMDRIT" <am****@hotmail.comwrote in message
news:u1**************@TK2MSFTNGP04.phx.gbl...
>Hello Everyone,

I am having an issue with my solution and hoping that you all can suggest
a resolution. I have a common library that (A) that three other projects
make reference of (B,C,D). Project B is the windows forms application
that also references C and D. Additionally, C references D and D
references C.

What is occurring is that project B cannot build telling me that a
read-only property is declared in project A which is not referenced in
project B and that I need to add a reference to project A in project B.
Finally the error states that this could be due to mixing a file
reference with a project reference and that I should try replacing the
file reference with a project reference.

After searching the web for answers, I have determined to individually
build each of projects (A, C and D) and reference the DLL's as a file
reference. This works great while I am only developing against the
windows forms application. Debugging the underlying projects now is
difficult. I think the issue really stems from the nested references,
perhaps it is the build order (even perhaps I should merge projects D and
C).

I really do not see how I can change the make-up of my solution to avoid
this issue. Anyone have anything to add to this quandary?
TIA


Nov 1 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.