J
Jürgen
Hello,
We have implemented a few years ago a "zero touch" deployed smart client
application for .NET 1.1.
We ported now this application to .NET 2.0 and deploying it with ClickOnce.
Because we have still .NET 1.1 clients around, we made a small ASP.NET
startup application that checks host header values and redirects
(Response.Redirect(...)) to the .application file in case the client has
..NET 2.0 installed. Otherwise it will launch the old smart client on a web
page.
This all works fine as long as we start the ASP.NET startup page (let's call
it StartClient.aspx) from within Internet Explorer. If we put a link to the
startup page into an e-mail or just on the desktop launching the ClickOnce
client with this link fails with a "Cannot Start Application" message box.
The details say:
SOURCES
Deployment url :
https://myserver/Client/StartClient.aspx
ERROR SUMMARY
Below is a summary of the errors, details of these errors are
listed later in the log.
* Activation of https://myserver/Client/StartClient.aspx
resulted in exception. Following failure messages were detected:
+ Downloading
https://myserver/Client/StartClient.aspx did not succeed.
+ The remote server returned an error: (403)
Forbidden.
The deployment url is the startup page and not the .application manifest
file as we would expect. When checking IIS logs, we can find first a request
to StartClient.aspx, second a request to
https://myserver/ClickOnceClient/MyApp.application (the manifest), and a
third request back to StartClient.aspx.
This third request doesn't happen when we access the aspx page from within
Internet Explorer (where, as mentioned before, everything works as
expected).
It seems like it only partially redirects when launching from a hyperlink in
a document.
Thanks for your help in advance,
Jürgen
We have implemented a few years ago a "zero touch" deployed smart client
application for .NET 1.1.
We ported now this application to .NET 2.0 and deploying it with ClickOnce.
Because we have still .NET 1.1 clients around, we made a small ASP.NET
startup application that checks host header values and redirects
(Response.Redirect(...)) to the .application file in case the client has
..NET 2.0 installed. Otherwise it will launch the old smart client on a web
page.
This all works fine as long as we start the ASP.NET startup page (let's call
it StartClient.aspx) from within Internet Explorer. If we put a link to the
startup page into an e-mail or just on the desktop launching the ClickOnce
client with this link fails with a "Cannot Start Application" message box.
The details say:
SOURCES
Deployment url :
https://myserver/Client/StartClient.aspx
ERROR SUMMARY
Below is a summary of the errors, details of these errors are
listed later in the log.
* Activation of https://myserver/Client/StartClient.aspx
resulted in exception. Following failure messages were detected:
+ Downloading
https://myserver/Client/StartClient.aspx did not succeed.
+ The remote server returned an error: (403)
Forbidden.
The deployment url is the startup page and not the .application manifest
file as we would expect. When checking IIS logs, we can find first a request
to StartClient.aspx, second a request to
https://myserver/ClickOnceClient/MyApp.application (the manifest), and a
third request back to StartClient.aspx.
This third request doesn't happen when we access the aspx page from within
Internet Explorer (where, as mentioned before, everything works as
expected).
It seems like it only partially redirects when launching from a hyperlink in
a document.
Thanks for your help in advance,
Jürgen