{"id":2043,"date":"2010-05-25T16:52:00","date_gmt":"2010-05-25T16:52:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudio\/2010\/05\/25\/programmatically-addingremovingquerying-vc-build-customizations\/"},"modified":"2022-10-13T14:30:06","modified_gmt":"2022-10-13T21:30:06","slug":"programmatically-addingremovingquerying-vc-build-customizations","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/programmatically-addingremovingquerying-vc-build-customizations\/","title":{"rendered":"Programmatically adding\/removing\/querying VC++ Build Customizations"},"content":{"rendered":"
\n

Build Customizations (Custom Build Rules in earlier editions) are commonly used for invoking external tools that translate files from one format to the other, often resulting in C++ sources that can be compiled at the C++ compilation step. In this post, I will explain how to programmatically add, remove,\u00a0 and query for Build Customizations in a VC++ project. I will use the API exposed by the Microsoft.VisualStudio.VCProjectEngine<\/a> namespace to achieve this goal. If you are creating wizards or project templates that introduce new file types which require custom processing during build, then you will find the contents of this post useful.<\/p>\n

In VS2010, Build Customizations (BCs) are represented by 3 files \u2013 (1) an .xml file representing the schema information of the Rule and its properties, (2) a .props file contains default values of some\/all of these properties and (3) a .targets file that contains build logic and in addition, includes the .xml file. The .targets file is mandatory while the other two files are optional. VS2010 requires that all these three files have the same name and be present in the same location. See Li\u2019s blog post<\/a> for more details on BCs and their file format in VS2010.<\/p>\n

For the purpose of this post, I will assume that you have a BC called MyBC which is represented by the three files MyBC.xml, MyBC.props and MyBC.targets in the \u201cC: BuildCustomizations\u201d directory as shown in the snapshot below.<\/p>\n

<\/p>\n

Adding a BC to a VCProject<\/span> is a two-step process:<\/p>\n

1.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>First you need to get a VCToolFile<\/span> object for the BC by requesting the VCProjectEngine<\/span> (you can use the GetBuildCustomizationRepresentation()<\/span> method listed below for this purpose). A VCToolFile<\/span> object simply stores the BC name and location internally.<\/p>\n

2.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span>Add a BC represented by a VCToolFile<\/span> object to the VCProject<\/span> (you can use the AddBuildCustomization()<\/span> method listed below for this purpose).<\/p>\n

Below, I list the C# code for performing 4 operations \u2013 get representation for a BC from the VCProjectEngine<\/span> and add\/remove\/query(two varieties) a BC from a VC++ project. Personally, I prefer testing code involving VC++ API by first creating a dummy Visual Studio Package (you need to install the VS2010 SDK<\/a> to get the project template for this project type) and calling my test methods in the Initialize()<\/span> method. That is what I<\/i> do, you should use whatever method you are most comfortable with.<\/p>\n

To use the code below, you need to add reference to Microsoft.VisualStudio.VCProjectEngine.dll (Version 10) <\/span>and \u00a0add a using<\/span>\u00a0Microsoft.VisualStudio.VCProjectEngine; <\/span>statement in your code file. In the code, input parameter checking is not shown for brevity.<\/p>\n

Getting a representation object (<\/span><\/b>VCToolFile<\/span>) for BC<\/span><\/b><\/p>\n

You do this by calling VCProjectEngine<\/span>.LoadToolFile()<\/span>. This operation does not change state of the project system. You can call this operation any number of times, even with the same argument. In earlier editions of VS (2008 and prior), a BC was represented by a single .rules file and this method would actually parse that file. Hence the term \u201cload\u201d. However, in VS 2010, a BC is represented by up to three files and the actual parsing is done when you actually add the BC to a VCProject<\/span>, not when you call the LoadToolFile <\/span>method.<\/p>\n

\/\/\/<\/span>\u00a0<\/span><summary><\/span>\r\n\/\/\/<\/span>\u00a0Gets\u00a0a\u00a0<\/span><see\u00a0cref=\"VCToolFile\"\/><\/span>\u00a0object\u00a0that\u00a0stores\u00a0the\u00a0location\u00a0information\u00a0of<\/span>\r\n\/\/\/<\/span>\u00a0a\u00a0Build\u00a0Customization\u00a0(BC).<\/span>\r\n\/\/\/<\/span>\u00a0<\/span><\/summary><\/span>\r\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=\"targetsFileFullPath\"><\/span>\u00a0The\u00a0full\u00a0path\u00a0for\u00a0the\u00a0BC\u00a0targets\u00a0file.\u00a0<\/span><\/param><\/span>\r\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=\"engine\"><\/span>\u00a0The\u00a0VCProjectEngine.\u00a0<\/span><\/param><\/span>\r\n\/\/\/<\/span>\u00a0<\/span><returns><\/span>\u00a0A\u00a0<\/span><see\u00a0cref=\"VCToolFile\"\/><\/span>\u00a0object\u00a0corresponding\u00a0to\u00a0the\u00a0BC.\u00a0<\/span><\/returns><\/span>\r\n\/\/\/<\/span>\u00a0<\/span><remarks><\/span>\u00a0<\/span>\r\n\/\/\/<\/span>\u00a0<\/span><para><\/span>\u00a0The\u00a0.xml\u00a0and\u00a0.props\u00a0files\u00a0of\u00a0the\u00a0BC,\u00a0if\u00a0present,\u00a0must\u00a0have\u00a0the\u00a0same\u00a0name<\/span>\r\n\/\/\/<\/span>\u00a0and\u00a0be\u00a0present\u00a0in\u00a0the\u00a0same\u00a0directory\u00a0as\u00a0the\u00a0.targets\u00a0file.\u00a0<\/span><\/para><\/span>\r\n\/\/\/<\/span>\u00a0<\/span><para><\/span>\u00a0The\u00a0returned\u00a0<\/span><see\u00a0cref=\"VCToolFile\"\/><\/span>\u00a0object\u00a0is\u00a0normally\u00a0used\u00a0to\u00a0add\u00a0this<\/span>\r\n\/\/\/<\/span>\u00a0BC\u00a0to\u00a0one\u00a0of\u00a0the\u00a0containing\u00a0VC++\u00a0projects.\u00a0<\/span><\/para><\/span>\r\n\/\/\/<\/span>\u00a0<\/span><\/remarks><\/span>\r\nprivate<\/span>\u00a0static<\/span>\u00a0VCToolFile<\/span>\u00a0GetBuildCustomizationRepresentation(string<\/span>\u00a0targetsFileFullPath,\u00a0VCProjectEngine<\/span>\u00a0engine)\r\n{\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0The\u00a0term\u00a0\"load\"\u00a0in\u00a0the\u00a0method\u00a0name\u00a0is\u00a0a\u00a0legacy\u00a0artifact;\u00a0none\u00a0of\u00a0the\u00a0BC\u00a0files\u00a0are\u00a0actually\u00a0loaded.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0VCToolFile<\/span>\u00a0myBC\u00a0=\u00a0engine.LoadToolFile(targetsFileFullPath);\r\n\u00a0\u00a0\u00a0\u00a0\u00a0return<\/span>\u00a0myBC;\r\n}<\/span><\/pre>\n
Adding\/Removing\/Querying for a BC from a <\/span><\/b>VCProject<\/span><\/p>\n
The following methods demonstrate how we can add, remove and query a BC from a VCProject<\/span>. Note that both adding a BC that has already been added and removing a BC that has already been removed result in an Exception being thrown. I present two methods of query corresponding to two different types of query objects \u2013 one is the VCToolFile<\/span> representation and another is the string<\/span> object representing the targets file path.<\/p>\n
Adding a BC to a VCProject<\/span> using AddBuildCustomization()<\/span> is equivalent to performing the following action in UI: right-click the project node > Build Customizations\u2026 > check the BC entry (find it first, if necessary) and hit Ok.<\/p>\n
<\/p>\n
\/\/\/<\/span>\u00a0<\/span><summary><\/span>\n\/\/\/<\/span>\u00a0Adds\u00a0a\u00a0Build\u00a0Customization\u00a0(BC)\u00a0to\u00a0a\u00a0VC++\u00a0project.<\/span>\n\/\/\/<\/span>\u00a0<\/span><\/summary><\/span>\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=”bc”><\/span>\u00a0The\u00a0BC.\u00a0<\/span><\/param><\/span>\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=”project”><\/span>\u00a0The\u00a0VC++\u00a0project.\u00a0<\/span><\/param><\/span>\n\/\/\/<\/span>\u00a0<\/span><remarks><\/span>\u00a0<\/span>\n\/\/\/<\/span>\u00a0<\/span><para><\/span>\u00a0The\u00a0.xml\u00a0and\u00a0.props\u00a0files\u00a0of\u00a0the\u00a0BC,\u00a0if\u00a0present,\u00a0must\u00a0have\u00a0the\u00a0same\u00a0name<\/span>\n\/\/\/<\/span>\u00a0and\u00a0be\u00a0present\u00a0in\u00a0the\u00a0same\u00a0directory\u00a0as\u00a0the\u00a0.targets\u00a0file.\u00a0<\/span><\/para><\/span>\n\/\/\/<\/span>\u00a0<\/span><para><\/span>\u00a0You\u00a0need\u00a0to\u00a0first\u00a0get a representation of the BC by\u00a0first<\/span>\n\/\/\/<\/span>\u00a0calling\u00a0<\/span><see\u00a0cref=”GetBuildCustomizationRepresentation”\/><\/span>\u00a0and\u00a0then\u00a0use\u00a0the<\/span>\n\/\/\/<\/span>\u00a0returned\u00a0object\u00a0as\u00a0the\u00a0argument\u00a0to\u00a0this\u00a0method.\u00a0<\/span><\/para><\/span>\n\/\/\/<\/span>\u00a0<\/span><\/remarks><\/span>\nprivate<\/span>\u00a0static<\/span>\u00a0void<\/span>\u00a0AddBuildCustomization(VCToolFile<\/span>\u00a0bc,\u00a0VCProject<\/span>\u00a0project)\n{\n\/\/\u00a0Add\u00a0the\u00a0BC\u00a0only\u00a0if\u00a0it\u00a0has\u00a0not\u00a0already\u00a0been\u00a0added.<\/span>\nif<\/span>\u00a0(!BuildCustomizationExists(bc,\u00a0project))\n{\nproject.AddToolFile(bc);\n}\n}\u00a0<\/span><\/p>\n
\/\/\/<\/span>\u00a0<\/span><summary><\/span>\n\/\/\/<\/span>\u00a0Removes\u00a0a\u00a0Build\u00a0Customization\u00a0(BC)\u00a0from\u00a0a\u00a0VC++\u00a0project.<\/span>\n\/\/\/<\/span>\u00a0<\/span><\/summary><\/span>\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=”bc”><\/span>\u00a0The\u00a0BC.\u00a0<\/span><\/param><\/span>\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=”project”><\/span>\u00a0The\u00a0VC++\u00a0project.\u00a0<\/span><\/param><\/span>\nprivate<\/span>\u00a0static<\/span>\u00a0void<\/span>\u00a0RemoveBuildCustomization(VCToolFile<\/span>\u00a0bc,\u00a0VCProject<\/span>\u00a0project)\n{\n\/\/\u00a0Remove\u00a0the\u00a0BC\u00a0only\u00a0if\u00a0it\u00a0has\u00a0been\u00a0added\u00a0before.<\/span>\nif<\/span>\u00a0(BuildCustomizationExists(bc,\u00a0project))\n{\nproject.RemoveToolFile(bc);\n}\n}<\/p>\n
\/\/\/<\/span>\u00a0<\/span><summary><\/span>\n\/\/\/<\/span>\u00a0Checks\u00a0if\u00a0a\u00a0Build\u00a0Customization\u00a0(BC)\u00a0exists\u00a0in\u00a0a\u00a0VC++\u00a0project.<\/span>\n\/\/\/<\/span>\u00a0<\/span><\/summary><\/span>\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=”bc”><\/span>\u00a0The\u00a0BC.\u00a0<\/span><\/param><\/span>\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=”project”><\/span>\u00a0The\u00a0VC++\u00a0project.\u00a0<\/span><\/param><\/span>\n\/\/\/<\/span>\u00a0<\/span><returns><\/span>\u00a0true,\u00a0if\u00a0the\u00a0BC\u00a0exists,\u00a0else\u00a0false.\u00a0<\/span><\/returns><\/span>\nprivate<\/span>\u00a0static<\/span>\u00a0bool<\/span>\u00a0BuildCustomizationExists(VCToolFile<\/span>\u00a0bc,\u00a0VCProject<\/span>\u00a0project)\n{\nVCToolFile<\/span>\u00a0myBC\u00a0=\u00a0GetAddedBuildCustomization(bc.Path,\u00a0project);<\/p>\n
return<\/span>\u00a0(myBC\u00a0!=\u00a0null<\/span>);\n}<\/p>\n
\/\/\/<\/span>\u00a0<\/span><summary><\/span>\n\/\/\/<\/span>\u00a0Returns\u00a0an\u00a0added\u00a0Build\u00a0Customization\u00a0(BC)\u00a0from\u00a0a\u00a0VC++\u00a0project.<\/span>\n\/\/\/<\/span>\u00a0<\/span><\/summary><\/span>\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=”targetsFileFullPath”><\/span>\u00a0The\u00a0full\u00a0path\u00a0for\u00a0the\u00a0BC\u00a0targets\u00a0file.\u00a0<\/span><\/param><\/span>\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=”project”><\/span>\u00a0The\u00a0VC++\u00a0project.\u00a0<\/span><\/param><\/span>\n\/\/\/<\/span>\u00a0<\/span><returns><\/span>\u00a0A\u00a0<\/span><see\u00a0cref=”VCToolFile”\/><\/span>\u00a0object\u00a0corresponding\u00a0to\u00a0the\u00a0BC,\u00a0if\u00a0it<\/span>\n\/\/\/<\/span>\u00a0exists.\u00a0Else,\u00a0null.\u00a0<\/span><\/returns><\/span>\nprivate<\/span>\u00a0static<\/span>\u00a0VCToolFile<\/span>\u00a0GetAddedBuildCustomization(string<\/span>\u00a0targetsFileFullPath,\u00a0VCProject<\/span>\u00a0project)\n{\n\/\/\u00a0Query\u00a0for\u00a0the\u00a0BC\u00a0by\u00a0using\u00a0its\u00a0full\u00a0path.<\/span>\nVCToolFile<\/span>\u00a0myBC\u00a0=\u00a0project.ToolFiles.Item(targetsFileFullPath);<\/p>\n
return<\/span>\u00a0myBC;\n}<\/p>\n
Finally, I would like to list some driver code which I used to test the above methods.<\/p>\n
Test Driver<\/span><\/b><\/p>\n
\/\/\/<\/span>\u00a0<\/span><summary><\/span>\r\n\/\/\/<\/span>\u00a0Invokes\u00a0the\u00a0above\u00a0methods\u00a0to\u00a0test\u00a0them.<\/span>\r\n\/\/\/<\/span>\u00a0<\/span><\/summary><\/span>\r\n\/\/\/<\/span>\u00a0<\/span><param\u00a0name=\"serviceProvider\"><\/span>\u00a0A\u00a0Visual\u00a0Studio\u00a0service\u00a0provider.\u00a0<\/span><\/param><\/span>\r\ninternal<\/span>\u00a0static<\/span>\u00a0void<\/span>\u00a0TestDriver(IServiceProvider<\/span>\u00a0serviceProvider)\r\n{\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0Get\u00a0the\u00a0DTE\u00a0object\u00a0corresponding\u00a0to\u00a0the\u00a0VS\u00a0instance\u00a0this\u00a0code\u00a0is<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0running\u00a0in.\u00a0I\u00a0had\u00a0this\u00a0code\u00a0in\u00a0a\u00a0dummy\u00a0Visual\u00a0Studio\u00a0Package,\u00a0so<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0I\u00a0could\u00a0readily\u00a0access\u00a0the\u00a0VS\u00a0services\u00a0such\u00a0as\u00a0SDTE.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0DTE<\/span>\u00a0vsEnvironment\u00a0=\u00a0serviceProvider.GetService(typeof<\/span>(SDTE<\/span>))\u00a0as<\/span>\u00a0DTE<\/span>;\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0Get\u00a0the\u00a0first\u00a0project\u00a0in\u00a0the\u00a0solution\u00a0and\u00a0assume\u00a0that\u00a0it\u00a0is\u00a0a\u00a0VCProject.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0You\u00a0should\u00a0find\u00a0the\u00a0VCProject\u00a0you\u00a0are\u00a0interested\u00a0in\u00a0by\u00a0using\u00a0a\u00a0more<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0meaningful\u00a0approach.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0VCProject<\/span>\u00a0project\u00a0=\u00a0vsEnvironment.Solution.Projects.Item(1).Object\u00a0as<\/span>\u00a0VCProject<\/span>;\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0Get\u00a0a\u00a0reference\u00a0to\u00a0the\u00a0VCProjectEngine.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0VCProjectEngine<\/span>\u00a0engine\u00a0=\u00a0project.VCProjectEngine;<\/span><\/pre>\n
\r\n \u00a0\u00a0\u00a0\/\/\u00a0The\u00a0full\u00a0path\u00a0of\u00a0the\u00a0BC .targets\u00a0file\u00a0we use in\u00a0this\u00a0blog\u00a0post.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0string<\/span>\u00a0targetsFileFullPath\u00a0=\u00a0@\"C:BuildCustomizationsMyBC.targets\"<\/span>;\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0Get\u00a0a\u00a0representation\u00a0object\u00a0for\u00a0the\u00a0BC\u00a0by\u00a0requesting\u00a0the\u00a0VCProjectEngine.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0VCToolFile<\/span>\u00a0myBC\u00a0=\u00a0GetBuildCustomizationRepresentation(targetsFileFullPath,\u00a0engine);\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0Add\u00a0the\u00a0BC\u00a0to\u00a0the\u00a0VCProject.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0AddBuildCustomization(myBC,\u00a0project);\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0Both\u00a0\"exists\"\u00a0and\u00a0\"exists2\"\u00a0will\u00a0be\u00a0true.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0bool<\/span>\u00a0exists\u00a0=\u00a0BuildCustomizationExists(myBC,\u00a0project);\r\n\u00a0\u00a0\u00a0\u00a0bool<\/span>\u00a0exists2\u00a0=\u00a0(GetAddedBuildCustomization(targetsFileFullPath,\u00a0project)\u00a0!=\u00a0null<\/span>);\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0Remove\u00a0the\u00a0BC\u00a0from\u00a0the\u00a0VCProject.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0RemoveBuildCustomization(myBC,\u00a0project);\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0Both\u00a0\"exists\"\u00a0and\u00a0\"exists2\"\u00a0will\u00a0be\u00a0false.<\/span>\r\n\u00a0\u00a0\u00a0\u00a0exists\u00a0=\u00a0BuildCustomizationExists(myBC,\u00a0project);\r\n\u00a0\u00a0\u00a0\u00a0exists2\u00a0=\u00a0(GetAddedBuildCustomization(targetsFileFullPath,\u00a0project)\u00a0!=\u00a0null<\/span>);<\/span><\/pre>\n
}<\/span>\u00a0<\/span><\/pre>\n
<\/pre>\n
\"Pavan<\/a> Short Bio:<\/strong> Pavan Adharapurapu is a developer on the Visual Studio Project and Build team. <\/span><\/p>\n
 As part of VS 2010, he has worked on numerous features of the VC++ project system such<\/span><\/p>\n
 as property sheets, filters, property pages, platform and tool extensibility, etc. His long term <\/span><\/p>\n
 focus is on developing a “common project system” infrastructure which could be used to quickly<\/span><\/p>\n
 build richly featured project systems. Prior to joining the Visual Studio team in 2008, he was <\/span><\/p>\n
working on Workflow technologies in Microsoft Dynamics Axapta. Pavan holds a Masters degree in Computer<\/span><\/p>\n
Science (CS) from the University of California, Los Angeles (UCLA) and a Bachelors degree in CS from the <\/span><\/p>\n
Indian Institute of Technology (IIT), Madras. He lives in Redmond, WA with his wife and loves to play soccer<\/span><\/p>\n
and watch movies in his spare time.<\/span><\/p>\n
 <\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Build Customizations (Custom Build Rules in earlier editions) are commonly used for invoking external tools that translate files from one format to the other, often resulting in C++ sources that can be compiled at the C++ compilation step. In this post, I will explain how to programmatically add, remove,\u00a0 and query for Build Customizations in […]<\/p>\n","protected":false},"author":13,"featured_media":255385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[5,185],"class_list":["post-2043","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio","tag-csharp","tag-node-js"],"acf":[],"blog_post_summary":"
Build Customizations (Custom Build Rules in earlier editions) are commonly used for invoking external tools that translate files from one format to the other, often resulting in C++ sources that can be compiled at the C++ compilation step. In this post, I will explain how to programmatically add, remove,\u00a0 and query for Build Customizations in […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/2043","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=2043"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/2043\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/255385"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=2043"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=2043"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=2043"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
The below driver method invokes the above methods. Notice that I access the VCProjectEngine<\/span> and VCProject<\/span> objects using DTE<\/span><\/a>. Since I wrote my driver in a Visual Studio Package, the DTE<\/span> object is easily available to me. You should, however, access the project engine and project objects in a way that is most meaningful in your context.<\/p>\n