I am working for a software house. We are developing an application which generates dll on the fly using reflection base on user changes and the dll is published on the server. When other winform clients detect the changes, this dll is downloaded to the client machine and loaded dynamically to show some winforms.

1. Is ClickOnce suitable for this kind of task?

2. Obviously we won't ship our source code with the product and this code will run in our client side. How can we build an app that can modify the manifest programmatically so that the Installed Client can detect the dll changes and update using ClickOnce? At this point, the application version is not changed but the dll to display the winform is changed.

3. We cannot use OnDemand, as the dll can be changed by any of the winclient at anytime and we need to load the dll again if there is any changes.

4. Is there anyway to override the CheckForUpdate

Thanks

Taddy.

I had the same issue and had to buy a Certificate. You can if you own Win2003 become your own Certification Authority but you would have to be able to get your users to download your certificate authority root certificate to their machines before installing your clickonce application, so we went with Thawte. Was really easy process to get a code signing certificate. Takes a few days but no code was needed, they only verified the company info and our website was valid.

We sell our software to difference client, and the application can be changed at runtime in the deployment server. So we need to have some code and the certificate to resign the application manifest on runtime whenever any win32 client change some settings and trigger a rebuild of the application in deployment server. The app will then be downloaded by the all win32 client by clickOnce.

I am thinking of storing our certificate in our application as a resource and then resign the manifest programmatically.

Another of my question is can we package our certificate in MSI and execute certmgr.exe -add certificate.cer -c -s -r localMachine TrustedPublisher
and use the ClickOnce bootstrapper to include this msi? Will the Client machine still receive a warning pop up while running the msi?