Thanks for the info. It looks to me this may be still related with VS2012. I logged this issue. The suggestion I can think of now is to work on a machine with VS2010 only. Sorry.
We finally addressed this issue. Please refer to the blog:
Sorry for the inconvenience caused.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!