Hi all
There seems to be lots of questions and answers on this topic. I hope this doesn't come across too much like I'm complaining about a great free product but I just want to make sure I'm not missing anything and also make a suggestion.
I'm developing a reasonably complex module which requires multiple views at different times in the portal skin. I'm using dynamic loading, i.e., LoadControl etc from a base view which does nothing but load the real view I want to show. That's working well so I'm proceeding down that path but ... it seems complicated for something that should be simple.
Pasting from one of Michael Washington's pages, I know I can do this:
http://localhost/MyDNNWebsite/Home/tabid/36/ctl/mygallery/mid/362/Default.aspx
But that shows the module in the admin skin and other modules disappear which I don't want.
Multiple module definitions is another suggested solution but that doesn't really do it either because it shows all the views at once.
If my understanding is correct then the only view that can ever be shown in the portal skin is one with a blank key. Is that correct?
I surprises me that the core framework doesn't have a simple way of solving this. It seems like a useful and obvious enhancement would be to make it intepret a url similar to the one above to mean "do everything the same as if ctl and mid are not present except show the view with that key rather than the one with the blank key". I know its easy for me to say as an armchair observer but it seems like it would be a simple enhancement and would solve a problem that seems to have frustrated module developers for a long time.
Cheers
Ross