Some feature suggestions...

Hello again, Sorry about my mistakes from the previous post but it was sent "premature". There are 4 suggestions not 2 and the post subject would have been "Some suggestions...".

Sorry again. 🙂

1. Add ExecutionArguments in the automatic update state file (wyUpdate.frmMain.SaveAutoUpdateData and wyUpdate.frmMain.LoadAutoUpdateData). (if (updateHelper.ExecutionArguments != null) {WriteFiles.WriteString(fs, 0x0C, updateHelper.ExecutionArguments);}).

Thanks for spotting this. We'll add this for wyUpdate 2.6.11.

2. Add arguments for starting services after/before update. (arguments to send to OnStart function of the NT service.)3. Could you please add a bool for each exe that we set to execute in order to rollback update (or not) if exit code is != 0?

Ok, we'll add these to wyUpdate 2.6.11 or 2.6.12.

4. Could you please parameterize the client file name (client.wyc)

I'm not quite sure what you mean. Can you clarify this?

Sorry about my mistakes from the previous post but it was sent "premature". There are 4 suggestions not 2 and the post subject would have been "Some suggestions...".

No worries. 😉

4. Could you please parameterize the client file name (client.wyc)

I'm not quite sure what you mean. Can you clarify this?

wyUpdate is searching for a file named "client.wyc" to take some information. I want that name to be parametrized. For example, I want my clients to have in the application folder: file_1, file_2, ... , file_n and for the udpate process: "update.exe" and "payroll.nfo" instead of "wyUpdate.exe" and "client.wyc".

Thank you for your quick feedback.

You can already do this using the "-cdata" parameter. For instance:

wyUpdate.exe -cdata:"C:\YourApp\payroll.nfo"

You can already do this using the "-cdata" parameter. For instance:

wyUpdate.exe -cdata:"C:\YourApp\payroll.nfo"

Yes, you are right. My misunderstanding. Sorry.

One last question: Do you have an update of the estimation for updating of the NT service.

Thank you.

One last question: Do you have an update of the estimation for updating of the NT service.

Do you mean the AutomaticUpdater that can be run from Windows Services? We've just finished this, it will be included with wyBuild 2.6.11 which is coming in about a week.

Hey Mishu,

wyBuild 2.6.11 is now out.

1. Add ExecutionArguments in the automatic update state file (wyUpdate.frmMain.SaveAutoUpdateData and wyUpdate.frmMain.LoadAutoUpdateData). (if (updateHelper.ExecutionArguments != null) {WriteFiles.WriteString(fs, 0x0C, updateHelper.ExecutionArguments);}).

Thanks, we've fixed this.

2. Add arguments for starting services after/before update. (arguments to send to OnStart function of the NT service.)

You can now specify the arguments you want to pass to your service.

3. Could you please add a bool for each exe that we set to execute in order to rollback update (or not) if exit code is != 0?

You can now specify whether you want the update to rollback on non-zero return codes.

One last question: Do you have an update of the estimation for updating of the NT service.

We now fully support silently updating services either with wyUpdate in standalone mode or, if your service is .NET, use the AutomaticUpdater in your service.