hi
i have a solution i have wrote with visual studio 2008 baset on net2.0 using clickedonce, i have published it to my iis server and all is ok
when i packed it and installed it on the client iis server , when downloading it looks for my server.
i have updated (with mageui) the .application file in the primary folder and under the version folder to use the client url
but still it looks for my server

where am i wrong?

Are you talking about changing the URL for the location of your ClickOnce deployment?

If you install it by calling the link to the application file itself, does it work? Is the problem the setup.exe file not looking in the right place?

If so, here's some excellent information:

Open a command window and change directories to your setup.exe file.
If you type in "setup.exe -?" it will show you the options.

To change the URL where it looks for the ClickOnce deployment, use -url.

setup.exe -url <new path to deployment manifest>

example:
setup.exe -url http://www.mycompany.com/myappname/

RobinDotNet

---

Click here to visit my ClickOnce blog!

Did you happen to try what I recommended? Because if you do, you should find that it works.

The setup.exe is not part of the digital signature; it is completely different from the ClickOnce installation, which IS digitally signed.

The setup.exe file runs the prerequisites, and then fires off the ClickOnce installation using the URL that is defined in the setup.exe. That's why if you change the URL for the ClickOnce installation (i.e. the application file), you have to change the URL that the setup.exe points to, using the instructions I provided before.

RobinDotNet

---

Click here to visit my ClickOnce blog!

Are you talking about changing the URL for the location of your ClickOnce deployment?

If you install it by calling the link to the application file itself, does it work? Is the problem the setup.exe file not looking in the right place?

If so, here's some excellent information:

Open a command window and change directories to your setup.exe file.
If you type in "setup.exe -?" it will show you the options.

To change the URL where it looks for the ClickOnce deployment, use -url.

setup.exe -url <new path to deployment manifest>

example:
setup.exe -url http://www.mycompany.com/myappname/

RobinDotNet

---

Click here to visit my ClickOnce blog!

hi

several problems , if i will change the setup.exe after the publish it will damage the digital signature.

in my deployment the solution will install pre-req' . i changed the url of the setup.exe and now it is installing the pre-req', but when it is going to download the *.application it is still looking for the original place and not for the client server ( although in the manifest the url is the client server)

Did you happen to try what I recommended? Because if you do, you should find that it works.

The setup.exe is not part of the digital signature; it is completely different from the ClickOnce installation, which IS digitally signed.

The setup.exe file runs the prerequisites, and then fires off the ClickOnce installation using the URL that is defined in the setup.exe. That's why if you change the URL for the ClickOnce installation (i.e. the application file), you have to change the URL that the setup.exe points to, using the instructions I provided before.

RobinDotNet

---

Click here to visit my ClickOnce blog!