projects-and-solutions

I'm working on a middle-sized project that contains several class libraries, database model and an ASP .NET MVC website project. However, even though there are less than 15 projects in the solution, I often find myself collapsing and expanding endless folders to find a certain class or view . While looking for class is mostly solved by Resharper type navigation feature , I often want to switch to a certain view in MVC project. I don't remember the file name and it wouldn't solve the problem either because there are many views with same file name (e.g. Message\ViewSingle.cshtml , Product

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("{FAE04EC0-F103-D311-BF4B-00C04FCBFE97}") = "Pro1", "Pro1\Pro1.csproj", "{...}" Project("{FAE04EC0-F103-D311-BF4B-00C04FCBFE97}") = "Pro2", "Pro2\Pro2.csproj", "{...}" Do I have to change these GUIDs so they're unique and what are they used for? Project persistence block in a solution file has the following format: Project("{project type GUID}") = "<Project name>", "<project file location>", "{<Unique project

How can I convert existing vcproj files to project files that the QT add-in to Visual Studio recognizes and treats as valid Qt projects? Should I just bite the bullet and create new projects to replace the old ones, and then add existing code? I am using QT 4.6 and VS 2008 with Qt Add-in 1.1.2. Original vcproj files have NOT been generated with QMake. Benjamin Using Visual Studio 2010+ it is now possible to convert a project to a Qt Addin project, using the "Convert project to Qt Add-in project" feature of the Qt Addin. The following steps are from the work around in bug QTVSADDINBUG-27. This

When/where do you decide to split a large Visual Studio project into smaller multiple projects? If it can be reusable? when project is too big? (but how big is too big?) and When you do split the project, do you, group by database tables group by similar functionality other.. Pros of many projects: Easier to isolate code for unit testing. I like to isolate code that has a dependency on a big external server thing, for example code that talks to the SMTP server gets its own assembly, code that talks to the database gets it's own assembly, code that talks to the webserver, code that is pure

I frequently work with multiple instances of Visual Studio, often working on different branches of the same solution. VC6 used to display the full path of the current source file in its title bar, but Visual Studio 2005 doesn't appear to do this. This makes it slightly more awkward than it should be to work out which branch of the solution I'm currently looking at (the quickest way I know of is to hover over a tab so you get the source file's path as a tooltip). Is there any way to get the full solution or file path into the title bar, or at least somewhere that's always visible so I can

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! I think it's clear from the other answers that solution files are useful and should be committed, even if they're not used for official builds. They're handy to have for anyone using Visual Studio features like Go To Definition/Declaration. By default, they don't contain absolute paths or any other machine-specific artifacts. (Unfortunately, some add-in tools don't properly maintain this property,