References in projects for multiple users...

[=?Utf-8?B?Y2FkYTAzMTA=?=]

Hello there,

We have a solution which has 18 c# projects in it. These projects all have
references to DLLs stored in a common folder in our source control.

I notice that VS appears to store a "default" folder in the project
properties for a reference path - probably the one that was first used when
the reference was added to the project? This might be C:\_SOURCE for me,
since that's the folder I use on my PC.

I also notice that you can override this for every project, and it's stored
locally for the particular user, which I suppose is good, but it's a bit
painful when someone just wants to do File->Open from Source Control and
build this thing into their C:\MYSOURCE folder (which differs from the
default).

Is there some way to do something smart to get around this, other than
having all the developers use C:\_SOURCE as their dev folder? Or having them
go into every project and update their reference path settings? I tried
using an environment variable in there, but it ignored me...and the docs say
you can't use relative paths, either.

Thanks for any tips.

Chris

[Chris Dunaway]

Re: References in projects for multiple users...

On Jan 29, 10:08 am, cada0310 <cada0...@discu ssions.microsof t.com>
wrote:

Hello there,
>
We have a solution which has 18 c# projects in it. These projects all have
references to DLLs stored in a common folder in our source control.
>
I notice that VS appears to store a "default" folder in the project
properties for a reference path - probably the one that was first used when
the reference was added to the project? This might be C:\_SOURCE for me,
since that's the folder I use on my PC.
>
I also notice that you can override this for every project, and it's stored
locally for the particular user, which I suppose is good, but it's a bit
painful when someone just wants to do File->Open from Source Control and
build this thing into their C:\MYSOURCE folder (which differs from the
default).
>
Is there some way to do something smart to get around this, other than
having all the developers use C:\_SOURCE as their dev folder? Or having them
go into every project and update their reference path settings? I tried
using an environment variable in there, but it ignored me...and the docs say
you can't use relative paths, either.
>
Thanks for any tips.
>
Chris

If you have control of the projects that create each .dll, then you
should be using a project reference and not a direct assembly
reference. The only time you should reference a .dll directly is if
it is a 3rd party .dll or a .dll for which you do not control the
source.

See this reference for additional information, particularly chapter 4.

http://msdn.microsoft.com/library/de...ml/tdlg_rm.asp