What is mojoPortal.Web.Framework project for?

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This thread is closed to new posts. You must sign in to post in the forums.

4/12/2007 9:15:10 AM

Alexander V. Yushchenko

Total Posts 488

View Posts

What is mojoPortal.Web.Framework project for?

Joe, please, explain.

I understand what are the separate Web, Business and Data projects created for.
I understand why you have created mojoPortal.Web.Controls.

But I just cannot understand what is the purpose of mojoPortal.Web.Framework project in the solution? Why are not these files included into mojoPortal.Web project?

The only reason I can see is to enable feature module developers to use this small project as a reference instead of the whole mojoPortal.Web.
But in this case some classes (at least SiteModuleControl and mojoBasePage) should be moved to this project.

4/12/2007 11:14:52 AM

Joe Audette

Total Posts 18439

View Posts

Re: What is mojoPortal.Web.Framework project for?

Well, it contains things that might be useful in projects that have no dependencies on mojoPortal.Web.dll, it is a small set of classes now but it may grow over time. Framework may not have been the best name for it since in another context I consider it only part of the framework, but it is a library of functionality that could be used in any web project not just mojoportal so it is separate for the same reasons that mojoPortal.Web.Controls is separate so it can be used without the rest of mojoportal and in projects not built using mojoPortal.

It is not meant to be mojo lite for module developers, modules are intended for integration with the mojoportal web project aka mojoPortal.Web.dll

SiteModuleControl and mojoBasePage are specifically to support module development for things that will run on top of mojoPortal.Web.dll so they belong in the main web project.

Joe

You must sign in to post in the forums. This thread is closed to new posts.