Unless what you have is a massive multi-megabyte end-user application, generating patches (which I assume you want to be minimal) is a daunting task, since you'll have to provide patches from each previous version to the most up-to-date one.
Alternatively, you can invest into autoupdate infrastructure, so that an app will update itself whenever a new version is released.
As for building setups for each commit, I personally don't think this is neccessary unless you're continuously testing setup program itself. Rather, complete build should be triggered manually, whenever it's time to release.
发布评论
评论（2）
除非您拥有的是一个巨大的多兆字节最终用户应用程序，否则生成补丁（我假设您希望将其最小化）是一项艰巨的任务，因为您必须提供从每个先前版本到最新版本的补丁-约会一。
或者，您可以投资自动更新基础设施，以便每当发布新版本时应用程序都会自行更新。
至于为每次提交构建设置，我个人认为这是没有必要的，除非您不断测试设置程序本身。相反，无论何时发布，都应该手动触发完整的构建。
Unless what you have is a massive multi-megabyte end-user application, generating patches (which I assume you want to be minimal) is a daunting task, since you'll have to provide patches from each previous version to the most up-to-date one.
Alternatively, you can invest into autoupdate infrastructure, so that an app will update itself whenever a new version is released.
As for building setups for each commit, I personally don't think this is neccessary unless you're continuously testing setup program itself. Rather, complete build should be triggered manually, whenever it's time to release.
您应该查看类似 Microsoft 的 ClickOnce 获取更新/补丁。
You should look at something like Microsoft's ClickOnce for updates / patches.