jdavidi
06-16-2010, 12:22 PM
Greetings!
We're attempting to leverage Visual Build's read/write XML capabilities to aid in a large scale csproj file update. Essentially, we're looking to specify the Target Platform to be x86 for all current build configurations (this is a change from its default of AnyCPU).
This involves the addition of the following element to each of the <PorpertyGroup> nodes that are concerned with build configurations:
<PlatformTarget>x86</PlatformTarget>
The attached bld file I believe is correctly querying out the 2 nodes in the sample csproj file correctly, and it adds an almost-correct node,
<TargetPlatform xmlns="">x86</TargetPlatform>
to the first of these 2 Property groups.
I'm unsure of :
a) if a loop is needed, the syntax for the write XML step to go after the one particular node in turn (or can the Update All Matching Nodes property be used instead of a loop?)
b) why xmlns="" is getting added. I presume this is due to the XPath expression (of which I'm also new to).
Thanks for any help!
--jdavidi
We're attempting to leverage Visual Build's read/write XML capabilities to aid in a large scale csproj file update. Essentially, we're looking to specify the Target Platform to be x86 for all current build configurations (this is a change from its default of AnyCPU).
This involves the addition of the following element to each of the <PorpertyGroup> nodes that are concerned with build configurations:
<PlatformTarget>x86</PlatformTarget>
The attached bld file I believe is correctly querying out the 2 nodes in the sample csproj file correctly, and it adds an almost-correct node,
<TargetPlatform xmlns="">x86</TargetPlatform>
to the first of these 2 Property groups.
I'm unsure of :
a) if a loop is needed, the syntax for the write XML step to go after the one particular node in turn (or can the Update All Matching Nodes property be used instead of a loop?)
b) why xmlns="" is getting added. I presume this is due to the XPath expression (of which I'm also new to).
Thanks for any help!
--jdavidi