Hi,

I saw the DB toolkit but notice that it (and the role based security stuff) is not part of the core framework. I also don't know if those only operate as add-ons to the framework or as seperate items (I'd guess the security stuff wouldn't be a standalone option)

I still don't see how the framework could be compatible either with EF or with WPF data-binding concepts such as data templates but I'll be interested to hear how you get on.....

Best,
Viv

>Thanks for the feedback. The Prism reference is a new one for me. It looks interesting and I see your point about the role of the third party framework relating to all of these other technologies. I had another look at the Strataframe site last evening and reviewed some of the postings and available videos. It does remind me of the environment that I have been working in with Maxframe. I do alot of custom development for small businesses and I need something that will allow me to get in and solve problems for the client without breaking their budgets. VFP and Maxframe has been perfect for that purpose. Strataframe does look like it will fit the bill after I get through some adjustments. They even have a database deployment project that reminds me of the Stonefield Database toolkit which allows easy data distributions and updates.
>
>Bill
>
>>
>>Hi,
>>About a year ago I Iooked at various frameworks for possible use with WPF but at that time, AFAIR, there was nothing with any specific support for WPF.
>>
>>I haven't looked since - mainly because my gut feeling is that unless something is being written from the ground up to be completely WPF orientated it won't be a good fit in most areas. Even so:
>>
>>If you are planning on using EF then that will be handling pretty much all of the backend / ORM side.
>>If you use a MVVM pattern (which is the obvious route with WPF) then nearly all UI would be pure XAML.
>>If you add Prism to the mix then there's not a whole lot of areas left for a framework to fill.
>>
>>Just my .02c