ClickOnce更新所有文件。为什么? [英] ClickOnce updates all files. Why?
问题描述
< GenerateDeploymentManifest AssemblyName =MyApp.exe.application
AssemblyVersion = 1.0.0.0
DeploymentUrl =\\ ... \MyApp.exe.application
Product =Egs.Client
TargetCulture =ru-RU
描述=我的应用程序
Publisher =MyCompany
Install =true
UpdateInterval =1
UpdateUnit =Weeks
UpdateEnabled =true
UpdateMode =Background
OutputManifest =$(ApplicationFile)
MapFileExtensions =true
EntryPoint =@(DeploymentManifestEntryPoint)/>
即使我只是将1.0.0.0更改为1.0.0.1,客户端将下载整个应用程序再次。
我错过了某些东西或者是标准行为?
如果程序集更改,将会下载。重建一个组件是一个变化。我通常跳过Visual Studio来创建部署,并使用 Mage 。然后,我不要在所有程序集建立的bin处点法师,我将其指向一个单独的文件夹,我手动复制我想要部署的程序集。有意义吗?
I've got small wpf application deployed using ClickOnce technology. The problem is that when I build new version clients download all files, though many of these files have not been changed. I use following configuration to make deployment manifest
<GenerateDeploymentManifest AssemblyName="MyApp.exe.application"
AssemblyVersion="1.0.0.0"
DeploymentUrl="\\...\MyApp.exe.application"
Product="Egs.Client"
TargetCulture="ru-RU"
Description="My application"
Publisher="MyCompany"
Install="true"
UpdateInterval="1"
UpdateUnit="Weeks"
UpdateEnabled="true"
UpdateMode="Background"
OutputManifest="$(ApplicationFile)"
MapFileExtensions="true"
EntryPoint="@(DeploymentManifestEntryPoint)" />
Even If I just change "1.0.0.0" to "1.0.0.1" clients will download whole application again. Am I missing something or it's standart behaviour ?
If an assembly changes at all it will be downloaded. Rebuilding an assembly counts as a change. I typically skip Visual Studio for creating deployments and use Mage instead. Then I don't point Mage at the bin where all the assemblies get built, I point it at a separate folder where I manually copy in assemblies I want deployed. Make sense?
这篇关于ClickOnce更新所有文件。为什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!