title: How to force ClickOnce deployment url?
body: <p>I'm having a bit of a hair-puller here.</p>
  
  <p>I'm publishing a VS 2008 application to a server, to be installed via ClickOnce. So far, so good. It installs just fine. Then I added in a ClickOnce update checker - one that uses ApplicationDeployment to handle checking for &amp; applying updates.</p>
  
  <p>So far, so good.</p>
  
  <p>Then, on some of the machines it was installed on, the updater wouldn't work. The error it returned was that the application had already been installed from another URI - which it wasn't.</p>
  
  <p>After enough digging around, I found that:</p>
  
  <p>URL 1: htfp://www.domain.com/app/myapp.application</p>
  
  <p>URL 2: htfp://www.domain.dom/App/myapp.application</p>
  
  <p>ClickOnce considers URLs 1 and 2 to be entirely different - even though "app" contains a capital A in URL 2, and both point to the same, valid .application file.</p>
  
  <p>When I found that out I edited all our intranet links to point to an all-lowercase version of the URL, which is working for now, but there's always the chance that someone might install it from an "incorrect" URL - the only solution being to forcibly uninstall and reinstall the application from the correct URL.</p>
  
  <p>How do I force the deployment URL ClickOnce checks against for updates? It seems to generate its manifest based on the URL it was installed from, so I'm not sure I can fix it from VS' end.</p>
  
  <p>Thanks,</p>
  
  <p>~ Wogan</p>