First, let me say that I have just begun exploring StrataFrame, so some of these observations may be the result of inadequate exploration or misconception... but here goes (my background is PowerBuilder, Delphi, many RDBMS's):

I really like the web site, the examples, and the StrataFram Help (especially the Getting Started stuff). I have created a simple single form / single Business Object WinForm application... so now I am an expert. <g>

Concerns (you had to suspect this would be the longer list... right?):

1) I question the idea of binding the Business Objects right to the forms. Why not bind a BO Proxy to the forms, and keep all the BO's in one container? I know there is some ability to Share Data... but why should this be a case by case implementation detail? In fact I would see this as something you guys already already addressed (at the macro level) with the Enterprise Server alternative to the Client Server approach of connecting each BO directly to the database. IOW, why would you want each form in an application have its own (Customer) BO with a private buffer... out of synch with each other form/(Customer) BO/buffer in the application?

2) There is a loud "silence" on the WPF/SilverLight front. Along these lines, there seems to be a bit of a hush over when the next maintenance release will appear... and what will be in it.

3) The use of "Select *" in the example SQL statements. Generally we remove the fingers of developers that do stuff like that. I'm not sure how your BO's react to changes in the database tables (renaming columns, changing data types, adding/removing columns, etc.). We find explicit column references helps us find the issues pretty quickly. Along this same line is the missing ability to Auto-Generate bound controls based on a Buisiness Object (or actually BO Proxy <g>.

4) There doesn't seem to be any system level caching capability.

5) Almost all the Help examples are in VB, which doesn't help a C# newbie.

6) And finally, why do the C# samples contain reverences to a VB construct...
//-- Forcibly close the application to stop message pumps from looping and preventing the application
// from closing
ProjectData.EndApp();

Mike;



Anytime!



I liked Delphi for Delphi and not so much of it's database access. However, I developed a complex database app that is 12 level deep in hierarchy relation and it's been working in a 2-tier environment since 2003 with zero problems.



SF is fairly new and [trust me] there is a lot of stuff in it that does not appear at first. But it has a solid core and foundation. The developers come all the way back from Mainframes experience. The interesting thing about this company, is that, not only they produce developers tools, they use the same tools to develop consumer products. To me, that won many points, because the support and developers could relate to your issues, versus some other companies who don't know the real world of business development.



I think after some time, you'll reach to the same confidence, once you communicate with SF team.



In any event, if you have questions, don't be shy and I'm sure you'll get your answers.



Take care!

..ßen