Serge van den Oever [Macaw]

There is another way. If you add your referenced assemblies you your project as linked project items (as well as project references), Visual Studio will used the linked assemblies in preference to the HintPath and even AssemblyFolders.

This problem was killing me for a long time. I was in the situation where it would only build on another machine if I checked in the .user files (which is wrong!). I found that adding the assemblies as project items does the trick. In simple cases just drag and drop the assembly into the project, otherwize add them as links.

I hope that makes sense.

Yet annother application of VisualStudio\7.1\AssemblyFolders


Thanks.

SolGen: C# Solution Generator v0.1

Great Serge,

Just what we needed for our BizTalk Cruisecontrol build machine.

Thanks

The easiest solution is to modify the .csproj file in a text editor and change the value of the <HintPath> tag to be static instead of relative.  Visual Studio will not modify the path when the project is reloaded and you will no longer have the problem.

Thanks Serge,

Exactly what we needed to solve assembly referencing problems on a dedicated system that carrys out automated builds

Resolving Assembly References at Build Time

At build time, Visual Studio .NET resolves assembly references by searching the following

locations in the following order:

  1. Look for the assembly in one of the project folders. This assumes that you have added the

assembly to the project by using the Add Existing Item menu option. Project folders include any

folder displayed by Solution Explorer (except when Show All Files is in effect).

  2. Look in the folders listed in the ReferencePath attribute of the <Settings> element within

the project user options file. This attribute can contain a comma delimited list of folders.

  3. Use the <HintPath> element in the project file.

  4. Look in a set of folders identified by registry settings. These are the ones that contain

assemblies displayed on the .NET tab of the Add references dialog box. For more details, see

Using the .NET Tab of the Add Reference Dialog Box.

  5. Look for COM Interop assemblies in the obj sub folder beneath the project folder. For more

details, see Referencing COM Objects.

Notice that the reference path in the project user options file takes precedence over the hint

path established when you set a file reference.