http://blogs.msdn.com/vcblog/archive/2009/06/10/vs-project-team-blog-is-up.aspxThe VS Project team, part of Platform team, own the C# and VB project systems brought their expertise to the table along with the VC++ team to give you an extensible and much more powerful project system. The team maintains a blog at http://blogs.msdn.com/vsproject/enCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/vcblog/archive/2009/06/10/vs-project-team-blog-is-up.aspx#9724553Wed, 10 Jun 2009 19:32:50 GMT91d46819-8472-40ad-a661-2c78acb4018c:9724553infoblog &raquo; VS Project Team Blog Is Up!<p>PingBack from <a rel="nofollow" target="_new" href="http://blog.a-foton.ru/index.php/2009/06/10/vs-project-team-blog-is-up/">http://blog.a-foton.ru/index.php/2009/06/10/vs-project-team-blog-is-up/</a></p> http://blogs.msdn.com/vcblog/archive/2009/06/10/vs-project-team-blog-is-up.aspx#9724749Wed, 10 Jun 2009 21:14:10 GMT91d46819-8472-40ad-a661-2c78acb4018c:9724749jalf<p>Would these be the chaps you had to pester if you wanted those horrendous old JS-based C++ project wizards replaced by something nice and sane like the other languages have? Or is that still the VC++ team's responsibility?</p> <p>Whoever &quot;owns&quot; these, I think an upgrade is long overdue. Trying to define a new VC++ project type is just a scary process. Messing around with scarcely-documented JavaScript API's should not be necessary if I just want to define a new type of C++ projects substituting the default configuration for my own.</p>