On Tue, Aug 11, 2009 at 10:40 AM, MB Software Solutions, LLC<[email protected]> wrote: > Stephen Russell wrote: >> The downside is that WPF is dissociated from data as compared to the >> current WinForm of today. Sure if you code in other languages you >> consider that as SOP. That is the biggest hurdle that many have hit >> hard in jumping over. > > > Can you expand on this please? The "dissociated" part I mean. Is it > all just objects that you pass around? -----------------------
WPF objects are from WCF "web services" so if you have not done WCF because your app is a winform and doesn't need to run over to a web portion for data access you find it frustrating. On top of that your binding an object to XAML. In the older environment you had the iron fist of control on the container that was used. In WPF that control is still there it is now coded much differently. Currently there are a lot more controls to purchase then there was when it first came out and when I tried it. But that was a huge frustration in I don't have a grid, I have to build one each time I need it. I have not touched WPF in a year and a lot has gotten tweaked and tuned. But they also released that MVC <http://weblogs.asp.net/scottgu/archive/2008/02/12/asp-net-mvc-framework-road-map-update.aspx> -- Stephen Russell Sr. Production Systems Programmer SQL Server DBA Web and Winform Development Independent Contractor Memphis TN 901.246-0159 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
