About new classes, what is the best thing?

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.
12/14/2005 4:08:49 AM
Romulo
Gravatar
Total Posts 146
View Posts

About new classes, what is the best thing?

I would like to know your opinion with respect to the incorporation of new classes to mojo.  These classes correspond to the functionalities that I need it for my application.  I want to know if you advise to me to include them in mojoPortal.Data.dll and mojoPortal.Bussiness.dll and mojoPortal.Web.dll respectively, or must create my own assembled.  I want to know what is the practitioner more and than it facilitates the work simultaneously mine. I hope that you can understand to me.

I will be tuned
12/14/2005 4:54:48 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: About new classes, what is the best thing?

I think it is ok to include them in the same assemblies but I would create new classes. For example don't put your custom data access code in dbPortal.cs, create a new class in the data project. This way if you later want to separate them into their own assemblies it will be easy.
Also this will avoid problems when you want to get the latest mojoportal code using SVN Update.

You may sometimes get a conflict when svn tries to merge the changes in the .csproj files. In this case you could let the version from svn win and then just right click your classes to include them back in the project after the update. Most of the time it should be ableto merge them without conflicts.

Hope it helps,

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