title: What determines if Visual Studio 2012 needs to "migrate" a Visual Studio 2010 projecT?
body: <p>I have an open source project that is primarily developed using MonoDevelop. I went to test it in Visual Studio 2010 and everything worked fine there. Then, I went to test it in Visual Studio 2012 and it did a "silent" migration of my project and solution. </p>
  
  <p>Unlike Visual Studio 2010, it didn't display any warnings about a migration being needed. Instead, it just did the migration and spew out a migration report. It also reset my project to using .Net 2.0, where before it was set to use 4.0.. (easy to change, but still). After this migration, it works in Visual Studio 2010 fine and doesn't attempt a migration. </p>
  
  <p>However, my question is what determines that it even needs to do a migration? At my work we have a Visual Studio 2010 project that works flawlessly in Visual Studio 2012 without any migration(the project file isn't even marked as modified afterwards) though. What's the difference here? </p>