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.