projects-and-solutions

Is it possible to open a project in Visual Studio 2008 without opening all the files that were previously opened last time I had the project open. I have a habit of keeping many files open as I am working on them, so next time I open the project, it (very slowly) loads up a bunch of files into the editor that I may not even need open. I have searched through the settings and cannot find anything to stop this behavior. Simply delete the .suo file. It contains the list of open files. A bit of research turns up the fact that you can do it with a macro: Create a new macro (or use an existing one).

I've checked out a branch of C# code from source control. It contains maybe 50 projects in various folders. There's no existing .sln file to be found. I intended to create a blank solution to add existing solutions. The UI only lets me do this one project at a time. Is there something I'm missing? I'd like to specify a list of *.csproj files and somehow come up with a .sln file that contains all the projects. Here is a PowerShell version of Bertrand's script which assumes a Src and Test directory next to the solution file. function GetGuidFromProject([string]$fileName) { $content = Get-Content

I recently installed the Visual Studio 11 Developer Preview to try it out, and now my VS 2010 projects won't open. Instead, I get the following error message: MSBuild does not contain a value for the "VCTargetsPath" property I found someone that had reported the issue here on Connect , and the response from Microsoft was: Posted by Microsoft on 12/2/2011 at 5:25 PM Hi Afshin, Thanks for the feedback. The issue you ran into is fixed for the next public release Visual Studio. Jim Griesmer Visual C++ Team Fantastic. So how do I restore VCTargetsPath so my projects will work again? "VCTargetsPath

I am working with a Visual Studio 2005 C++ solution that includes multiple projects (about 30). Based upon my experience, it often becomes annoying to maintain all the properties of the projects (i.e include path, lib path, linked libs, code generation options, ...), as you often have to click each and every project in order to modify them. The situation becomes even worse when you have multiple configurations (Debug, Release, Release 64 bits, ...). Real life examples: Assume you want to use a new library, and you need to add the include path to this library to all projects. How will you avoid

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 "copy local" 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' folders a good way of organizing stuff? I know that splitting the solution up into multiple smaller solutions is an option,

I opened my vs2010 solution with vs2012 but it didn'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't got any problem running like that but I am curious. Is there any difference? if yes, how to convert into vs2012 solution? There are some exceptions , but mostly you'll be able to open the same project and solution files files in both VS2012 and VS2010 SP1. VS2012 may convert projects when you first open them, but the changes are (except noted in the document