we are trying to build an enterprise level application. The application will
consist of Warehousing, Invoicing, Payroll, Order Entry...etc. We are currenlty
using caringorm and basically build one Shell app and each of the other modules
as separate projects and then load them using module loader. We are trying to
find what is the best practise for building such an app. Do we build it as one
project and make each part as separate modules within the main app or do we
create it as separate modules liek we are doing currenlty. The main idea
behind our current approach was that each module was easily managable as a
seaprate project but then we are duplicating model locators if we load 4
modules into our shell app. Is this a good way to do it or shoudl we do it
another way. Any help will be greatly appreciated. sebssg

BUMP - I was really hoping someone could respond to this post, as I'm interested in hearing possible solutions.

hi

my experience tells me you are going on the right track because, making
several projects and then loading each on a needed base is what i do on my
projects that are enterprise applications, now i'm working on an application
that allows other developers to add modules themselves and i'm using that
aproach.

the only thing you have to be careful is to always try to use remote share
librarys so that applications get very small thus taking less time to be
downloaded by the client.

One thing, i'm using only webservices to tier my application with the backend,
because we can't have caingorm or other things like that instaled on a server ,
so we use webservices and httpservices