Click once parameters not coming through

  • Thread starter Thread starter CSharpner
  • Start date Start date
C

CSharpner

I posted this a while ago with no response other than a confirmation
from someone else. Has anyone gotten this to work?

Problem:
I've created a click-once deployed application that cannot receive
paramters from the query string in the URL of the click once page.

I've followed this to the letter:
http://msdn2.microsoft.com/en-us/library/ms172242(VS.80).aspx


My query string is always blank. Here's my actual URL:


http://MyMachine/MyApplication/publish.htm?test=something


The application starts up just fine, it's just that
ApplicationDeployment.CurrentDeployment.ActivationUri.Query is always
blank.


Has anyone ever gotten this to work?
 
I appreciate the response, but I don't think you quite understand the
problem: How do you do that from a web application? This is how the
Microsoft examples do it.

The scenario is:

Users of a web site will click on a link. The link will send them to
my click once page with the parameters on the URL in the query
string. When the application starts up on their local machine, it
knows what objects to load based on the data in the query string. I
don't believe it's possible to "send them [parms] to the application"
other than through the query string. I'm certainly open to anything
new though as Microsoft's examples don't work. I can of course, make
some kind of a hack, like writing the parms to a table, then have a
web service which the app calls upon start up to look up the parms,
but passing the user ID is still a problem, unless I force the user to
log in (which wouldn't be necessary with the parms passed via the
query string).

What I'm primarily looking for is an explanation of why this query
string parm is not working... unless there's a more elegant solution
(ie, not a hack).
 
OH Man! I see what you (DotNetDan) were saying now! Never mind my
blithering misunderstanding below. I didn't realize you had retyped
the URL. I thought you had just copied my original URL and when you
said "send them to the application" I thought you meant "send them to
the exe".

Now that I finally figured it out on my own, I see you had the answer
posted here all along!

Sorry man! You clearly DID understand the problem!


I appreciate the response, but I don't think you quite understand the
problem: How do you do that from a web application? This is how the
Microsoft examples do it.

The scenario is:

Users of a web site will click on a link. The link will send them to
my click once page with the parameters on the URL in the query
string. When the application starts up on their local machine, it
knows what objects to load based on the data in the query string. I
don't believe it's possible to "send them [parms] to the application"
other than through the query string. I'm certainly open to anything
new though as Microsoft's examples don't work. I can of course, make
some kind of a hack, like writing the parms to a table, then have a
web service which the app calls upon start up to look up the parms,
but passing the user ID is still a problem, unless I force the user to
log in (which wouldn't be necessary with the parms passed via the
query string).

What I'm primarily looking for is an explanation of why this query
string parm is not working... unless there's a more elegant solution
(ie, not a hack).

Hi CSharper,
Click to expand...
It looks to me like your url is incorrect. Don't send the parms to
publish.htm, send them to the application:

Have a good one,
Click to expand...
- Show quoted text -- Hide quoted text -
Click to expand...

- Show quoted text -
Click to expand...
 
Back
Top