EricHi,
at first, I would like to say great job for this piece of software, it's great thing and I am happy that I can use it, it will definitelly safe lot of my time.
I have C# app ( www.fibix.cz ) , and I am trying to make an updater for it. I've watched your tutorials, read the faq, read all the stuff around and I stepped into the integration. Server side and updates management seemed to me pretty clear and understandable. I got into second part, which is much more confusing for me, it seemed to me , there's really not enough informations how the backend works , but maybe I didn't read properly. Finally, I have control in my app, I can check for the version, I update, download the installer ... but, when I want to install the version, I got into the really serious problem. My application tries to quit asap, but wyBuild.exe seems to be runned always with /skipinfo param, couldn't help myself. When I launch wyBuild separately, it gives me the time to select if I want to update the version, but when ClosingForInstall from control comes true, it propably always launches with /skipInfo and my process is always blocking the installation, app cannot turn off so fast. Users will be confused a lot... If the update info menu would be there, I think, it will work perfectly fine. I will be grateful for any ideas, I hope I've overlooked something.
What is also really interesting is the fact, that I created separated process for my update, and file which is running is not part of the installation, so no operation shouldn't be applied on it, am I right ?
Thanks a lot for any thoughts.
CheersEric
Starting from the top of the step-by-step walkthrough is the easiest way to get everything set up and tested properly.
What is also really interesting is the fact, that I created separated process for my update, and file which is running is not part of the installation, so no operation shouldn't be applied on it, am I right ?
I don't really understand the question.
Eric1] I really thing I've read all those things, there's really not so much info related to my issues.
2] Sorry, I'll try again.
I have the control in my app ( Launcher.exe ) , update is downloaded, I launch the application, control tells me ClosingForInstal, so I exit the app. Installer launches, but it doesn't wait for user to click to proceed the installation, it just runs the installation of the latest update, that's the issue number one, I didn't find any way how I can control this, details written in previous post.
As the installer runs the installation right after it launches, it writes me that process which was triggering the installation ( Launcher.exe ) , which holds the automaticUpdate control, is still running and needs to be stopped, which is very confusing for me, because the file itself ( Launcher.exe ) is not part of the installation update package and thus shouldn't be overwritten anywhere and shouldn't be a must to close it, but I am propably missing something.
What I did is just a standalone executable for app itself and Launcher.exe, which should handle the installation, any of the files contained in the installation package shouldn't be opened ( thus write protected ) in the time, when Launcher.exe is running, so I am quite confused, why the process needs to be closed. But, whatever, I could accept it in the worse case, and in fact, don't use the launcher at all, but the problem then stays the same. Installer will launch without possibility to proceed the installation by clicking any buttons, it just runs the installation right after the launch and my process Launcher.exe , which didn't catch to quit, is then request to close. This annoying message will really confuse any user ...
Thanks for the patience, I really need this working.
Sorry, I meant to get back to you right away. Somehow this slipped through.
I have the control in my app ( Launcher.exe ) , update is downloaded, I launch the application, control tells me ClosingForInstal, so I exit the app. Installer launches, but it doesn't wait for user to click to proceed the installation, it just runs the installation of the latest update, that's the issue number one, I didn't find any way how I can control this, details written in previous post.
This is the default behavior of the AutomaticUpdater. It (the AutomaticUpdater) checks for updates, downloads them, extracts them, and patches the files. Then, when the update is prepared, it show wyUpdate to finished the process.
If you want to give the user control you can either give them control over the AutomaticUpdater (using events, methods and properties of theAU) or use wyUpdate in standalone mode.
As the installer runs the installation right after it launches, it writes me that process which was triggering the installation ( Launcher.exe ) , which holds the automaticUpdate control, is still running and needs to be stopped, which is very confusing for me, because the file itself ( Launcher.exe ) is not part of the installation update package and thus shouldn't be overwritten anywhere and shouldn't be a must to close it, but I am propably missing something.
All exes in the "base" directory (the directory where wyUpdate.exe is sitting) must be closed (with the exception of wyUpdate.exe, of course).
So either close the launcher program (why would it be running? The AU re-opens your app after a successful update) or put the launcher program in a directory "up" from the base directory.
Does that make sense?
EricHey,
Thanks for the reply !
From you ( I can't find quote, sorry ) :
This is the default behavior of the AutomaticUpdater. It (the AutomaticUpdater) checks for updates, downloads them, extracts them, and patches the files. Then, when the update is prepared, it show wyUpdate to finished the process.
If you want to give the user control you can either give them control over the AutomaticUpdater (using events, methods and properties of theAU) or use wyUpdate in standalone mode.-----------------------------------------------------------------------------------------------------
Yes, in the end, what I did, is that I am running the final launch of the installation via command line in silent mode. But, why it confused me was, that when I launched wyUpdate file, it gave me the time, to click Next, the installation itself ( copying of files ) didn't start before I click to proceed ( or next, or whatever button is it.. can't remember now, but hope it's clear what I mean ) . When you let it go via app , it says closing. .. I close app. It launches the wyUpdate and then it goes directly to the instalation. I was trying to find the console setup or change it for this behaviour .. but unsuccessfuly 🙁o but anyway, my point is, that it behaves differently so it made me confused and in the end, I need to run it via command line, so it didn't save lot of time from this point of view ... 🙁o I hope, i had verified, that we both mean the same thing right now, if not, please fix me... Thank you..
----------------------------------------------------------From you ( I can't find quote, sorry ) :----------------------------------------------------------So either close the launcher program (why would it be running? The AU re-opens your app after a successful update) or put the launcher program in a directory "up" from the base directory.
-----------------------------------------------------------it seemed to me nice, that it can still run so I can transparently made the installation , without need to close the launcher, this is the way, how it is usually done in lot of applications ( I guess at least, from what I've seen and been told ). But you propably rewrite the whole folder, or something, rather than copying the files themselves ... right ?
Thanks again !
