I am currently working on a software application that will have certain portions which will run in a disconnected model. To speed development along, I have been using another OR/M tool suite developed by the team at DevExpress.

I am at a crossroads at this point, as their suite/framework feels like it is only meant for use when it's a single database, and a single software application against that database. I know that with nHibernate/Hibernate, the Framework is being used more commercially, and as such, probably has been used in the same scenario as above.

I have been theorizing of ways to make this work, but would like to check with the nHibernate community, as I am in the process of evaluating whether to use direct sql to objects, continue using and struggling with the DevExpress suite for OR/M, or switch to using nHibernate going forward.

Any insight or thoughts would be helpful. For reference, the way the OR/M works in DevExpress is that you build your classes as a decendent of a general abstract object called XPObject, and then build it out. the XPO framework, as its called, generates the database to match the object layout.

I have also been looking into Microsoft Sync services, and did not know if anyone has yet worked with that along side of either nHibernate or other OR/M frameworks.

As I said, any insight would be most helpful and appreciated