...And yes, this one I am afraid doing myself. And not just me. Better get stuck with 2012 and support it or ask Ogre's Gurus to support 2013 / Windows 7.
Yes, it's terrible that I have to explicitly state this, but the industry and software maintenance are somehow dictating what users do. Just switching to 2013 will force so much users get pissed off because compiling libraries like Ogre and Qt is terribly difficult. (Well. these Linux guys are definitely smarter by us, Windows guys).
In the ideal world, everything will be standardized in a way that everybody just downloads it, unpacks it, compiles it with just a command and is happy.
In the REAL world, there is a thing called CMake (and another one called Visual Studio).
They both makes the pain to compile libraries and projects a little bit not-so-painful.
Still, Visual Studio is somehow forced "standard" here on Windows. You either use precompiled libraries and drop them right into your project, or you feel the pain to compile them with some unknown version of GCC / CLANG. And when Visual Studio versions come into play, you still encounter this issue.
You can spend up entire days in order to get a library just compile for a version of a compiler that this version was untested from, instead of concentrating your efforts to work on your artistic innovative Veoxel-based piece of code