The best way to update the application

Question

I am developing a game with WPF technology. I want to add new features to the game every three days. The size of the update is important to me. my game is to start the internet. like an online game. Another issue is the size of the updates. most important: I need to update a program that does not need to stop. What is your suggestion? Is Clickonce different? Thank you for your attention. give me recommendations.

Answer 1

When deploying ClickOnce, incremental updates are performed. When deploying an update, if the date / time and hash of the file match the latest version, ClickOnce copies them from the cached version to the new version, rather than copying them over the Internet.

If you have several projects in one solution, ClickOnce will deploy each of them each time, because they will be recompiled and overwritten when creating the solution. BUT, if you have projects that you think will not change much, you can put them in a separate solution, build them and include the DLL in the main application. Then it will not be rebuilt and redrawn every time you publish, and will no longer be copied over the Internet.

As for starting work on the Internet, you can indicate that the application should run only over the Internet, which requires that the user can connect to the deploymnet manifest (.application file) and be able to check for updates every time he launches it.

Note that most people install ClickOnce to check for updates and install them before launch, which ensures that the client always runs the latest version.

I'm not sure what this means: "I need to update a program that does not need to stop."

If you want to update the ClickOnce application without forcing the user to close it, you can use the programming APIs to check the update and install it, but you will have to restart the application to install the updates. (Application.Restart ()).

Answer 2

As far as I know, clickonce will not do what you want.

One option is to take the source code for the diff diff application and modify it to compare the bytes of your binary files (V1.0 and V1.1 for arguments).

Then you will create an instruction file that explains how to turn V1.0 into V1.1 with the output of this differential program.

Then you need to write an update application that takes update instructions and turns V1.0 into V1.1 along with them.

Thus, only modified bytes were sent over the wire, not throughout the program.

Take a look at this: http://www.codeproject.com/KB/files/LPTextFileDiff.aspx

Hope this helps :-)