{"id":7131,"date":"2020-12-23T08:54:51","date_gmt":"2020-12-23T16:54:51","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=7131"},"modified":"2020-12-23T08:55:41","modified_gmt":"2020-12-23T16:55:41","slug":"importing-msbuild-property-sheets","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/documentation\/projects\/msbuild\/propertysheets\/importing\/","title":{"rendered":"Importing MSBuild Property Sheets"},"content":{"rendered":"

VisualGDB supports importing variables from MSBuild property sheets, so that they can be used anywhere throughout VisualGDB Project Properties. This page provides brief instructions to do it.<\/p>\n

First of all, create a property sheet file (e.g. test.props) that will define the necessary properties inside a PropertyGroup<\/strong> with the “UserMacros<\/strong>” label:<\/p>\n

<?xml version=\"1.0\" encoding=\"utf-8\"?> \r\n<Project ToolsVersion=\"4.0\" xmlns=\"http:\/\/schemas.microsoft.com\/developer\/msbuild\/2003\">\r\n  <PropertyGroup Label=\"UserMacros\">\r\n    <TestProperty>TestValue<\/TestProperty>\r\n  <\/PropertyGroup>\r\n<\/Project><\/pre>\n
Then, add the following lines to the .vgdbsettings<\/strong> file (or the .vgdbcmake\/.vgdbproj<\/strong> file when using advanced project types) directly under the VisualGDBProjectSettings2<\/strong> element:<\/p>\n
  <ImportedPropertySheets>\r\n    <ImportedPropertySheet>\r\n      <Path>PropertySheet.props<\/Path>\r\n    <\/ImportedPropertySheet>\r\n  <\/ImportedPropertySheets><\/pre>\n
The Path<\/strong> element should contain the relative path to the property sheet file that is being imported.<\/p>\n
The $(TestProperty)<\/strong> expression can now be referenced anywhere in the VisualGDB Project Properties (e.g. directory uploading settings, build commands, custom build\/debug actions). You can test it by adding a custom pre-build action running “cmd.exe \/c echo $(TestProperty)<\/strong>“. In this example, it will output “TestValue<\/strong>“.<\/p>\n
Although VisualGDB cannot fully evaluate MSBuild conditions, you can use the syntax below to limit the properties imported by VisualGDB:<\/p>\n
<ImportedPropertySheet>\r\n    <Path>PropertySheet.props<\/Path>\r\n    <MatchingCondition>'$(Configuration)' == 'Debug'<\/MatchingCondition>\r\n<\/ImportedPropertySheet><\/pre>\n
This will restrict the imported variables to variables with no condition and variables where the condition is set to exactly ‘$(Configuration)’ == ‘Debug’<\/strong>.<\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
VisualGDB supports importing variables from MSBuild property sheets, so that they can be used anywhere throughout VisualGDB Project Properties. This<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[227],"tags":[],"_links":{"self":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/7131"}],"collection":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/comments?post=7131"}],"version-history":[{"count":1,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/7131\/revisions"}],"predecessor-version":[{"id":7132,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/7131\/revisions\/7132"}],"wp:attachment":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/media?parent=7131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/categories?post=7131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/tags?post=7131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}