In my automated build I'm using both steps in one go -> ... /bu /bwu -add=... that works fine.
Command line -add
glengHi guys,Bought wyBuild a few days ago and have stumbled on a lil' problem while integrating it into my build process.
Using wybuild.exe /bu -add="c:\newversion.xml" works perfectly - updates are created and the new version is added to the project.Using wybuild.exe /bwu -add="c:\newversion.xml" outputs wyBuild and Client.wyc but doesn't add the new version to the project.
Am I doing something wrong?
Cheers
Glen
glengThanks for your reply Frederick - yes, that works for me too - but /bwu alone with -add doesn't.
I wanted to run /bwu with -add first in the process so I could create the client.wyc file and then add it to the update folder before running /bu to create the update. But thinking about it this evening, I'm wondering if including a client.wyc in the update is possibly not required. (I'll do some more forum reading...and perhaps someone with more understanding could clarify)
Cheers!
Hey Glen,
These are great questions.
Adding the client.wyc is only required if you changed images, your company name, product name, etc. See the FAQ for a list of what client.wyc contains. If you change any of those things, include the client.wyc with your updates.
If you didn't change any of those things, you can include client.wyc as well. There's no harm.
Lastly, you don't need to split building wyUpdate and building the updates into 2 steps. When you use the /bwu, /bu, and -add commandline switches, the new versions are added/removed first, wyUpdate is always built second, and the updates are always built last.
This means that you can specify the new client.wyc file in your XML files even if the client.wyc doesn't exist on disk before you run wyBuild. Just check where the output folder will be in your project (File -> Properties, "wyUpdate" tab) then specify that path in the XML file. For example:
<Files dir="basedir"> <File source="C:\YourProduct\wyUpdate\client.wyc" /> ...</Files>Tell me if this helps.
glengHi Wyatt,
I have a much better understanding of client.wyc now - thanks.
The question raised in my mind after thinking about your reply is this...
If I do change the contents of client.wyc and if I am pointing to the same location for client.wyc in each update - won't that stop it from being added to the patch?
i.e. I create version 1.1 and point to "C:\YourProduct\wyUpdate\client.wyc" (as per your example), and then later create 1.2 and point at the same location - won't that cause wyBuild to think when comparing versions that there is no difference and therefore exclude the file from 1.2?
This was my original thought process and why I wanted to run /bwu first, then move client.wyc and then run /bu. Hope this makes sense.
Regards,
Glen
The "client.wyc" files are a special case within wyBuild. wyBuild always includes the full "client.wyc" files - it never tries to patch the file. We designed it this way for a number of reasons, and this is one of them.