Brady Kelly wrote:

abmv1 wrote:

Would you rather go back and do it without XPO !

Yes, I'd rather go back and do it with Entity Framework at the back and eXpressApp at the front.

I believe that when we complete our Domain Components (DC) technology (a part of XAF) and XAF will be fully abstracted from XPO, this scenario can be very easily done. However, with EF you may miss some XAF goodies powered by XPO.

The same is true for XPO :) Just mark your POCO with the PersistentAttribute and that is it.

Brady Kelly wrote:

I've been wrestling with their persistence layer, XPO, for about three days now, logged many questions on their support site, and lost many billable hours.

I checked your account and could find only 7 support tickets created by you during one week and half, back in February 2011. My only suggestion for you if you continue to use our products is to contact our Support Team as soon as you experience any difficulty, which was not resolved using the search through online docs, Code Central examples, knowledge base articles, training videos, blogs and finally a large database of support tickets asked by other users.

Brady Kelly wrote:

First up the spouse doesn't need a Spouse screen, children don't need a Children tab, etc. Instead of hours spent generating separate views for all three, I used three different objects. Shoot me. Then, XPO wouldn't let me declare a 1-to-1 association between PolicyHolder and Spouse. It insists that one side of an association must be a list or collection. I went ahead without the association. Shoot me.

I checked a related ticket (http://www.devexpress.com/Support/Center/Issues/ViewIssue.aspx?issueid=Q307810[^]) and think that your task was correctly resolved using the suggestion we provided. Could you please describe in greater detail what was unsatisfactory in it for you? I would love to learn more about your case and help you find an alternative solution, if possible.

Brady Kelly wrote:

This app is targeted at a small business, with, I must assume, a very non-technical owner. By no means enterprise stuff. He will never access the DB and add a PolicyHolder with an invalid spouse. If he does, it isn't a train smash and we can assist. On the other hand, my solution has absolute minimum of my code, and therefore minimum risk of post-deployment bugs. He gets a smoothly working app quickly, whereas on other projects I have gone out of my way to be perfect, and written hundreds of lines of code that required extensive beta testing.

A very fair comment about how much time XAF can save you. Also, both programmers and less-technical or ev

Hello, It would be great to see such a review. XAF and LS are definitely good candidates. BTW, you may find the blog post we made about LS helpful: LightSwitch Illuminates Application Development[^] If you have any questions about XAF, feel free to contact me at denis.garavsky@devexpress.com I will be glad to help you.

Hello, You can use any unit tester with DevExpress, because they are not specific to any developer tool by design. We even have our own Unit test runner tool[^] Many of us are using it internally. As for testing eXpressApp Framework applications, I suggest you have a look at our own functional testing framework - EasyTest[^]. It was specially designed to test XAF applications and we have been successfull using it to test XAF releases internally for more than 6 years. BTW, EasyTest also can be used to test regular non-XAF applications build using DevExpress components. Please contact our Support Team[^] in case of any questions. Finally, I suggest you look at the Best practices of creating reusable XAF modules by example of a View Variants module extension[^] blog I recently wrote. You may be interested in it, because it also demonstrates how EasyTest can save you a lot of time. Thanks, Dennis DevExpress Support, R&D, .NET Application Frameworks