Password Protected ClickOnce Deployment

  • Thread starter Thread starter Sachin Palewar
  • Start date Start date
S

Sachin Palewar

I just created a clickonce deployment and uploaded it on a website. It
works great but I am worried because anybody can download it from the
URL if they know about it. At this point my application may not be
useful in its current form to everybody but going into the future I
would like to protect it so that only authorised users can install and
run the application. Any pointers in that direction will be
appreciated.

Another related query I have is that I would first like to deploy to a
test server and then to a production server. If I just change the
publish URL, will it deploy to different servers. Can I keep changing
URLs like this? Won't incremental versions post certain problems.

Thanks in advance...

Regards,
Sachin Palewar

Palewar Techno Solutions
(Mobile Solutions for Your Business)
www.palewar.com

Blog - http://palewar.blogspot.com/
LinkedIn -http://www.linkedin.com/in/palewar
 
I don't think you can password-protect a ClickOnce deployment; you will
have to password-protect the web page where they get to it.

Just uncheck the box that says "increment the version number
automatically".

Also, you can publish it once (like to a location on disk) and use MageUI
to modify the manifest and then ftp it to multiple locations. You would do
this if you wanted to ensure that the exact same build was pushed to
multiple places. Frankly, it's easier just to publish it twice to different
URLs and not change the version number, assuming your code base can't be
modified by anyone else while you're doing it.

Robin S.
 
Thanks for your response. Just one more question, I understand that we
can password protect the webpage for installation, but we need to also
provide a URL from where application will be automatically updated. If
we password protect that directory on server, then I assume software
won't be able to update or check for update.

My concern is that if somebody comes to know of the direct URL for my
installation, he can directly install from that location. Do you have
any suggestion to prevent this?

Thanks again for your help.

Regards,

Sachin
 
That's a good point. I recommend trying it; it might pop up and ask for the
user credentials before checking for updates. This would be my bet.

Robin S.
-----------------------------------
 
Back
Top