EGrant63Hello,
I am attempting to automate the build of one of our applications and I am running into some problems with the cmdline runner recognizing my new updates. When I run the cmdline tool with the following arguments, it says that building wyUpdate and Building updates are successful.
.\wybuild.cmd.exe "$wypFile" /bu /bwu -add"$newVersionXML"
Where $wypFile is the current wyp file and $newVersionXML is the following XML File.
<?xml version="1.0"?>
-<Versions>
-<AddVersion>
<Version>17.10.18.1220</Version>
<Changes>These are all the changes!</Changes>
<InheritPrevRegistry/>
<InheritPrevActions/>
-<Files dir="basedir">
<Folder source="C:\My\Application\Directory" insideonly="true"/>
</Files>
</AddVersion>
</Versions>
Is my XML file OK? And do I also have to define the previous version that I am building from?
Thanks
The XML looks fine, but after running it you can always visually see what was added by opening the project in wyBuild.
>> "And do I also have to define the previous version that I am building from?"
If you add the version in wyBuild it keeps the old version around (so that wyBuild can efficiently build patches from the old version to the new version).
EGrant63Wyatt,
I am still having some problems with the cmdline tool recognizing my new version. I am able to run it and it will build all previous versions just fine. If I open the project in WyBuild, the new version does not appear either. If my XML file looks good, then is the problem with the path to the XML file?
For the -add switch, I am putting in the full path of the XML file. Is that correct or does the file need to be in another directory?
Hi, ensure your wyp file has write access: I ran into a similar issue when my project file was read only, in my case for the check-in into source control.
