That is better if blog module and forum modules be separated projects.

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

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.

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.
1/18/2008 3:10:11 AM
Gravatar
Total Posts 550

That is better if blog module and forum modules be separated projects.

Hi Joe
In my opinion that is better if blog module and forum modules be separated projects like poll or survey modules.

Thanks.
 

1/18/2008 7:40:41 AM
Gravatar
Total Posts 18439

Re: That is better if blog module and forum modules be separated projects.

Hi A.Samarian,

I disagree. The main reason a few features are separate is to show other developers how they can implement features without mingling their code in the core. In the case of the Poll and Survey, it also makes it easier to handle the fact that all the data layers have not yet been implemented for those features. However I can see no good reason to make every core feature into separate projects. It will make the solution have too many projects and will make it more complicated to manage the builds for all the different data layers. You see for every feature that we make separate we end up with 7 projects, 1 UI, 1 Business, and 5 Data layer projects. So to separate the blog and forum we would have to add 14 projects to the solution.

Right now when I want to do a build for MySQL, I just need to change the data layer reference on mojoPortal.Business, but if all the projects get separate I need to do it on every Business layer project. Already I am faced with this when the other data layers get implemented for the current separate projects.

Best Regards,

Joe

1/18/2008 10:42:06 AM
Gravatar
Total Posts 550

Re: That is better if blog module and forum modules be separated projects.

Hi Joe

Ok.In my opinion separated projects make mojoportal will be very modular and this is cause mojoportal will be very extendable. We must try to find share things in all projects as mojoportal core.

Best  regards.


 

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