I just read Configuring ClickOnce Trusted Publishers and got it on another computer on the network. I deployed the application to the network itself (i.e. \\\abc\something).
Although I could not find certmgr.exe as part of the main component of Windows, as the article says (..also you will need to use the certificate management console (certmgr.exe) included in Windows ..), instead I found it is in the folder "C: \ Program Files \ Microsoft SDK \ Windows \ v6.0A \ bin". It worked great, but did I miss something? I mean, what if the user did not install Visual Studio?
Now I had to explicitly go and do it (i.e. import the certificate using certmgr.exe) on the user / client computer on the network. Is there any way to automate it? If I do not do anything explicitly and when the user clicks setup.exein the deployed application on the network ( \\\abc\something), he can install the same without receiving security-based prompts.
I checked BOOTSTRAP, but I couldn’t figure out exactly how to use it, HERE? I was thinking about inserting the certificate in the appropriate place (I thought that importing the certificate with the help certmgr.exeinserts it somewhere on the disk? In some kind of "personal" directory)?
In gist, I want to automate the process where the user can install the application from the network ( \\\abc\something) without any security / trust hints. And I, as a developer, do not explicitly import the certificate to my / user / client computer.
source
share