Hi Evan

>Gary, what would you say is your productivity increase with Strataframe over just using .NET itself for a typical app?

I am doing mostly WinForms applications and I have seen your threads in recent times and am therefore aware that your application is ASP.NET based. So, I cannot speak for ASP.NET but I guess its a pretty huge leg-up with WinForms. In my scenario, I have just trained a team of five developers in the finer points of StrataFrame <s>. I have to say that I encountered a lot of resistance towards an application framework - these were not ex-Fox guys who were used to frameworks. Whilst they kicked and screamed, the penny eventually dropped and off they went. At certain points in the application, I recommended to some of the guys to use regular ADO.Net and datasets as opposed to StrataFrame business objects. The same guys started howling about how much extra work they had to do, why couldn't they use StrataFrame and so on. So, this is the kind of experience I have had with the framework. To create business objects, its literally as simple as going through a very nice tool, pointing at a table in a database and clicking a button. In return, you get a customizable, mapped, strongly typed business object. These kinds of tools are littered through the framework, integrate with VS2005 and can really make the productivity difference.

>What would you consider to be the major downsides to Strataframe?

Up to now, notwithstanding my total lack of experience using StrataFrame with ASP.NET, I haven't really encountered anything that I would class as a downside. When I have found issues, I have discussed them with the StrataFrame developers and if a generic and worthwhile change or resolution could be agreed, it has been incorporated into the framework almost overnight.

Best

-=Gary