project-reference

We Have a large VS solution using project references which is build by TFS Build like so: Solution - Project 1 - Project 2 - Project ... - Project N Because the solution is too large we have several smaller solutions which we use day to day: SubSolution - Project 1 - Project 19 The problem is that developers working on SubSolution find that it is not building because the project references could not be found, so they change the projects to use file references. This then goes on to break the TFS Build which cannot find these file references because they have not been built yet (Even though the

I have some projects in a Visual Studio solution that have ended up with project references that include the wrong GUID for the referenced project. (Possibly due to the referenced project being recreated at some stage) eg. Consider a project CoreProject.csproj with the following properties: <ProjectGuid>{93803F9C-8C65-4949-8D44-AB7A3D0452C8}</ProjectGuid> <OutputType>Library</OutputType> <RootNamespace>CoreProject</RootNamespace> <AssemblyName>CoreProject</AssemblyName> Another project includes a reference to this, but at some stage the GUID has changed and is now incorrect. <ProjectReference

Lets say I have two projects A and B. A depends on B. I can specify this in two ways: Include A and B in the same solution and specify B as a project dependency for A. This shows up in A's msbuild project as a "ProjectReference" node. Include a reference to the B's compiled dll as dependency for A. This shows up in A's msbuild project as a "Reference" node My question is, once I've build the assembly for A, is there a difference in the final output between these two methods. I tried creating a couple of simple projects which model this relation and tried a comparison - but different comparison

I have a weird error showing up in my project when it is open in the VS2012 IDE. Everywhere where I make use of another referenced project it suddenly says "Type or Namespace name could not be found" . And by "says", I mean it has the text underlined in red with the error when I hover over it. The intellisense doesn't work for that code. BUT (and here's the weird part), the errors do not show up in the error console and the project builds and runs fine. I can even debug and step through the code and it works perfectly fine. So at runtime the project is referenced fine but at design time the

Alrighty then, the short version of my question would be: What is the best way to handle project references in Git when you have projects that are shared across multiple solutions and how should my Git repos be organized? The long version is: We are a small dev team(5 developers) and currently we use TFS as our source control and build server and Visual Studio is our IDE of choice. I've always been keen on trying new things and trying to improve our dev environment so I decided to read up on Git to find out if it would be good replacement for the source control part of TFS. We just integrated

We have a .NET project consisting of multiple subprojects (around 20). There are several solutions, each containing only those subprojects which are relevant to the particular solution. To allow for arbitrary solutions, our subprojects never reference each other by means of project references, but rather by direct dll references. There is little tweaking of the csproj file, to make HintPath include $(Configuration), so Debug builds reference Debug dlls and Release builds reference Release dlls. All works great, but there are two major problems - one is annoying and another is really acute: VS