I have heard that Microsoft uses ClickOnce to deploy their HR and other apps internally to all 80,000 employees. We have thousands of customers, but our application is very small.

I don't see where application size isa problem except maybe in download time. IT also depends on the structure, too. If you strongly name your dll's, ClickOnce will do incremental updates, which means it does not copy down dll's that haven't changed since the last deployment, it uses the last one it got. (This is great!)

You can not install it anywhere except the user's profile. You can not install for all users. So if you want multiple users to use the machine, each one would use 500MB of disk space.

On the other hand, aside from the prerequisites you might have, it doesn't require any admin privileges, which is nice.

I think it depends somewhat on what prerequisites you are going to have, can you deploy the dll's locally or do you have to put them in the GAC, and stuff like that. Why is the deployment so large, is it content that you are including, or the dll's and assemblies?

You can always try it and see if it works.

RobinDotNet

I have heard that Microsoft uses ClickOnce to deploy their HR and other apps internally to all 80,000 employees. We have thousands of customers, but our application is very small.

I don't see where application size isa problem except maybe in download time. IT also depends on the structure, too. If you strongly name your dll's, ClickOnce will do incremental updates, which means it does not copy down dll's that haven't changed since the last deployment, it uses the last one it got. (This is great!)

You can not install it anywhere except the user's profile. You can not install for all users. So if you want multiple users to use the machine, each one would use 500MB of disk space.

On the other hand, aside from the prerequisites you might have, it doesn't require any admin privileges, which is nice.

I think it depends somewhat on what prerequisites you are going to have, can you deploy the dll's locally or do you have to put them in the GAC, and stuff like that. Why is the deployment so large, is it content that you are including, or the dll's and assemblies?

You can always try it and see if it works.

RobinDotNet