Without source control: If one solution (MVC4 Cool Towel SPA) in VS is in debug mode and you open also another solution, in another simultaneous VS instance, of a former version with the same solution name, for some copy and paste work, and if Entity Framework (EF) has changed between the two versions. Then stop debug, restart debug, newest version is all of the sudden out of sync with EF, maybe the corruption happens here, moreover closing the former version VS, does not fix the problem, you must reboot the computer, and then you discover that your newest version solution SPA has all kinds of weird errors typical for corruption.
Could you please fix this? Its a consequence of the fact that Microsoft does not want the VS GUI be cluttered with a "Save solution (with all files) as ..." menu option. I ask you to pass this bill of solution corruption prevention, not for me, but for all people, that do not have source control!
PS: I used to (before I had source control) copy / paste the solution directory and rename it to ... version X.X, of course the solution inside keeps its name, actually its a hell of a job to rename a solution file (*.sln) itself and keep it VS functional, when I recall correctly that name is also in ~5 config files, moreover also the physical directory path is in several of those files!