>>>>I have been looking at switching to .net from vfp. I have toyed with mm.net at bit but have not purchased it. I am the only developer at a medium size company and build in house apps. While mm.net looks great for the backend, it has nothing for the ui. I want to use WPF to make mainly UI's that look like winforms type apps for business but will use some WPF features for enhancements that aren't possible in winforms. We are actually on a spending freeze now but I want to use this time to check frameworks out. Are there any frameworks that handle both the backend and UI? Should I use mm.net and get a UI framework? Keep in mind the cost too. mm.net is something like $600-700 and then a UI framework for $???? and then Expression Blend on top of that all for something like$300-400. All makes me wish vfp was going to live.
>>>
>>>Maybe it is good to have UI as separate? I suggest you to at least have a look at Devforce - www.IdeaBlade.com
>>>
>>
>>That's the one (big) thing I don't like about using a DataSource with a winform. It is breathtaking how much ADO code gets generated for you, except the UI is bound pretty directly to data. That's an abomination in any N-tier architecture I have seen.
>
>Mike,
>Sorry I didn't understand exactly - I still have problems with daily English after all these years not sure I am interpreting right:)
>
>Yes, too much code is generated for you. Is that what you don't like? I like it because if someone didn't do it for me, I would frst write a code generator that does it for me.
>
>UI is not bound and I like it really to have a control on what gets bound and stored (but a tool is provided to bind them for you).
>
>PS: BTW VS2010's just dragdrop binding to WPF controls is something I love most:)
>

Sorry. Sometimes I really do forget you are not a native English speaker.

I am fine with the amount of ADO code generated for me. What I am uncomfortable with is the data layer hooking straight into the UI.