Hello:

I recently started doing module development with DNN 4.3.5 and the Dev Kit. The setup is working fine for me with VS 2005. I have a sample module working based on the Dev Kit sample template. I also have another (separate) module working based on the excellent tutorial by Michael Washington at http://www.adefwebserver.com/DotNetNukeHELP/DNN_ShowMeThePages/Default.htm. So far, so good.

Now, I need to use multiple view user controls on a module I need to build. So, I thought that I use the view control from the Dev Kit as the main view control and then load the SuperSimple user control from Michael’s sample as a secondary control (for lack of a better name) and load it dynamically with NavigateURL. I recreated the SuperSimple module in the same directory as the Dev Kit sample taking care of renaming the directory name where appropriate (as far as I could tell). I also registered this new module (manually) with the new name and a unique Key name.

I have done extensive searches of the Forum and have tried different ways to use the NavigateURL to invoke the secondary view control and none seem to work for me. The thing is that on the test page I have two other modules and when I introduce the NavigateURL none of the modules show up. The best part is that no errors are displayed either, on the page or the logs. If I rem out the NavigateURL line then the modules appear just fine.

Borderline crazy and not trusting my own test assumptions (something I learned long ago) I decided to test the new copy of the SuperSimple module I created and I put it on a page to run by itself and guess what? It does not work, great. But again, I don’t get any errors on the page or the log. That module is pretty simple indeed, so I thought that just renaming the module name and the directory would be enough to move it. I don’t know what is going on.

Therefore my questions:

1. When using multiple View user controls, how are the “Sub” user controls supposed to be defined? Just like a regular View control???

2. How about the registration, is it the same? I understand that the “Sub” modules should also be registered as View control with a unique Key name. Is this correct?

3. Is there an even simpler sample of a minimal user control I could use for testing? Or what need to be adjusted in Michael’s sample to be able to use it as a “Sub” or “Secondary” view control.

4. Please provide any other detail I may be missing.

I’m going off-line for a while now, my brain hurts… Your help will be appreciated.

This is the normal behavior. If you look closer, you would have also noticed that it is showing the admin skin instead of the portal skin.

You can try this alternative method to avoid these issues.  In addition, you also avoid the need to register any extra view controls.

mcsenow:

Thank you for your feedback. I did look at the previous version of your architecture and benefited from it. I got it to work in 4.3.5 with modifications of course. I've been meaning to post my findings but been too busy building the module I'm supposed to be doing at this moment.

I liked your architecture because it did not require registration of all the controls to be used, I noticed that you changed this in the new version, could you elaborate on the change of heart? And to follow up on this, isn't the Summary on your page contradicting the Change Log for the download package? What is the benefit of using NavigateURL???

Thank you for your contribution.

Carlos