I'm not sure but with Server.Transfer the Form collection of the calling page is available within the page you transfer to using Request.Form. I would imagine this is the same for Server.Execute.
Rob
Go placidly amidst the noise and haste, and remember what peace there may be in silence - Erhmann 1927
Whats wrong with the querystring? Do you want to pass an object to the page rather than a value?
You could store them in the Session or the Cache and pull them back in the executed page I guess.
AFAIK there is no Server.Execute specific mechanism for passing parameters. Just the same as are available to the page if called directly by the browser ie. Request.QueryString and Request.Form.
Rob
Go placidly amidst the noise and haste, and remember what peace there may be in silence - Erhmann 1927
Ok - that is probably one of the few valid uses of Server.Execute. I have seen people use it to encapsulate functionality (as we did in classic ASP) before which is kind of missing the point a bit I feel. As you don't need the parameters after the email has been sent the Context collection seems a good place to put them.
Rob
Go placidly amidst the noise and haste, and remember what peace there may be in silence - Erhmann 1927
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.