Hi,

I really can't help you much with general ASP.NET questions, there is a wealth of information available on the internet and in books that can help you understand how to achieve the results you are seeking and how to organize your work.

I will only point out that in mojoPortal, what I call a a module is the entry point to a feature, its the part the plugs into the page. It is a .ascx file, but it is special because it inherits from SiteModuleControl instead of directly from UserControl.

Normal .ascx files inherit from UserControl and can be used anywhere and even nested within other UserControls where mojoPortal SiteModuleControls should not be nested inside other SiteModule controls, but can have normal UserControls nested within them. UserControls are an easy way to encapsulate functionality that you want to re-use on more than one page.

Hope it helps,

Joe

No its not a good idea. A feature should have one and only one module control (which is the entry point to the feature), you can use user controls inside the module control but you cannot use other modulecontrols inside it nor should there be any cross talk between module controls. A module control should be self contained and it should not care what other modules are on the page with it, it should not have any knowledge of other modules or dependencies on other modules.

It can link to an external page for results (ie a physical page not a content system page as they are virtual). You can see several features that use external pages including the blog and the forums. You need to pass pageid and moduleid at a minimum to your external page(s) in the query string to keep the context of the current content system page.

Hope it helps,

Joe

You have the source code for mojoportal right? That is the example. Study the code for existing features to learn how to implement your own features, the examples for almost anything you want to do is right in front of you in the mojoportal source code.

Best,

Joe