<rant>MS is trying to kill me. What happened to a two year release cycle? What is wrong with releasing new or updated packages for the previous platform (VS2012) so that everyone other vendor's tools still install and register the same way? They used to call a few new features a service pack, not a new product. I just got an official VS2012 installed at the beginning of the summer so I could both build and run NORMA on VS2012 (instead of just building it, the license is only checked when you open the IDE, which isn't needed for build). Upgrade licenses don't cut it for me because I have to be able to build and run the previous platform as well, not transfer the license to another product.</rant>
I've been gone most of the summer, so I guess I missed the release. It's mighty unsporting of Microsoft to burden my poor build machine with a new (fifth) version of Visual Studio less than a year after I got the last one running. It will be at least a couple of weeks before I can look at this. After download and install, it takes around a day to investigate the new system and get it to build--assuming there are no interface or libary changes, and there are always some surprises. If the DSL templates have changed sufficiently that the new libraries no longer work with the older generated bits, then add at least one more day of work to integrate a third set of generated files.
That's just the predictable busy work. Then come the surprises.
The last go round deprecated all of the build and project system classes (full rewrite of the custom tool code generator), broke coloring in the fact editor (and hid the settings to fix it in a completely undocumented registry key just to make it fun), mangled the extension installation system badly enough that I could no longer use it reliably, changed the toolbox item registration system, added some new diagram events that crashed at odd times if you didn't handle or block them (which, of course, the existing code didn't), and required new WiX (installer) versions that didn't like the old setup files. They haven't had as long to stir the pot this time, so hopefully it will be a smoother transition.
I guess the rant continued past the end tag, sorry.
Seriously, though, I'll see what I can do to at least get this out in 2013. Until I burn a couple of days to get the build working and the packages running in a new VS version I have no way of providing any estimate as to the total time. It's a total crapshoot.