Only the project files determine their build outputs - solutions only link projects together into a logical entity, so that they can be loaded at the same time in a Visual Studio instance. If the projects are still the same, nothing's broken.
You can open your . Sln file with whatever editor you'd like, even notepad, and see that it contains only references to your project files in it, you can modify it so that the relative paths to your project files in it match your layout. VS wouldn't have anything against it.
All build settings are stored in project files, so you don't loose any configuration changes you've done in your projects.
...but use source control/make a backup first! :) – TrueWill Aug 30 '09 at 16:42 that's very true, and as a side note, . Suo can be safely deleted and added to your VCS ignore list.
– Dmitry Aug 30 '09 at 18:14.
And the . Suo file can be safely deleted. It's a user-specific file that simply retains a particular user's options for a solution.It contains nothing that's important to projects, build settings etc.
Sln file with whatever editor you'd like, even notepad, and see that it contains only references to your project files in it, you can modify it so that the relative paths to your project files in it match your layout. VS wouldn't have anything against it. All build settings are stored in project files, so you don't loose any configuration changes you've done in your projects.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.