Project persistence block in a solution file has the following format: Project(“{project type GUID}”) = “<Project name>”, “<project file location>”, “{<Unique project GUID>}” EndProject So it’s expected that first GUID is non-unique, it uniquely identifies Visual Studio package that handles this type of projects. The GUID you posted is interesting – it looks like mangled … Read more
This is a extension available in the online gallery specifically tailored for this job. Checkout Labs > Visual Studio Extension: Customize Visual Studio Window Title.
You might be interested in these two MSBuild articles that I have written. MSBuild: Best Practices For Creating Reliable Builds, Part 1 MSBuild: Best Practices For Creating Reliable Builds, Part 2 Specificially in Part 2 there is a section Building large source trees that you might want to take a look at. To briefly answer … Read more
**Two Approaches for PHPSTORM 2018.3 Version ** A. Eternal Removal or Deletion from Hardware and Phpstorm IDE Please visit the folder ‘PhpstormProjects’ and delete the project file manually. If you do so, you will see the folder disappear from Phpstorm explore window. This might be weird, but true. B. Remove from the recent project panel … Read more
If you follow my recommendations below (I have for years), you will be able to: — put each project anywhere in source control, as long as you preserve the structure from the project root directory on down — build each project anywhere on any machine, with minimum risk and minimum preparation — build each project … Read more
{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} is the GUID for C# project {60dc8134-eba5-43b8-bcc9-bb4bc16c2548} is for project in WPF flavor package So your ProjectTypeGuids is for a WPF C# project. You could see the meaning of the different GUID in the register : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\Projects for ProjectTypeGuids HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\Packages for packages reference by some project Some ProjectTypeGuids Windows (C#) {FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} Windows (VB.NET) {F184B08F-C81C-45F6-A57F-5ABD9991F28F} … Read more
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 … Read more
Settings for compiler In the project where you want to #include the header file from another project, you will need to add the path of the header file into the Additional Include Directories section in the project configuration. To access the project configuration: Right-click on the project, and select Properties. Select Configuration Properties->C/C++->General. Set the … Read more
Ugh, this is an old problem, something that still pops up in Visual Studio once in a while. It’s bitten me a couple of times and I’ve lost hours restarting and fighting with VS. I’m sure it’s been discussed here on SO more than once. It’s also been talked about on the MSDN forums. There … Read more
I find some missing information in the other answers (at least for people who come from other IDEs like, say, Eclipse) . To say that a solution is a container for projects is only part of the thing. The conceptual feature of a VS project (what determines its ‘granularity’) is that one project produces one … Read more