project-reference

What process does .NET use to locate a referenced assembly at runtime and is it different than the process used to locate a referenced assembly during compilation? I am specifically interested in the locations that are searched and their search order and any parameters/configuration settings that might affect the outcome. There are three types of references that can be made in a .NET application. This answer will only cover the first two in the list below. File references. Project references Service references. Every reference must be resolved. Reference resolution is the process of locating a

I have three projects in my .net solution. The main project and two class library projects. I have found out that I need to cross reference the class library projects. Can I do that? Is it safe or there are some considerations? The IDE won't let you when the projects are in one solution. There are subtle ways to confuzzle it. But then the solution cannot be built from scratch (i.e. Build + Rebuild) since the assembly reference isn't available yet. Refactor this, you probably want a 3rd assembly that both can reference. Circular references are possible (via the command-line and some tricks; not

In VS2010, Silverlight 4, .NET 4, I've got a WCF service and a Silverlight app, and Silverlight is accessing the class not with Add Service Reference but by sharing the contract. Naturally, this means I have the contract in a Silverlight class library, and the service has a project reference to that library. Strangely, this results in a /!\ icon on the reference, and a warning: The project 'SilverlightClassLibrary1' cannot be referenced. The referenced project is targeted to a different framework family (Silverlight) However, the reference works fine (I can use the interface in my Silverlight

As part of a solution containing many projects, I have a project that references (via a <ProjectReference> three other projects in the solution, plus some others). In the AfterBuild , I need to copy the outputs of 3 specific dependent projects to another location. Via various SO answers, etc. the way I settled on to accomplish that was: <MSBuild Projects="@(ProjectReference)" Targets="Build" BuildInParallel="true" Condition="'%(Name)'=='ProjectA' OR '%(Name)'=='ProjectB' OR '%(Name)'=='ProjectC'"> <Output TaskParameter="TargetOutputs" ItemName="DependentAssemblies" /> </MSBuild> <Copy

We use Team Foundation Server for our main project. Every time we add a new employee either onsite or offsite we always have to set up the references manually. Is it possible for TFS to copy/save/pass the dll's to the new user without having to install them every time? For example I add new functionality and install DocumentFormat.OpenXml to my project. Set up the code it runs and works fine on my machine, I publish it works just fine live. I check in everything into TFS. My co worker downloads the project attempts to build it and it errors out saying it doesn't know what to do with

I wish to test the core class of a plugin by directly referencing the plugin project and instantiating the plugin class. When I create a test Console App project and add a project reference to the plugin project, I get a warning icon (yellow triangle with exclamation mark) next to the reference in the References list. When I instead add a reference to the dll, the assembly build output of the plugin, I get no such warning. What could this warning be trying to tell me? As mentioned in the question's comments, differing .NET Framework versions between the projects can cause this. Check your new