>I'm interested in the addition of a couple of web controls to the framework:
>
>datalist
>user control
What are you missing in mmDataList?
UserControl would be a tough one since it is too generic. The main things the UI controls implement is databinding and security interfaces and they're specific to the control and map to specific properties of these controls. With a generic user control this would be difficult to do and there's little to be gained. Basically you can create a new control subclassed from that control and then implement the interfaces you're interested in for databinding or security.
>Another goal I have it to integrate the MM framework into the IBuySpy portal. While the MM web framework goes a long way to assisting in the process of creating web forms, it has no real UI framework for navigation, menus, users, roles, etc. At least I haven't seen it. The I Buy Spy portal has all that and a fairly straight-forward mechanism for managing content.
You shouldn't have any problem integrating this stuff into any other framework. IBuySpy is essentially a UI front end and so it should play just fine with what MM provides. You can use IBuySpy as is and then for the page content use standard Web Form stuff with mm Controls to provide your logic.
>Ideally, I could create an ASCX component that could inherit the attributes of the portals "module" class (in order to play well with its framework) but implement the attributes of the MM Business class (to play well with the MM business classes). This way it would be possible to add MM modules into the IBuySpy portal framework.
I'm not sure I understand why you would think there would be any issues with integration. The main things I can think of would be to have the portal BOs use MM classes behind the scenes which would mean you pull out whats there and replace it. I'm not sure if that's necessary or whether that really buys you anything.
FWIW, in ASP.Net 2.0 a lot of the stuff that you build for a typical portal will all be built-in to to the framework. Registration, controlled content, master pages - all of these things will drastically change the amount of code needed to do this sort of thing - and it is all pluggable with custom providers so you could for example, just plug in BO's from an MM app. But unfortunately that's still almost a year off...