![]() We'll start by creating 2 different solutions, each one containing a console application, referencing a class library: If the same project is included in multiple solutions, Visual Studio might start to misbehave. In simple scenarios this is enough to ensure consistency. When you add an existing project to the solution file, it verifies its project GUID and modifies it, if there is already a project with the same GUID in the solution. For this to work, it needs all project GUIDs to be unique inside a solution file. Visual Studio uses project GUIDs to identify different project files and their dependencies in a solution file, as well as for references between projects inside a single solution file. The troubles begin, when you create a copy of a project by copying its folder and renaming the files. Each one of them contains a GUID value which should by definition be unique in normal circumstances. You might not be aware of it, but Visual Studio projects have additional identity beyond their project file name and path. NET Framework Project GUIDs Uniquely Identify Projects
0 Comments
Leave a Reply. |