title: Deploy WPF ClickOnce .application File as .EXE
body: <p>I've developed a WPF application. A large company is trying to make my application available to users' desktops. The traditional way to do this would be to point the users' browsers to:</p>
  
  <p><a href="http://www.MySite.com/MyApp.application" rel="nofollow">http://www.MySite.com/MyApp.application</a></p>
  
  <p>But the I.T. group at this company has configured their proxy server in such a way so as to block .application files for security reasons. They do, however, allow .exe files to pass through their proxy server and execute on client workstations. The irony of allowing .exe's from the Internet while blocking .application text files "for security reasons" isn't wasted on me but let's put that aside for a moment.</p>
  
  <p>What kind of workaround would you recommend that would allow my app to launch from client desktops given that .EXEs <em>are</em> allowed? My first thought is to write a mini launcher app that does nothing more than download a .zip'd version of the .application file and all dependencies to a temp folder on the user's machine and then launch the .application file from there. Is there a better solution?</p>
  
  <p>FWIW: Google has figured out a way to deploy their Chrome browser to Windows desktops in corporations like this one, despite the fact that ClickOnce is their deployment mechanism. If you view the source code at: </p>
  
  <p><a href="http://www.google.com/chrome/thankyou.html?&amp;oneclickinstalled=" rel="nofollow">http://www.google.com/chrome/thankyou.html?&amp;oneclickinstalled=</a></p>
  
  <p>...you'll see they're pointing to an installer at: </p>
  
  <p>/update2/installers/clickonce/GoogleInstaller_en.application. </p>
  
  <p>That's a clickonce file. But somehow they've figured out a way to wrap it in an .exe in order to bypass proxy restrictions on .application files. I not familiar enough with JScript to understand what they're doing but it works. I'm trying to emulate this behavior for my own app.</p>