Which projects are more important to keep in Solution

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.
7/21/2009 3:29:04 AM
Gravatar
Total Posts 17

Which projects are more important to keep in Solution

Dear Admin,

There are many projects in mojo portal solution file. Initially we removed some projects related to Data Access  other than MSSQL (liek MYSQL etc.). There are still 20 projects, and we want to remove from our solution so that solution can be loaded quickly and compiled. Can you please advise which projects will be more usable or required to run mojo portal with all features. We are not going to change the core functionality of mojo portal, but only change the theme/layout and some interfaces of mojo portal if required. Currently our solution has following projects:-

  1. Web
  2. mojoPortal.Business
  3. mojoPortal.Business.WebHelpers
  4. mojoPortal.Data.MSSQL
  5. mojoPortal.Features.Business
  6. mojoPortal.Features.Data.MSSQL
  7. mojoPortal.Features.UI
  8. mojoPortal.Net
  9. mojoPortal.UnitTests
  10. mojoPortal.Web.Controls
  11. mojoPortal.Web.Editor
  12. mojoPortal.Web.Framework
  13. mojoPortal.Web.Rest
  14. SiteOffice.Business
  15. SiteOffice.Data.MSSQL
  16. SiteOffice.ExternalMail
  17. SiteOffice.UI
  18. WebStore.Business
  19. WebStore.Data.MSSQL
  20. WebStore.UI

Regards,
Imran
 

 

7/21/2009 5:23:44 AM
Gravatar
Total Posts 18439

Re: Which projects are more important to keep in Solution

You could remove all the SiteOffice projects since it is just in the protype stage. You could remove the UnitTest project, you could remove the mojoPortal.Web.Rest project. Everything else is needed for all the features.

I would not change any of the code in any of the projects or you will have trouble upgrading. ALL of your work other than custom skins, should be in your own set of projects which you would add to the solution for custom development. You use post build events to copy needed files up to Web for runtime/debuging, you can see examples of post build events in mojoPortal.Features.UI and in WebStore.UI.

Best,

Joe 

7/21/2009 9:21:49 AM
Gravatar
Total Posts 17

Re: Which projects are more important to keep in Solution

Dear Joe,

Many thanks for your support.

Regards

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