Subscribe to my RSS feed
|
|
DotNetNuke Module Development
I wish someone could explain to me why the DotNetNuke module framework
only allows ONE "View" control for each module. I''m working on a
module right now that needs 3 different view controls, but anytime I
try to load one of the non-default (according to the module definition)
view controls DNN forces the admin skin on it and I lose the other
panes. Why can''t I just load a specific view control for my
module and have it keep the other panes! aaahh! The only
solution I''ve found that other people have used is to implement a
dynamic control injection scheme using the query string and a big
switch statement inside their one default view control which
dynamically loads other view controls as needed in-place.
Unfortunately, when you do that you lose a lot of features like module
actions per view control and design time event assignments to your
buttons, datagrids, etc. on each page. Say it isn''t so!
Someone please tell me there''s a better way......
| Comments | Currently, there are no comments. Be the first to post one!
Click here to post a comment |
|