I solved the mystery of the missing files (process error), but it would be useful to know if there is a way either to log what files are affected by the patch, or look into the .wyu file to see what's there.
Thanks!
I am using the command line build for my updates, updating from version 1.0 to version 1.1. I have a a target folder that is to be populated from a source folder as follows:
<Files dir="Reports"> <Folder source="C:\Releases\Version1.1\Reports" insideonly="true"/></Files>The new version contains two files in the source folder that are not present in the previous version's source folder.
I expected those two files to appear on the target system after I ran my update, but they did not. I am currently trying to determine why. When I look at the built .wyp file in the wyBuild GUI, it doesn't list the files that were found in the source folder, so I can't use that method to determine whether or not the new files made it into the update.
Is there some other way to find out exactly what's there? Does the command line builder have a logging mechanism that I don't know about?
Thanks in advance for any insight you can give me.
I solved the mystery of the missing files (process error), but it would be useful to know if there is a way either to log what files are affected by the patch, or look into the .wyu file to see what's there.
Thanks!
Can you tell me what the problem was so we can write a proper error handler for it?
The problem was that our automated build process was copying the files into the source folder _after_ the command-line update build took place. I looked at the source folder only after the build was complete, so the files were there by then.
Obviously, you don't need to write an error handler; we need to ensure that our build batch file gets the source files into place before we ask wybuild.cmd.exe to build the updater !
I think a nice feature for wybuild.cmd.exe would be the ability to ask for various levels of logging (info/warning/error/fatal), so it could, for example, spew property values, what files/changes are getting built into the update, exceptions, etc. Then it would have been obvious that the source folder was empty and I would have found the problem sooner.
I'm not complaining, it's a great product!
Ok, we'll show a warning if you add a folder but nothing is inside of it.