![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | ClickOnce 404 - no deployment files at the Update location Hi All, I've been successfully deploying clickOnce successfully through the 2.0 and 3.X frameworks, but now have a problem with ClickOnce updates in 3.5 SP1. The scenario is this: I want to deploy an *offline* application that can only be installed from behind our organizational firewall (a Win2k3 domain), but can be updated from anywhere (hotels, etc). To do this, the publishing folder location is set to a UNC share path: \\MyServer\OurDeployments\ThisDeployment. And the update location is set to: http://my.fullyqualified.srvr/Deploy...ThisDeployment So, what we see is that the deployment files all get happily copied to the UNC share, but nothing gets copied to the update web site. This seems reasonable. (btw, the update web site was correctly created, using the vs wizard) When we go to the UNC share and run setup.exe to do the first installation, it fails: "Cannot start application". The details accessible from the error message form indicate that the Deployment URL is pointing to the UNC share and the deployment provider url is pointing to the the update web. It seems that the .application file on the UNC share is immediately trying to get a version of itself from the update web!? Pls see below: ---snip------------------------ ERROR SUMMARY Below is a summary of the errors, details of these errors are listed later in the log. * Activation of \\MyServer\OurDeployments\ThisDeployment\myapp.application resulted in exception. Following failure messages were detected: + Downloading http://my.fullyqualified.srvr/Deploy...pp.application did not succeed. + The remote server returned an error: (404) Not Found. ---snip----------------------- Interestingly, If I publish an update, nothing is written to the update web, it only gets written to the UNC share. So, is this *by design*? If so, then how do I configure ClickOnce to work correctly for my scenario. If not, any ideas? Kind regards, T!M |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| ClickOnce Deployment | .NET General | |||
| try to update a Microsoft Visual Studio 2005 ClickOnce application after the certificate that you used to sign the installation expires, error message recieved | .NET General | |||
| Re: DLL.config files and MSI Deployment Projects | .NET General | |||
| ClickOnce Deployment (BUG?) | .NET General | |||