I personally would go with 3 ASCX files

1 that Loads the other 2 controls, have it do the checking of the Cookie, and then redirect the User to a different URL using a querystring parameter such as ViewControl=Email or ViewControl=Success

Using the NavigateURL method and passing in the TabId, along with the appropriate querystring parameter, will build out a unique URL and allow Google Analytics and other controls to still load on the page.

For an example, see my DNNSimpleArticle module

http://dnnsimplearticle.codeplex.com/

It has a Listing control that displays by default, or an ArticleDisplay control that loads if you click on a link in the listing and build a URL with an article id parameter.

---

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions

Chris, I opened the solution you recommended from codeplex - the DNNSimpleArticle, however I don't see the source code, only the markup and the binary.
I have started the work according to the design you suggested and would like to ask a few questions.

I have 3 ascx controls in my DealRequest module.
1. Controller. This control recieves a call from another control (outside DealRequest module) when the user clicks on a "Request a Deal" button.
2. RequestEmail. is redirected to by the Controller if ["Email"] cookie is not found on the client
3. DealSuccess. is redirected to by the Controller if ["Email"] cookie is not null

I have the three controls developed. Now I have to make them work in DNN - do some wiring. So I logged in to DNN. Could you provide me with a little direction from here?

1. Where do I place the Controller? How does the calling control on the DNN website knows how to call the Controller. Do I create a new page and put the Controller on a page with particular tabid and then have the calling control call navigateURL method from it's code with that page's URL?

2. Could you also elaborate on the proper URL building method that suits this solution? I am not familiar with DNN URL providers. Apparently, there are many ways of doing it. In our production I see strings like this

http://www.dealfinder.com/src/dealrequest?BusinessID=144&BusinessName=Canadian Tire

I have seen other looks online like

http://www.dnndaily.com/tabid/353/default.aspx
or
http://www.dnndaily.com/default.aspx?tabid=353

3. When the Controller makes the call to the appropreate control, why does it need to use a query string parameter? I understood that the page the redirect is going to has been determined by the logic of the Controller, so it knows exactly what page it is calling - no parameters required. Ex, call http://dealfinder.com/RequestEmail if the cookie is null or call
http://dealfinder.com/DealSuccess page if the cookie in not null.

Thank you.
s.