%version% BugsSolved

Hey Omaer,

However, the 'Output the wyUpdate filest to:' path does not expand the variable properly. For example, the folder created actually contains %version% in the name.

This is by design. wyUpdate.exe and the client.wyc don't need to be output to a version specific folder (you can rebuild previous versions by selecting them in the dropdown above the "Build wyUpdate" button).

Another problem I noticed where %version% is not correct is in the Registry Changes section.

This is a bug, thanks for spotting it. We'll fix this in the version after 2.6.15 (probably 2.7).

Hi Sam

Thanks for the quick reply.Here's the thing: For the 'Output the wyUpdate files to:' path, if one enters %version%, then the version number is expanded, but the folder is not created.

For example, here's what happens:Output the wyUpdate files to: C:\Temp\%version%Version Number: 11.06

Scenario 1:Contents of C:\Temp before building the update: emptyWhen you click on Build Updates, you get an error and the updates fail to build.Contents of C:\Temp after building the update: an empty folder named %version%

Scenario 2:Contents of C:\Temp before building the update: an empty folder named 11.06When you click on Build Updates, you do not get an error, and the updates are built successfully.Contents of C:\Temp after building the update: an empty folder named %version%, and the client.wyc file, and the wyupdate.exe file are now inside the folder named 11.06

Therefore, the variable is actually being expanded correctly, except when the new folder is being created.

Also, if it isn't too difficult (and I imagine it should not be since only the folder creation is lacking the variable expansion), then would it be possible to add this as a feature? In my workflow, I need to keep the older wyc's as well, not just the latest (enterprise requirements - things aren't so straightforward here)... So I'd appreciate not having to copy and paste the files manually...

Thanks!

Ok, we'll add that for 2.6.15.

Thanks Sam...

wyBuild 2.6.16 is now out -- these bugs are fixed.

HI Wyatt/Sam

I just tested with 2.6.17.1, and the %version% variable is still not updating in the Registry changes section.Quoting the initial problem from my first post in this thread:

Another problem I noticed where %version% is not correct is in the Registry Changes section.I added a registry entry with Value Name: version, and Value Data: %version%This should be a simple enough change and it seems to work. When you create a new version, and look under registry changes, the version number is reflected there. The problem happens if you manually change the Version number. For example, my application jumped from version 11.02 to version 11.06. When I added a new version, wyBuild assigned it a default name of 11.03. When I renamed the version number to 11.06, the registry change still showed 11.03 instead of being changed to 11.06. The only was to rectify this was to delete the registry change and then add it again.

Not an urgent request since it isn't too difficult to make the change manually, but thought I'd let you know...

Thanks

Omaer

Sorry, you're right, the registry bug is not fixed (using variables in the output folder is fixed). I should've read the post more carefully when saying all the bugs have been fixed.

The impact of the registry bug is smaller than you think. When you change the version, and you have a registry value that depends on that version variable, the node won't be updated (as you've correctly reported). However, when you build your updates wyBuild will use the correct version number. So the problem is really a display problem. Everything in the background still works.

This is an important bug, though, so I'm not dismissing it. We'll be fixing it soon(ish). There are higher priority bugs we want to get squashed first.

Yup you're right... that's fiine then. If I close the project and open it again, the value is displayed correctly.Thank's for pointing that out - I'll stop deleting and re-adding values!