Problem with references

  • Thread starter Thread starter Zanna
  • Start date Start date
Z

Zanna

Hi again :)

I would like to know how you manage the references in your projects and
solutions.
When I'm in debug I can have a solution with more projects, i.e: one exe and
two dll referenced by the exe.

Ok, when the dll are Ok I reopen the exe-project, but the references still
point to the project (that there is no longer), so I have to re-reference
the compiled dll... each time!

Add to this that it seems that VS.net sometimes when I do these
"reference-games" go crazy and does not recognize the referenced dll (no
intellisense, build hangs up...)... you understand that I need a sure way to
manage it.

Some tips?

Thanks
 
I don't really understand what you said but I could risk a guess.

if you reference a DLL directly in VS.NET (and if it is a private assembly
as opposed to one in the GAC), every time you change your project target
(Debug, Release, etc ..) VS.NET will just lost everything and you will have
to re-reference the DLL manually.
I guess that you have to cope with that (and alway work in Debug mode so the
problem don't come too often.)


Otherwise, if this is DLL of yours, you could have many project in a single
solution !
So just add all your project in the same solution and reference the Project
(NOT the DLL) and you would no such problem.
 
Lloyd said:
Otherwise, if this is DLL of yours
Click to expand...

Yes, this is what I mean.

you could have many project in a single
solution !
So just add all your project in the same solution and reference the Project
(NOT the DLL) and you would no such problem.
Click to expand...

You're right, but this can be good when the solution has 3/4 projects in
it... when you begin to have 10/20 projects in a solution... only the
loading will take 10 minuts :(
 
Back
Top