I have created a .net user control with some functionality. Then i have a XSLT extension which has some functionality. Then i have created both the macros.
I have implemented the both on a same page. Here i have an issue the XSLT macro is called first than User control macro. Can we make it other way round as i have to call my User control macro first.
Actually i have to perform some checking in the request object and need to place an information in the Cookie. Then xslt should call the cookie information. So her in my case the XSLT is called first and it will check for the cookie information and it cant find.
This isn't to do with the order of execution. A cookie won't be avaialble in the HTTP context in which it is set as it will need to be written to the browser which then makes it available to subsequent requests.
Once the user control sets the cookie have it perform a client side redirect back to its containing page.
Personally I would handle all of this logic in an HTTP module as you have more entry points into various stages of the request.
XSLT macro and User control macro
Hi all
I have created a .net user control with some functionality. Then i have a XSLT extension which has some functionality. Then i have created both the macros.
I have implemented the both on a same page. Here i have an issue the XSLT macro is called first than User control macro. Can we make it other way round as i have to call my User control macro first.
Any help please....
Best Regards
Sujith PV
Can you explain why the order is significant.
They shouldn't be dependent on one another and your issue is most likely a design flaw.
Hi Darren Ferguson
Actually i have to perform some checking in the request object and need to place an information in the Cookie. Then xslt should call the cookie information. So her in my case the XSLT is called first and it will check for the cookie information and it cant find.
Best Regards
Sujith PV
This isn't to do with the order of execution. A cookie won't be avaialble in the HTTP context in which it is set as it will need to be written to the browser which then makes it available to subsequent requests.
Once the user control sets the cookie have it perform a client side redirect back to its containing page.
Personally I would handle all of this logic in an HTTP module as you have more entry points into various stages of the request.
Thanks Darren Ferguson for your reply. i think it makes sense.
Best Regards
Sujith PV
is working on a reply...