wyBuild and Previous Versions

I purchased wyBuild a few months ago and am just getting around to using it. When updating between versions (i.e. 1.0 to 2.0) do you need to need to keep the 1.0 binaries around to merge against?

Just trying to plan, and trying to determine if I need to keep the binaries for every build available somewhere.

Thanks in advance.--Chad

Hey Chad,

Yes you need to keep all the version binaries around. wyBuild onl references the files from disk -- it doesn't store the files for you. This is explained in the step-by-step walkthrough.

Any tips or best practices for doing this over the long term? Does wyBuild use relative or full paths? I am thinking of storing every release build in subversion, but I am wondering if I have to checkout to the exact same directory every time.

--Chad

Right now wyBuild store full paths in the project file (*.wyp file). But this will be changed to relative paths in the near future.

Any updates on a releast date for v2.7 with relative paths?

We're working on it. We don't have a firm release date.

Any updates on this? I recently purchased wyBuild and would definitely appreciate relative paths.

Hey George,

Yes, this is still coming with wyBuild 2.7. We're shooting for a late-January or mid-Feb release.

Any news then?

We're looking at integrating wyBuild into one of our products and if the "relative path" release is within a couple days, then we'd probably rather wait until then to start the process. Days, weeks? Dare I ask: months?

We can do a special release of wyBuild that just adds the relative path ability, if you'd like that. It will take at least 3 or 4 days.

Considering this issue goes back a couple years (earliest mention on the forum is August 2009), I think an early release would be warranted. ;D

Ok. We'll release a new version with this feature implemented on Moday or Tuesday.

wyBuild 2.6.17 is now out. Relative paths are now the default.

Reply
Discard post