Mojo for use in a webbase application

This is an open forum for any mojoPortal topics that don't fall into the other categories.

This thread is closed to new posts. You must sign in to post in the forums.
7/20/2005 4:42:15 AM
Jan Hussaarts
Gravatar
Total Posts 73
View Posts

Mojo for use in a webbase application

Hi,

I have built a couple of applications for  an industrial environment. One of  them is based on the portal stuff available on the asp.net web site. About two years ago I have built another application not based on any portal application. For this application I am developping new functionality. I would also like to add common look-and-feel for the pages and add user access control.

Mojoportal has some nice facilities for user access control. I also like the menu facilities. I compared Mojoportal with DNN, Omiportal and Rainbow. Mojoportal was the easiest environment within which I could setup a basic application.

Currently I am developpig my modules within the mojoportal libraries. This is not the proper way to do it. I think I should develop my stuff in a seperate webapplication, test it and when I am happy with it, make the functionality available for the portal I have created in Mojo. What is the easiest way to do this?

Since I don't use that much portal functionality, should I use a portal application like mojo for my goals?

Jan

7/20/2005 3:55:37 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Mojo for use in a webbase application

Hi Jan,

Thanks again for the design view fix you provided!

It is possible to build modules that plugin to mojoportal but have all of their code in external assemblies. I'm hoping at some point to put up a sample project illustrating that but I don't jave one right now.

You could also just use the latest code as a starting point and branch to build your application from there if you really don't need much of the CMS/Portal features and don't need to keep up with future features.

Or you could also pull it down from svn and add your own modules and pages. As long as your work is all in separate files you could build them into the same assemblies as mojoportal. You can pull again from svn later and get the latest core code and it won't touch your code since its not part of svn, though you would have to add your files back into the project each time after you got the latest mojo code then do a build and your code should still be as it was and should work. The only problem would be if you had to make changes in the mojoportal code to make your stuff work then you would need to branch.

I can't really say which is the best way to go, its kind of a judgement call but those are a few possible choices as I see them.

Hope it helps,

Joe
8/23/2005 11:36:41 AM
Jan Hussaarts
Gravatar
Total Posts 73
View Posts

Re: Mojo for use in a webbase application

Hello Joe,

What if i want to put it under source control, but the rest of the app not. It would be nice to have an example!

KR

 

Jan

8/23/2005 11:36:43 AM
Jan Hussaarts
Gravatar
Total Posts 73
View Posts

Re: Mojo for use in a webbase application

Hello Joe,

What if i want to put it under source control, but the rest of the app not. It would be nice to have an example!

KR

 

Jan

8/23/2005 2:34:53 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Mojo for use in a webbase application

Jan,

I'm not sure I undestand the question.

What if i want to put it under source control, but the rest of the app not. It would be nice to have an example

Does it mean?, your code or mojoportal code?

It would be nice I agree, if you come up with an example I'll be glad to share it. I have a theory of how to do it but honestly it will be a while if you wait for me to make an example because I am focused on development more than making tutorials for now.

The idea is that you can add your own pages (.aspx) and user controls (.ascx) and inherit from your own assemblies in the bin folder while still taking advantage of mojoportal features. You create a class library project for your code and make it reference mojoPortal.Web.dll for using built in features. You can maybe specify the output folder for compilation to be the bin folder under mojoportal web.
Your page would have something like this at the top of the markup:
Page language=c# Inherits=myCustomWeb.SomePage AutoEventWireup=false
and your assembly would be like myCustomWeb.dll

Or its ok to add your stuff in the same projects with mojoportal as long as you don't have to change the mojoportal code. When you get the latest mojoportal code from svn ,it won't touch your code but you may have to add the pages and code files back into the project because the project file from svn won't know about your files.

Hope it helps, wish I had time to do more.

Joe
8/25/2005 6:27:46 AM
Jan Hussaarts
Gravatar
Total Posts 73
View Posts

Re: Mojo for use in a webbase application

Joe,

I use Visual Source Safe for source control. I would like to keep doing that, but without adding all the Mojo stuff in it. Currently I develop my web modules in a subdirectory in the Mojoportol.web project. perhaps that is not the best way to do it, but at least it works fine.

If I have some spare time I will try out your suggestion.

Regards,

Jan

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