I played with Visual Studio builtin profiling tools and now every time I check out any file this section automatically adds to my solution file:

    GlobalSection(Performance) = preSolution
        HasPerformanceSessions = true
    EndGlobalSection

I totally removed all profiling reports, then removed local copy of all source control files from this solution and update to latest. This section still in *.sln file after any checkout.

Other teammates who haven&#39;t used prfiler doesn&#39;t have this problem.
Has anyone any ideas?

How to force Visual Studio not to add GlobalSection(Performance) section?

I have some class libraries with a non-trivial amount of existing code. The class libraries currently target .NET 4.0. Is there any guidance on how to convert these libraries to be portable libraries? From looking at the .csproj, it doesn&#39;t appear that there are a lot of differences:

    &lt;Import Project=&quot;$(MSBuildExtensionsPath32)\Microsoft\Portable\$(TargetFrameworkVersion)\Microsoft.Portable.CSharp.targets&quot; /&gt;

and

    &lt;ProjectTypeGuids&gt;{786C830F-07A1-408B-BD7F-6EE04809D6DB};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}&lt;/ProjectTypeGuids&gt;

Is it a good or bad idea to try converting an existing class library to be a portable library?



Is there any guidance on converting existing .NET class libraries to portable libraries?

Realizing that this could be subjective based on the project at hand, I&#39;m looking for the &quot;best practice&quot; method of structuring a VS (Visual Studio) Solution.

Please feel free to edit this, comment on what you think might be incorrect, suggest alternatives, etc.  I&#39;d love to see this Community Wiki grow into a great resource for people just starting with VS Solutions.

Below is what I have working for me now (on my current project), however I know for a fact that there is some stuff in the wrong place.  *In my scenario, I&#39;m building a **Web Application** using **MVC 2***

Please post your idea of the ultimate solution structure so that we can get an idea of the &quot;best way&quot; / &quot;best practice&quot; (*whatever that means exactly*)

**IE:**  
How do you break up your DAL (Data-Access-Layer) / BLL (Business-Logic-Layer)?  
Do you put your repository layer and service layer inside your BLL?
If you&#39;re using MVC (Model-View-Controller), do you keep your controllers in the UI instead of the Core?  
Do you throw lots of stuff in your Utility/Miscellaneous folders, or do you break it apart even further?  
etc...

----

&gt; - **MySolution**  
    - **MySolution.Core**
      - **Authentication**
         - *this is where I have a POCO and a method to searialize the poco into the userData secion of the auth cookie*
      - **Base**
         - *here is where I keep my BaseController and by BaseGlobal*
      - **Controllers**
         - *all of my controllers (obviously)*
      - **Domain**
         - **DatabaseModels**
             - *contains my L2S .dbml file*
         - **JsonModels**
             - *models used to pass JSON objects to the veiw*
         - **Repositories**
         - **Services**
         - **ViewModels**
      - **Extensions**
         - *all extension methods*
      - **Filters**
         - *Action Filters*  
      - **Utilities**
         - **Apis**
             - *all third party API code goes in here*
         - **Badges**
             - *badge calculation goes here*
         - **MailClient**
             - *send plain text or html email using the classes in here*
         - **RoutingHelpers**
             - *contains a class to enable lowercase routes*
         - *also contains things that I don&#39;t know where else to put... IE: HTMLSanitizer, custom HtmlHelpers,UserInfo helper (IP address, browser, etc), DataConverter, etc* 
    - **MySolution.UI**  
      - **App_Browsers**  
      - **Assets**   
          - **Css**  
          - **Images**  
          - **Scripts**  
      - **Views**
      - **Global.asax** - *inherits from BaseGlobal*
      - **Web.config**

-----

**Screen Shots**  
![Core][1]![UI][2]

Please feel free to comment accordingly, or better yet, post your own version (answer) below.  I know that what I&#39;ve got isn&#39;t the best way.  

  [1]: http://i.stack.imgur.com/y34gc.png
  [2]: http://i.stack.imgur.com/t8uMn.png

The Ultimate Visual Studio Solution Structure

For the most part, you just take whatever Visual Studio sets it for you as a default... I&#39;m referring to the [BuildAction][1] property for each file selected in Solution Explorer. There are a number of options and it&#39;s difficult to know what each one of them will do.

  [1]: https://docs.microsoft.com/en-us/visualstudio/ide/build-actions?view=vs-2019


What are the various &quot;Build action&quot; settings in Visual Studio project properties and what do they do?

When I start a new ASP.NET project in Visual Studio, I can create an ASP.NET Web Application or I can create an ASP.NET Web Site.

What is the difference between ASP.NET Web Application and ASP.NET Web Site? Why would I choose one over other?

Is the answer different based on which version of Visual Studio I am using?


ASP.NET Web Site or ASP.NET Web Application?

My current solution for renaming the project folder is:

  - Remove the project from the solution.
  - Rename the folder outside Visual Studio.
  - Re-add the project to the solution.

Is there a better way?


How can I rename a project folder from within Visual Studio?

Visual studio has always annoyed me because (to my knowledge) you cannot create a solution first and then add new/existing projects to it.  The only way I know how to create a solution is to create a project and specify the solution name for it.

So, is there any way to start with a blank solution (.sln) in visual studio (any version)?

Is there any way to create a blank solution (.sln) file first and then add projects?

In Visual Studio, we can &quot;Add as link&quot; to add a link to a file in another project in the solution.

Is there any way to do this for entire folders, so that an entire folder in project A will be visible in project B, without the need to manually link to new items in that folder?

&quot;Add as Link&quot; for folders in Visual Studio projects

Being new to VS, how may I think of these two concepts, what is the difference?

Visual Studio Project vs. Solution

When I debug my project, I get following error:

&gt; &quot;Unable to copy file &quot;obj\Debug\My Dream.exe&quot; to &quot;bin\Debug\My Dream.exe&quot;. The process cannot access the file &#39;bin\Debug\My Dream.exe&#39; because it is being used by another process.&quot;

Using Process Explorer, I see that MyApplication.exe was out but System process still uses it although I stopped debug before.
Whenever I change my code and start debug it is going to happen. If I copy project to USB and debug, it runs OK.

Why? How can I fix this error?

I use Window 7 Professional. With Xp I have never got this error.

Error: Cannot access file bin/Debug/... because it is being used by another process

I am working on a game using Visual C++. I have some components in separate projects, and have set the project dependencies. How do I #include a header file from a different project? I have no idea how to use classes from one project in another.


visual c++: #include files from other projects in the same solution

Is it a best practice to commit a .sln file to source control? When is it appropriate or inappropriate to do so?

**Update**
There were several good points made in the answers. Thanks for the responses!

Should a .sln be committed to source control?

First, I know about this: https://stackoverflow.com/questions/51217/how-would-you-organize-a-subversion-repository-for-in-house-software-projects
Next, the actual question:
My team is restructuring our repository and I&#39;m looking for hints on how to organize it. (SVN in this case).
Here&#39;s what we came up with. We have one repository, multiple projects and multiple svn:externals cross-references

    \commonTools /*tools used in all projects. Referenced in each project with svn:externals*/
       \NUnit.v2.4.8
       \NCover.v.1.5.8
       \&lt;other similar tools&gt;
    \commonFiles /*settings strong name keys etc.*/
       \ReSharper.settings
       \VisualStudio.settings
    \trash /*each member of the team has trash for samples, experiments etc*/
       \user1
       \user2
    \projects
       \Solution1 /*Single actual project (Visual Studio Solution)*/
          \trunk
             \src
                 \Project1 /*Each sub-project resulting in single .dll or .exe*/
                 \Project2
             \lib
             \tools
             \tests
             \Solution1.sln
          \tags
          \branches
       \Solution2
          \trunk
             \src
                 \Project3 /*Each sub-project resulting in single .dll or .exe*/
                 \Project1 /*Project1 from Solution1 references with svn:externals*/
             \lib
             \tools
             \tests
             \Solution2.sln
          \tags
          \branches

To clear the vocabulary: Solution means single product, Project is a Visual Studio Project (that results in a single .dll or single .exe)

That&#39;s how we plan to lay out the repository. The main issue is, that we have multiple Solutions, but we want to share Projects among Solutions.
We thought that there is no point really in moving those shared Projects to their own Solutions, and instead we decided to use svn:externals to share Projects among Solutions. We also want to keep common set of tools and 3rd party libraries in one place in the repository, and them reference them in each Solution with svn:externals.

What do you think about this layout? Especially about the use of svn:externals. It&#39;s not an ideal solution, but considering all pros and cons, it&#39;s the best we could think of. How would YOU do it?

How do you organize your version control repository?

What is the significance of the ProjectTypeGuids  tag in a visual studio project?? When I created a WPF application, i am seeing two GUIDs in here. 

    {60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}**

Does these represent WPF and Windows type of applications?

If I create my own project type (.myproj) that has .xaml and .cs files, what should I fill in this ProjectTypeGuids tags? Should I also need to fill the ProjectType tag?

It would also be better if someone differentiate the ProjectType and ProjectTypeGuids*tags.

What is the significance of ProjectTypeGuids tag in the visual studio project file

Is there a way to add existing Folders to a Visual Studio Project so that I do not have to do this file by file?

**Edit**

To make it clear: I want to add *references* not *copies*.

Visual Studio: Add existing folder(s) to project

How can I delete (and not simply close) a project in PHPStorm?

How to remove a project (from the workspace) in PHPStorm?

We have a solution with around 100+ projects, most of them C#. Naturally, it takes a long time to both open and build, so I am looking for best practices for such beasts. Along the lines of questions I am hoping to get answers to, are:

 - how do you best handle references between projects
    - should &quot;copy local&quot; be on or off?
 - should every project build to its own folder, or should they all build to the same output folder(they are all part of the same application)

 - Are solutions&#39; folders a good way of organizing stuff?

I know that splitting the solution up into multiple smaller solutions is an option, but that comes with its own set of refactoring and building headaches, so perhaps we can save that for a separate thread :-)

Best practices for large solutions in Visual Studio (2008)

I frequently work with multiple instances of Visual Studio, often working on different branches of the same solution.

[Visual C++ 6.0][1] used to display the full path of the current source file in its title bar, but Visual&amp;nbsp;Studio 2005 doesn&#39;t appear to do this. This makes it slightly more awkward than it should be to work out which branch of the solution I&#39;m currently looking at (the quickest way I know of is to hover over a tab so you get the source file&#39;s path as a tooltip).

Is there a way to get the full solution or file path into the title bar, or at least somewhere that&#39;s always visible, so I can quickly tell which branch is loaded into each instance?

  [1]: https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B#Strictly_32-bit_versions




Display solution/file path in the Visual Studio IDE

I have a solution in Visual Studio which contains several projects. I&#39;d like to run a command at the very beginning of every build - no matter which projects are involved and whether or not they are up-to-date.

Essentially I need something similar to a solution-wide pre-build event, but unfortunately VS does not appear to support these. Does anyone know an alternative way of achieving what I need?

Solution-wide pre-build event?

I have multiple projects in a single Visual Studio (2008) solution.  
I just discovered that each of these projects uses a same GUID, so in the solution file it looks like this:

    Project(&quot;{FAE04EC0-F103-D311-BF4B-00C04FCBFE97}&quot;) = &quot;Pro1&quot;, &quot;Pro1\Pro1.csproj&quot;, &quot;{...}&quot;
    Project(&quot;{FAE04EC0-F103-D311-BF4B-00C04FCBFE97}&quot;) = &quot;Pro2&quot;, &quot;Pro2\Pro2.csproj&quot;, &quot;{...}&quot;

Do I have to change these GUIDs so they&#39;re unique and what are they used for?


What are the project GUIDs in a Visual Studio solution file used for?

If I add a new file to a project under TFS source control, it will check out the project file and the corresponding .vspscc file for that project file. 

The project file itself changes (to include the new file), but the .vspscc file doesn&#39;t change at all. Why bother checking it out? Is there a way to disable it from being checked out and if there is, should I?

Why does Visual Studio check out the .vspscc file when I add a file to a project?

Visual Studio 2017 breaks in debug mode and displays the message:

&gt; Your app has entered a break state, but there is no code to show
&gt; because all threads were executing external code (typically system or
&gt; framework code).

The message is in the `Break Mode Window`.

What to do?

Your app has entered a break state, but there is no code to show because all threads were executing external code (typically system or framework code)

I have always used Visual Studios built in GUI support for configuring my projects, often using property sheets so that several projects will use a common set.

One of my main gripes with this is managing multiple projects, configurations and platforms. If you just do everything with the main GUI (right click the project -&gt; properties) it quickly becomes a mess, difficult to maintain and prone to bugs (like failing to correctly define some macro, or using the wrong runtime library, etc). Dealing with the fact that different people put there dependency libraries in different places (eg mine all live in &quot;C:\\Libs\\[C,C++]\\[lib-name]\\&quot;) and then often manage the different versions of those libraries differently as well (release, debug, x86, x64, etc) is also a large problem since it vastly complicates the time to set it up on a new system, and then there is issues with version-control and keeping everyone&#39;s paths separate...

Property sheets make this a bit better, but I cant have one sheet have separate settings for different configurations and platforms (the drop down boxes a greyed out), resulting in me having many sheets which if inherited in the correct order do what I want (&quot;x86&quot;, &quot;x64&quot;, &quot;debug&quot;, &quot;release&quot;, &quot;common&quot;, &quot;directories&quot; (deals with the previously mentioned dependency issue by defining user macros like BoostX86LibDir), etc) and if inherited in the wrong order (eg &quot;common&quot; before &quot;x64&quot; and &quot;debug&quot;) lead to issues like trying to link an incorrect library version, or incorrectly naming the output...

What I want is a way of dealing with all these scattered dependencies and setting up a set of &quot;rules&quot; which are used by all my projects in the solution, like naming an output library as &quot;mylib-[vc90,vc100]-[x86,x64][-d].lib&quot;, without having to do all this for each individual project, configuration and platform combination, and then keep them all correctly in sync.

I am aware of moving to entirely different systems like CMake that create the needed files, however this then complicates things elsewhere by making it so even simple tasks like adding a new file to the project then requires additional changes elsewhere, which is not something I am entirely happy with either, unless there is some with VS2010 integration which can keep track of these sorts of changes.

Using Visual Studio project properties effectively for multiple projects and configurations

I&#39;m using Eclipse. Say I have a project &#39;ProjectA&#39; in the eclipseworkspace (in a folder ProjectA). I want to copy the project but with a new name (ProjectB) and have all the references in the new project adjusted. I can&#39;t find much help for what I thought would be a vary basic operation. I want to try out variations on the original design/code and creating a copy seemed the obvious way to go about it.

Any suggestions please.

Android - copy existing project with a new name in Eclipse

I opened my vs2010 solution with vs2012 but it didn&#39;t make any conversion as from 2008 to 2010 was happening. So my solution still remains the same as 10 label on it. when I make a new solution of course it has 11 label on it. I haven&#39;t got any problem running like that but I am curious. Is there any difference? if yes, how to convert into vs2012 solution? 



Visual Studio 2012 doesn&#39;t convert vs2010 solution?

__Direct Question:__ If I have two files with the same name (but in different directories), it appears that only Visual Studio 2005 can handle this transparently??  VS 2008 &amp; 2010 require a bunch of tweaking?  Aside from my naming convention, am I doing something wrong?

__Background:__

I&#39;m developing C++ statistical libraries...  I have two folders:

    / Univariate
    
    Normal.cpp
    Normal.h
    Beta.cpp
    Beta.h
    Adaptive.cpp
    Adaptive.h
    
    / Multivariate
    
    Normal.cpp
    Normal.h
    Beta.cpp
    Beta.h
    Adaptive.cpp
    Adaptive.h

I need to support cross compilation -- I&#39;m using g++/make to compile these same files into a library in Linux.  They work just fine.

I had been using Visual Studio 2005 without issue, but I need to upgrade to Visual Studio 2008 or 2010 (currently drooling over nVidia&#39;s nsight tool).  However, I&#39;m having trouble if I add files to a project with the same name (even if they&#39;re in a different directory).  I&#39;m willing to change my naming convention, but I&#39;m curious if others have encountered this problem and have found any __well__ documented solutions??

I&#39;m further boggled by the fact that if I upgrade from 2005 projects to 2010 projects, it appears that VS 2010 __is__ able to correctly handle two source files with the same name in different directories; however, if I remove one of the duplicate files and then add it back to the project I am greeted by the following warning:

Distributions\Release\Adaptive.obj : warning LNK4042: object specified more than once; extras ignored

Now I have the intermediate directory specified as $(ProjectName)\$(Configuration) -- I need to have my object files in a different location from my source tree.  So I can see why it&#39;s copying the object files on top of each other, but when the projects are converted from 2005 to 2008 or 2010, a bunch of conditional compiles are added:

    &lt;ObjectFileName Condition=&quot;&#39;$(Configuration)|$(Platform)&#39;==&#39;Release|x64&#39;&quot;&gt;$(IntDir)%(Filename)1.obj&lt;/ObjectFileName&gt;
    &lt;XMLDocumentationFileName Condition=&quot;&#39;$(Configuration)|$(Platform)&#39;==&#39;Release|x64&#39;&quot;&gt;$(IntDir)%(Filename)1.xdc&lt;/XMLDocumentationFileName&gt;

These are accessible from the Source file Properties page in C/C++ -&gt; Output Files -&gt; &quot;Object File Name&quot; &amp; &quot;XML Documentation File Name&quot;.  But if I simply add the file directly (or remove and re-add them), VS doesn&#39;t complain until I try to compile, but also never adds the conditional directives -- So in order for things to work correctly, I have to add the conditional directives myself for every single configuration.  Am I making a mistake / poor assumption or have I uncovered a valid bug in VS 2008 / 2010?


Visual Studio 2010 &amp; 2008 can&#39;t handle source files with identical names in different folders?

I have error from visual studio 2010:

&gt; Error	1	The item &quot;CrossDomainService.svc.cs&quot; was specified more than once in the &quot;Sources&quot; parameter.  Duplicate items are not supported by the &quot;Sources&quot; parameter.	WcfServiceDomain

and from msbuild 

&gt;   C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets(160,9)
: error MSB3105: The item &quot;CrossDomainService.svc.cs&quot; was specified more than o
nce in the &quot;Sources&quot; parameter.  Duplicate items are not supported by the &quot;Sources&quot; parameter. [C:\inetpub\Wwwroot\axaptaWcfConnection\WcfServiceDomain\WcfSer
viceDomain.csproj]


My file is csproj:


        &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;Project ToolsVersion=&quot;4.0&quot; xmlns=&quot;http://schemas.microsoft.com/developer/msbuild/2003&quot;&gt;
      &lt;Import Project=&quot;$(MSBuildToolsPath)\Microsoft.CSharp.targets&quot; /&gt;
      &lt;PropertyGroup&gt;
        &lt;Configuration Condition=&quot; &#39;$(Configuration)&#39; == &#39;&#39; &quot;&gt;Debug&lt;/Configuration&gt;
        &lt;Platform Condition=&quot; &#39;$(Platform)&#39; == &#39;&#39; &quot;&gt;AnyCPU&lt;/Platform&gt;
        &lt;ProductVersion&gt;
        &lt;/ProductVersion&gt;
        &lt;SchemaVersion&gt;2.0&lt;/SchemaVersion&gt;
        &lt;ProjectGuid&gt;{8D40933A-E036-4CD0-9003-314A692724D5}&lt;/ProjectGuid&gt;
        &lt;ProjectTypeGuids&gt;{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}&lt;/ProjectTypeGuids&gt;
        &lt;OutputType&gt;Library&lt;/OutputType&gt;
        &lt;AppDesignerFolder&gt;Properties&lt;/AppDesignerFolder&gt;
        &lt;RootNamespace&gt;WcfServiceDomain&lt;/RootNamespace&gt;
        &lt;AssemblyName&gt;WcfServiceDomain&lt;/AssemblyName&gt;
        &lt;TargetFrameworkVersion&gt;v4.0&lt;/TargetFrameworkVersion&gt;
        &lt;TargetFrameworkProfile /&gt;
        &lt;FileUpgradeFlags&gt;
        &lt;/FileUpgradeFlags&gt;
        &lt;UpgradeBackupLocation&gt;
        &lt;/UpgradeBackupLocation&gt;
        &lt;OldToolsVersion&gt;4.0&lt;/OldToolsVersion&gt;
      &lt;/PropertyGroup&gt;
      &lt;PropertyGroup Condition=&quot; &#39;$(Configuration)|$(Platform)&#39; == &#39;Debug|AnyCPU&#39; &quot;&gt;
        &lt;DebugSymbols&gt;true&lt;/DebugSymbols&gt;
        &lt;DebugType&gt;full&lt;/DebugType&gt;
        &lt;Optimize&gt;false&lt;/Optimize&gt;
        &lt;OutputPath&gt;bin\&lt;/OutputPath&gt;
        &lt;DefineConstants&gt;DEBUG;TRACE&lt;/DefineConstants&gt;
        &lt;ErrorReport&gt;prompt&lt;/ErrorReport&gt;
        &lt;WarningLevel&gt;4&lt;/WarningLevel&gt;
        &lt;PlatformTarget&gt;x86&lt;/PlatformTarget&gt;
      &lt;/PropertyGroup&gt;
      &lt;PropertyGroup Condition=&quot; &#39;$(Configuration)|$(Platform)&#39; == &#39;Release|AnyCPU&#39; &quot;&gt;
        &lt;DebugType&gt;pdbonly&lt;/DebugType&gt;
        &lt;Optimize&gt;true&lt;/Optimize&gt;
        &lt;OutputPath&gt;bin\&lt;/OutputPath&gt;
        &lt;DefineConstants&gt;TRACE&lt;/DefineConstants&gt;
        &lt;ErrorReport&gt;prompt&lt;/ErrorReport&gt;
        &lt;WarningLevel&gt;4&lt;/WarningLevel&gt;
      &lt;/PropertyGroup&gt;
      &lt;ItemGroup&gt;
        &lt;Reference Include=&quot;System.Web.ApplicationServices&quot; /&gt;
        &lt;Reference Include=&quot;System.Web.DynamicData&quot; /&gt;
        &lt;Reference Include=&quot;System.Web.Entity&quot; /&gt;
        &lt;Reference Include=&quot;System.Configuration&quot; /&gt;
        &lt;Reference Include=&quot;System.Drawing&quot; /&gt;
        &lt;Reference Include=&quot;System.EnterpriseServices&quot; /&gt;
        &lt;Reference Include=&quot;System.Runtime.Serialization&quot; /&gt;
        &lt;Reference Include=&quot;System.ServiceModel&quot; /&gt;
        &lt;Reference Include=&quot;System.ServiceModel.Web&quot; /&gt;
        &lt;Reference Include=&quot;System.Web.Services&quot; /&gt;
      &lt;/ItemGroup&gt;
      &lt;ItemGroup&gt;
        &lt;Content Include=&quot;ClientAccessPolicy.xml&quot; /&gt;
        &lt;Content Include=&quot;CrossDomainService.svc&quot; /&gt;
        &lt;Content Include=&quot;Service1.svc&quot; /&gt;
        &lt;Content Include=&quot;Web.config&quot;&gt;
          &lt;SubType&gt;Designer&lt;/SubType&gt;
        &lt;/Content&gt;
        &lt;Content Include=&quot;Web.Debug.config&quot;&gt;
          &lt;DependentUpon&gt;Web.config&lt;/DependentUpon&gt;
        &lt;/Content&gt;
        &lt;Content Include=&quot;Web.Release.config&quot;&gt;
          &lt;DependentUpon&gt;Web.config&lt;/DependentUpon&gt;
        &lt;/Content&gt;
      &lt;/ItemGroup&gt;
      &lt;ItemGroup&gt;
        &lt;Compile Include=&quot;CrossDomainService.svc.cs&quot;&gt;
          &lt;DependentUpon&gt;CrossDomainService.svc&lt;/DependentUpon&gt;
        &lt;/Compile&gt;
        &lt;Compile Include=&quot;ICrossDomainService.cs&quot; /&gt;
        &lt;Compile Include=&quot;Service1.svc.cs&quot;&gt;
          &lt;DependentUpon&gt;Service1.svc&lt;/DependentUpon&gt;
        &lt;/Compile&gt;
        &lt;Compile Include=&quot;IService1.cs&quot; /&gt;
        &lt;Compile Include=&quot;Properties\AssemblyInfo.cs&quot; /&gt;
      &lt;/ItemGroup&gt;
      &lt;ProjectExtensions&gt;
        &lt;VisualStudio&gt;
          &lt;FlavorProperties GUID=&quot;{349c5851-65df-11da-9384-00065b846f21}&quot;&gt;
            &lt;WebProjectProperties&gt;
              &lt;UseIIS&gt;False&lt;/UseIIS&gt;
              &lt;AutoAssignPort&gt;True&lt;/AutoAssignPort&gt;
              &lt;DevelopmentServerPort&gt;51421&lt;/DevelopmentServerPort&gt;
              &lt;DevelopmentServerVPath&gt;/&lt;/DevelopmentServerVPath&gt;
              &lt;IISUrl&gt;
              &lt;/IISUrl&gt;
              &lt;NTLMAuthentication&gt;False&lt;/NTLMAuthentication&gt;
              &lt;UseCustomServer&gt;False&lt;/UseCustomServer&gt;
              &lt;CustomServerUrl&gt;
              &lt;/CustomServerUrl&gt;
              &lt;SaveServerSettingsInUserFile&gt;False&lt;/SaveServerSettingsInUserFile&gt;
            &lt;/WebProjectProperties&gt;
          &lt;/FlavorProperties&gt;
        &lt;/VisualStudio&gt;
      &lt;/ProjectExtensions&gt;
      &lt;Import Project=&quot;$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets&quot; /&gt;
    &lt;/Project&gt;


I not see any duplicate :/ Any idea from this error ?? 

error in csproj - duplicate item

Up to VS2008, you set your **native C++** project dependencies up in the solution file (`Project Dependencies ...`) and if (by default) the Linker Option

    Properties -&gt; Linker -&gt; General : Link Library Dependencies = Yes

is set, the Visual Studio Build will automatically link in the `.lib` files of all projects (DLLs, LIBs) that this project is dependent on will be &quot;statically&quot; linked in.

-----

***Side** Note*: Microsoft changed how the dependencies worked in **VS2010** and you are now supposed to add the dependency directly to the project

    Common Properties -&gt; Framework and References : (List of depenencies) 

        (each lib/dll has a separate option: 
         Project Reference Properties -&gt; Link Library Dependencies : True|False

I&#39;m fine with that. *This is **not** what this question is about.*

(One explanation here: [Flexible Project-to-Project References][1].)

-----

It is *still* possible however to define project dependencies on the Solution level and the `General` Linker option is also *still* there. However it doesn&#39;t work. See:

* [Link Library Dependencies not working?][2]
* https://stackoverflow.com/questions/2704576/did-visual-studio-2010-break-project-dependencies-between-c-projects
* https://stackoverflow.com/questions/3795567/visual-studio-2010-not-autolinking-static-libraries-from-projects-that-are-depend
    * [&quot;but oddly enough, without removing the old UI, or in any way indicating that it no longer works&quot;][3]

and especially see here (acutal *question* follows)
-----------------------

* [MS Connect Bug 586113: &quot;Link Library Dependencies&quot; does not work][4]

Where Microsoft confirms that the Linker Option doesn&#39;t do what the rest of the world&#39;s population expects it to do, and adds the following explanation:

&gt; Thanks for reporting this feedback. The issue you are experiencing is
&gt; by design. &quot;Link Library Dependency&quot; is a flag that only dictates
&gt; whether or not to pass the library as an input to the linker. It does
&gt; not find the dependency automatically. As a customer you will have to
&gt; define the depedency manually as you suggest.

Can **anyone explain what that means**, or more to the point: *What does the &quot;Link Library Dependency&quot; linker option actually do in Visual Studio 2010?*

What is an &quot;input to the linker&quot; that isn&#39;t actually linked supposed to be?

  [1]: http://blogs.msdn.com/b/vcblog/archive/2010/05/03/flexible-project-to-project-references.aspx
  [2]: http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/163a3b2d-c747-4436-8e5b-2e52b45af1a2/
  [3]: https://stackoverflow.com/questions/3795567/visual-studio-2010-not-autolinking-static-libraries-from-projects-that-are-depend/3796378#3796378
  [4]: http://connect.microsoft.com/VisualStudio/feedback/details/586113/link-library-dependencies-does-not-work#details

What does the &quot;Link Library Dependency&quot; linker option actually do in Visual Studio 2010 - 2015 and upwards?

Due to issues with merging etc, we have lots of project files that don’t contain all source code files that are within their folders.

Before I write a little tool, that checks that every `*.cs` file is included in a project file, I wish to make sure that no-body else has already done that before.

(We have close to 100 project files, and 1000s of C# files)

-------------------
-------------------

Clearly the support that visual studio now has for using wildcards to include all “*.cs” files from a given directory in the project is the best solution to this problem.      In that there is then no need to update project files when “.cs” files are added, renamed ete.     However it is only in VS2017 that this become usable from the UI. 



How do I find files that are missing from visual studio projects?

In Visual Studio 2008, what determines the order in which projects appear within a solution folder? It&#39;s not alphabetical order, nor is it build order.

I cannot find any way of altering the order in which projects are being listed. I&#39;ve tried removing my *.suo* file, as well as moving things about in the *.sln* file. Neither had any effect.

**How can I change the order in which my projects are being displayed?**

Project Order in Visual Studio Solution

I recently installed the Visual Studio 11 Developer Preview to try it out, and now my VS 2010 projects won&#39;t open. Instead, I get the following error message:

&gt; MSBuild does not contain a value for the &quot;VCTargetsPath&quot; property

I found someone that had reported the issue [here on Connect](http://connect.microsoft.com/VisualStudio/feedback/details/710360/visual-studio-net-2010-could-not-open-vc-projects-after-installing-visual-studio-net-2011-developer-preview-edition), and the response from Microsoft was:

&gt; Posted by Microsoft on 12/2/2011 at 5:25 PM  
&gt; Hi Afshin,
    
&gt; Thanks for the feedback. The issue you ran into is fixed for the next public release Visual Studio.
    
&gt; Jim Griesmer  
Visual C++ Team

Fantastic. So how do I restore VCTargetsPath so my projects will work again?

&gt; &quot;VCTargetsPath is a toolset property that is defined in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0. &quot;

I browsed to the VCTargetPath value in the registry and it has the value: 

    $(MSBuildExtensionsPath32)\Microsoft.Cpp\v4.0\

Not sure where to go from here. Any suggestions?

All Projects and-Solutions Solutions on Gang of Coders

Total of 31 Projects and-Solutions Solutions