Re: Click Once Install Defaults

[RobinS]

"Steve Gerrard" <my********@comcast.netwrote in message
news:1t******************************@comcast.com. ..

RobinS wrote:

>"Steve Gerrard" <my********@comcast.netwrote in message
news:0b******************************@comcast.com ...

>>>
Interesting, I had not heard that. How would it manage to keep track
of where the assembly was, if it was not in the GAC and not in the
app folder? It seems like havoc would reign if the user uninstalled
the other app, and somehow that dll has to now get put in the second
app folder. Oh wait, maybe it just sees it missing and downloads it
from the install site again...

Forgot to answer this one.

If you look in the obfuscated folder where your deployment resides,
you will see a whole bunch of folders -- I think there's one for each
dll that you deploy.

For example, our application uses DirectX deployed locally (not put
in the GAC), and although I have two versions of the app installed
(because ClickOnce lets you back the most current one out if it's not
a forced upgrade), I only have one folder for DirectX, called
something like micr...bunchofobfuscated stuff.

I did look, and did notice that only three or four dlls have two copies,
the rest are down to one. I'm still curious if that can be coordinated
between two different apps. Thanks for looking into it...

Sorry for the late response. Been working a lot.

So here's the deal with this: If you strongly sign your assemblies, and they
are used by multiple applications, they will only be copied down from the
server once. The application manifest tells if it is using it locally.

When it is doing updates, it checks the version in those folders that appear
for each assmebly against the one coming from the server, and if it is not
different, it copies it from the local cache folder over to the new
version's folders rather than downloading it from the server.

Now, Brian Noyes said that it does that when you strongly sign the
assemblies, but we are seeing *that* behavior without having all of our
assemblies strongly signed, so maybe I misunderstood him. It takes 3-4
minutes to install our application, but less than 1 minute to install
updates.

Hope this helps.

RobinS.
GoldMail.com