You're right, wyBuild should let you do this. People are probably going to cringe when I say this, but we're going to delay wyBuild 2.6.15 a bit longer to get this fixed.
Thanks for spotting this.
Hi Sam,
we are using wybuild to update our services. I am using Update Actions to stop and start the services before and after the update. But the problem is i have two services which are dependent. First i need to stop the ClientService then i need to stop the ServerService. But after update finish i need to start the serverservice first then only ClientService. When I add these services to update actions, the services are getting sorted in alphabetical order. Can you please let me know how to resolve this issue. If i try to stop the ServerService, then it will throw error saying dependent services are existing.
Thanks,Banu
You're right, wyBuild should let you do this. People are probably going to cringe when I say this, but we're going to delay wyBuild 2.6.15 a bit longer to get this fixed.
Thanks for spotting this.
Hi, I have one doubt to clarify regarding the Wybuild. We are using wybuild to update the project. The initial version of the update is v1.0.0.0. I created a Wybuid project with name xxx and added update information for v1.0.0.0 and respective files and uploaded to server. When i check the files uploaded to the server are all to v1.0.0.0. After tha I added another version to wybuild project v1.0.0.1 without removing the v1.0.0.0, now i build and upload it to server. the files created are 1.0.0.0 to 1.0.0.1 and all to 1.0.0.1 , two files got created and uploaded to server. It is going for past 6 months already. The problem now is, the latest update versionn in my project is v1.0.8.2. when I build the xxx project with all these versionsit takes lot of time to build and upload the files as it need to generate the respective files (around 82 files i.e v1.0.0.0 to v1.0.8.2, v1.0.0.1 to v1.0.8.2 , v1.0.0.2 to v1.0.8.2 ..... all to v1.0.8.2). It is quite huge and the server space is being occupied mostly by this. So what i have done is, in my wybuild xxx project, when i create a new version v1.0.8.3, i remove all the previous versions from v1.0.0.0 to v1.0.8.2. so i left only with v1.0.8.3 then i build and upload it to server, which created only one file all to v1.0.8.3. When i check for latest updates, it shows v1.0.8.3 is available and it is getting the latest files from server. As i am dealing with production, i can not play with it. So i want to know how really wybuild works. So is it safe to remove all the versions or do i need it for future reference? is only all to v1.0.8.3 file is enough to get updates? please explain.
Regards,Banu
Hey Banu,
As i am dealing with production, i can not play with it. So i want to know how really wybuild works. So is it safe to remove all the versions or do i need it for future reference? is only all to v1.0.8.3 file is enough to get updates?
It's not recommended to remove old version from wyBuild unless you absolutely know that all your users have upgraded to a newer version and that none of the users will ever use an old version of your software again.
We're working on this problem for wyBuild 2.7 where we'll have incremental patches (A->B, B->C) instead of just having direct patches (A->C, B->C). With incremental patches you'll only upload the latest changes to your server.
But in the meantime it's best just to leave your old versions in your project.
Hi Wyatt,
If user is having v1.0.0.0 and the server contains all to 1.0.8.3 file only will the user get latest 1.0.8.3 version or not?Thanks,Banu
.. will the user get latest 1.0.8.3 version or not?
He will not. In wyBuild 2.7 we'll make the amount of data you have to upload to your server a lot less. In the meantime you have to build all the patches.
Sorry.
Thanks for your immediate response Wyatt.
Can i takeout the "Cancel" button in the dialogue prompted when any update available? If can, then please let me know the procedure. Do i need to change the WyUpdate source code?
Thanks,Banu
Yes, you can remove the cancel button by modify the source code. But you absolutely should not do this. Because if a user really wants to cancel they'll just kill the process (instead of clicking cancel).
The cancel button rolls back updates. Killing the process does not.
Why do you want to remove the cancel button?
Hi Wyatt,
Thanks for your reply. My Boss worried that , the user might click 'Cancel' button when the updates are being asked. He requested me to check into it.
Regards,Banu