Clarify - building updates directly from Release directory

a few questions in-line below. (I also cannot watch the videos at work. watching them tonight may answer some questions)

I started using this today and built a small test. Ran a few different iterations and found one where i was told the update worked, but inspection of the file shows that the update really did not happen. Running update now says that it is up to date, but the app is not up to date.

I would like to purchase wyBuild, but this is a show stopper.

looking through the forums I found this:

"But, as it is now, you need to keep every version of your software."

Is that still true? So what is the typical setup for projects? I typically compile everything under \bin\release. Would I create a folder for each release and move the files there, then build the new version (Update Information) from that folder?

I also see that it is often recommended to use a product like Inno to distribute the application? Is this still true?

Thank you. Hoping to be able to purchase and use the product.

a few questions in-line below. (I also cannot watch the videos at work. watching them tonight may answer some questions)

Why can't you watch the video? Is YouTube blocked at work, or is all video blocked?

I started using this today and built a small test. Ran a few different iterations and found one where i was told the update worked, but inspection of the file shows that the update really did not happen. Running update now says that it is up to date, but the app is not up to date.

I would like to purchase wyBuild, but this is a show stopper.

looking through the forums I found this:

"But, as it is now, you need to keep every version of your software."

Is that still true?

Yes.

So what is the typical setup for projects? I typically compile everything under \bin\release. Would I create a folder for each release and move the files there, then build the new version (Update Information) from that folder?

Yes, create a separate folder for each version of your software. For example:

C:\YourSoft\1.0\C:\YourSoft\1.1\etc.

And add the files from these directories to wyBuild.

We realize this is a conceptual hurdle for new users. We're working to make this easier.

I also see that it is often recommended to use a product like Inno to distribute the application? Is this still true?

Well, I personally recommend NSIS. Or even WiX. But Inno is another option. But yes, we require you use a 3rd party installer. This will be changing in the near future in a couple of ways. Soon wyBuild will allow you to build...

  • A web installer. That is, the user downloads a tiny executable which then downloads & installs your required files.
  • A full installer. We'll be integrating NSIS and WiX within wyBuild. You'll be able to simply click a button to build your installer.

Tell me if this helps.

most video at work is blocked.

I understand the folder stuff. just need to change the way I think.

I have an application already deployed to about 60 people. As I understand it I need to:

1) Create an install using a 3rd party tool, including wyUpdate.exe and client.wyc to the base folder. Copy these files to my distribution server.

2) Distribute the latest release (first release with auto update added to it). Can I manually run the wyupdate.exe that is on the server to install the latest release or do I have have to run the exe created by the install application.

Questions:

1) the update screens run fast and then close. is there any way to pause or slow down each screen?

2) I don't want my users to manually check for updates. I want to check everytime the application starts and possibly other times. (apps are sometimes not closed for days) Can I call wyupdate.exe directly from my code? If so, do i run the wyupdate.exe that is on my server or do I run one that is local to the PC?

Thank you.

1) Create an install using a 3rd party tool, including wyUpdate.exe and client.wyc to the base folder. Copy these files to my distribution server.

That's correct. Add wyUpdate & the client.wyc along with your programs files to the installer.

2) Distribute the latest release (first release with auto update added to it). Can I manually run the wyupdate.exe that is on the server to install the latest release or do I have have to run the exe created by the install application.

You could force all your users to download the wyUpdate.exe and client.wyc files and put these files in the base folder. Or you can just make a new installer and deliver updates to people with this new installation onward.

Questions:

1) the update screens run fast and then close. is there any way to pause or slow down each screen?

Why do you need it to go slower?

2) I don't want my users to manually check for up

dates. I want to check everytime the application starts and possibly other times. (apps are sometimes not closed for days) Can I call wyupdate.exe directly from my code? If so, do i run the wyupdate.exe that is on my server or do I run one that is local to the PC?

You can use either the AutomaticUpdater control, or using wyUpdate in standalone mode for the silent updating. Running wyUpdate.exe on your server will do nothing. What wyUpdate does is download and install the update on your users machines. So it has to be installed alongside your app.

Both the AutomaticUpdater and wyUpdate in standalone mode give you fine-grained control over when updates are checked for, etc.

Thank you for the response. It looks like I will have to keep an installer around for any new users and I can use wyupdate (either Automatic control or wrap standalone mode into a process)