I have not tested VS 2013 Preview yet, but since the macros IDE was
not updated in VS 2010 and was completely removed in VS 2012, I wouldn’t
expect it to be back in VS 2013 (after all, colors are not getting back either). So, for those many users aggraviated by the macros removal I have written a small article that shows how to convert macros to an add-in with minimal effort:
HOWTO: Migrate macro methods to a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013016.aspx
And the final chapter of this series about to create solution configurations, project configurations and project platforms, and the lack of support to create new solution platforms, and how to change project configuration, is about changing the project platform for a given solution platform, something that had to wait 3 versions of Visual Studio (2005, 2008, 2010) until support was added in VS 2012:
HOWTO: Change the build platform of a project from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013014.aspx
PRB: Cannot change the build platform of a project from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013015.aspx
Once we learned how to create solution configurations, project configurations and project platforms, and the lack of support to create new solution platforms, the next thing is to be able to change the project configuration for a given solution configuration. Alas, this is possible in VS 2005 and 2012 but VS 2008 and 2010 have a bug that ruins the attempt:
HOWTO: Change the build configuration of a project from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013012.aspx
BUG: Build configuration of a project cannot be changed from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013013.aspx
After learning how to add / delete build project configurations from a Visual Studio add-in, the counterpart to do the same with project platforms:
HOWTO: Add / delete build project platforms from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013011.aspx
This article completes the creation / deletion of solution configurations, solution platforms, project configurations and project platforms. In the next articles I will show how to change programmatically the project configuration/platform for a given solution configuration/platform, along with some issues doing it.
The next article of the convoluted build configuration automation model (EnvDTE/EnvDTE80) and its diagram is about adding or deleting project configurations programmatically:
HOWTO: Add / delete build project configurations from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013010.aspx
The convoluted build configuration automation model (EnvDTE/EnvDTE80) and its diagram was already so tricky to add / delete solution configurations that it has to explode from some angle: the lack of direct (*) support to add / delete solution platforms:
PRB: Build solution platforms cannot be added / deleted from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013009.aspx
(*) There is a kind of workaround creating project platforms propagated as new solution platforms (via EnvDTE.ConfigurationManager.AddPlatform(newName, existingName, true) that I will explore in a new post / article.
The next article about the convoluted build configuration automation model (EnvDTE/EnvDTE80) and its diagram series of articles that I have started shows the code to add or delete solution configurations from a Visual Studio add-in. The deletion approach of the automation model has a hidden trap explained in the article and code:
HOWTO: Add / delete build solution configurations from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013008.aspx
After explaining how to get information about the solution and project configurations/platforms, it’s time now to know how to modify them. The most common question about this is how to change the active solution configuration / platform:
HOWTO: Get or set the active solution configuration/platform from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013007.aspx
Continuing with the convoluted build configuration automation model (EnvDTE/EnvDTE80) and its diagram series of articles that I started yesterday, today a new installment about how to get the information about the build configuration / platforms for a given EnvDTE.Project from a Visual Studio add-in:
HOWTO: Get the project configurations / platforms from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013006.aspx
Long time ago I wrote about the convoluted build configuration automation model (EnvDTE/EnvDTE80) and its diagram. Since questions about this keep appearing in the MSDN VSX Forum, I am going to write some articles about how to get/modify/add solution/project configurations/platforms.
The first one is about how to get the information of the Configuration Manager from a Visual Studio add-in:
HOWTO: Get the solution configurations / platforms from a Visual Studio add-in
http://www.mztools.com/articles/2013/MZ2013005.aspx