I've been looking into the Sync services offered by Microsoft recently, and was wondering if anyone (Maybe Trevor) looked into this yet, and would have any feedback on building an appropriate class model or provider model that could be built to be used with the XPO suite.  I know in the past, things have been done using interfaces, where XPO thinks that it is connecting to a datastore, and indeed, it is, but being done via a WCF class  (The stuff that Oliver S. did).

I was theorizing, and hoping that someone could help me with this, that a new provider type could be used that XPO would see that all access seems to be done locally, but behind the scenes, the provider model could look at it and decide if the table is a local cache table, or is one that should be on the server, and pulled from there?

Any ideas?

"Richard Bennett" ha scritto nel messaggio news:227311@community.devexpress.com...

I've been looking into the Sync services offered by Microsoft recently, and was wondering if anyone (Maybe Trevor) looked into this yet, and would have any feedback on building an appropriate class model or provider model that could be built to be used with the XPO suite.  I know in the past, things have been done using interfaces, where XPO thinks that it is connecting to a datastore, and indeed, it is, but being done via a WCF class  (The stuff that Oliver S. did).

I was theorizing, and hoping that someone could help me with this, that a new provider type could be used that XPO would see that all access seems to be done locally, but behind the scenes, the provider model could look at it and decide if the table is a local cache table, or is one that should be on the server, and pulled from there?

Any ideas?

---

NerdzOnline Technical Services, Inc.
"Where is your technology taking you?"

P.O. Box 4636
Reading, PA 19606
Mobile: 484.529.9935

---

http://community.devexpress.com//forums/p/66899/227311.aspx#227311

Hi there Luca,

I'm going to put a Question/Suggestion into DevExpress and see what comes of it.  My problem is/has been that most of my clients need software to run in disconnected mode, so I may be trying to find out how the XPO suite works "under the covers" and then extend it to support what I need.

I'll post the link to the issue once i get it written.

Thanks.

 As promised... the link.

http://www.devexpress.com/issue=S91964

Another gentleman requested the same idea, and I have his case linked in mine.  I also have his case being tracked under my profile, and stress to Luca, and anyone else that is in need of this feature to track it, so hopefully, Oliver and the rest of the DevExpress team sees this thought and can either give us some insight on how to build it, or can build it into the core system.

 Any progress, Richard?

 I just adding my vote to this thread as well (along with tracking the suggestions).

I can see DX stance on this and it IS ok to set up Sync services independetly until one would like to inject busyness object specific logic into the syncing process and THEN it becomes a pain going back to  pure SQL when you could continue doing things "XPO way" if these two were integrated. Especially in the context of XAF...

Evgeniy

 Evgeniy:

Yes,  the overwhelming answer from the Dx team is to use Merge replication (bleh) for this scenario.  Very buggy when you are trying to use XPO.  Sync Services for ADO.Net with XPO makes XPO very unstable as well.  Added to this, most of the clients we are taking on are not technically proficient.   Anything past clicking Next to get a software package setup in their environments is too much for them (literally in some cases).  Merge replication requires a certain degree of technical knowledge most individuals do not have, and to hire a DBA guy to setup merge replication is a waste, since our b2b app is not cheap.

We are in the process of converting dealprocessor from using the XPO suite to go to Linq to SQL.  Trevor, and a few other folks on the forum have successfully come up with being able to use the Dx suite to be able to provide items like WCF services, and handled it well, but there is a lot of repetitive coding that is required.  Being a small isv, I cannot afford the extra time in re-writing the codebase that I have created already (meaning creating a dto set of objects, a business set of objects, and an OR/M set of objects).  I need to have tools that fit the scenario that I'm doing with minimal coding, so that I can focus on the problem domain.  In my evaluation to this point, Linq to SQL will fit quite nicely in our needs.

Julian, if you read this, I take my hat off to you... you created something with your suite that is above what the competition has currently.  I would caution you however to have your team really evaluate what the reasoning is that they do not want to implement new technology theories (like WCF) in their codebase.  I get it's hard, but so is everything in life.  Most of us microISV companies that are purchaing your software are doing so because it helps solve a problem domain for their projects.  Unfortunately, the market trends are beginning to show cloud computing, web services, etc. becoming mainstream. As of right now, some of your tools (like XPO) cannot handle well.  This is a big downfall, and gets developers, much like myself, to question if they should re-up the maintenance in your software, move to a new package, or start rolling our own as we need tools.  If you wish to discuss, my contact info is in my signature.  Feel free to contact me.

 Richard, thanks for the thorough reply. O do hope that those things are coming to XPO (and XAF) and DX is simply holding back the information untill its ready for release...

Evgeniy