J
Joe
Hello,
I am trying to access the ApplicationURI property, but it seems that no
matter what I do, it is null. I have enabled the "Allow URL parameters to
be passed to application", but with no effect.
My test program is really simple:
if (ApplicationDeployment.IsNetworkDeployed) {
if (ApplicationDeployment.CurrentDeployment.ActivationUri == null) {
MessageBox.Show("activationuri is null");
}
} else {
MessageBox.Show("Application is not being run over http://");
}
I am placing the application onto an IIS 6.0 website, and "running" it via
http://server/clickonce.application?username=joe .
The application runs fine, but ActivationUri is always null. If I run it
locally from my own disk or via the debugger, I get the expected result of
"application is not being run over http://".
I have checked the clickonce.application file, and find a line that says
(please note the trustURLParameters attribute):
<deployment install="false" mapFileExtensions="true"
trustURLParameters="true" />
Is the trustURLParameters the only flag the runtime checks to enable this
feature?
Thanks for any information, I am about to resort to writing to file, and
then reading from it on the local system as a workaround
Joe
I am trying to access the ApplicationURI property, but it seems that no
matter what I do, it is null. I have enabled the "Allow URL parameters to
be passed to application", but with no effect.
My test program is really simple:
if (ApplicationDeployment.IsNetworkDeployed) {
if (ApplicationDeployment.CurrentDeployment.ActivationUri == null) {
MessageBox.Show("activationuri is null");
}
} else {
MessageBox.Show("Application is not being run over http://");
}
I am placing the application onto an IIS 6.0 website, and "running" it via
http://server/clickonce.application?username=joe .
The application runs fine, but ActivationUri is always null. If I run it
locally from my own disk or via the debugger, I get the expected result of
"application is not being run over http://".
I have checked the clickonce.application file, and find a line that says
(please note the trustURLParameters attribute):
<deployment install="false" mapFileExtensions="true"
trustURLParameters="true" />
Is the trustURLParameters the only flag the runtime checks to enable this
feature?
Thanks for any information, I am about to resort to writing to file, and
then reading from it on the local system as a workaround
Joe