WHen installing a delivery and then signing the F1Mage a new manifest file is created and downloaded on users laptops the first time the access the application after the delivery. This then prompts all DLLs to be re-downloaded even though no dll files are changed.
Is this how it is supposed to work?
+18
I’m pretty sure that’s how it has always worked.
After re-signing the certificate I believe it treats it like a new application and therefore needs to download the ‘new’ files, even if those are ones previously downloaded under the prior application. If you apply a delivery and do not re-sign - which may be possible depending on the content of the delivery - then it should not do this.
Nick
Hi
Yes, this is definitely how click once will behave. As soon as the manifest changes and has a new signature, the client cache will assume that there are new dll’s in the server and will download them to bring the client cache to the same version.
What is interesting is why the manifest has been resigned in the first place. If there are no client file changes, there is no real reason for the delivery to even have a “client” folder. If there is no client folder in the delivery, the installer should not resign the manifest. Assuming this is Apps10, the only scenario where this can happen is that if you do a reconfiguration as part of the delivery and have the “automatically sign the client” check box checked.
cheers
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
