Executable file and the update process

I have an executable file that is being executed at the end of the update process. We are thinking about only having this run when necessary (to process database changes).

Here is a scenario where we have a question.Versions 1 and 2 have database changes, 3 does not have a database change (so the process is not run) , 4 does a database change , but 5 does not. Our users have the option of the application running the updates automatically or they can manually check for updates. A user is manually checking for updates and they last updated to version 3 but now we are on version 5. If they run the update, will wyupdate run the executable file for version 4 (will it play catch-up with the executable file)?

The current way wyBuild builds patches means that the executable listed in the latest version of your app is the only one that will be executed. The best way to handle this currently is to use the %versionto% and %versionfrom% variables and in your script apply database changes based on those values.

Need sample application for database updates by using windows service.Need to update database by using Silently update through windows service.please help me.

It depends on a thousand things (what database you're using, the name of the database, where your credentials are stored, etc., etc., etc.). Here's a general overview of the process: Updating databases (Microsoft SQL Server, MySQL, etc.)