>>>>>>>>>>>>>>Hi
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>I'm trying to find some good examples of WPF applications. Development walkthroughs etc
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>Something that involves data access.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>Any recommendations.
>>>>>>>>>>>>>
>>>>>>>>>>>>>Hi,
>>>>>>>>>>>>>Maybe something here: http://www.actiprosoftware.com/Support/ResourceGuides/WPF/ViewCategory.aspx?ResourceGuideCategoryID=26
>>>>>>>>>>>>>
>>>>>>>>>>>>>But, to me, the problem with most WPF samples is that they tend to favour showing off the clever UI stuff rather than demonstrating simple 'ground up' examples
>>>>>>>>>>>>
>>>>>>>>>>>>Yes thats what I'm finding.
>>>>>>>>>>>>
>>>>>>>>>>>>I may just put it to one side till vs2010 as I can't believe how long winded the data access is.
>>>>>>>>>>>In what way 'long-winded'? WPF uses the same NET data access classes as a WinForms or ASP.NET app.......
>>>>>>>>>>
>>>>>>>>>>I can't drag and drop data controls onto a form.
>>>>>>>>>
>>>>>>>>>Something is wrong then, I just tested in a new WPF simple application from scratch and dropped a few controls (generic vs controls, not infragistics) on a window...
>>>>>>>>
>>>>>>>>I think Nick was referring to the Winforms ability to drag fields from a datasource and have the relevant control created and databound automatically (something that's slated for WPF in VS2010)
>>>>>>>
>>>>>>>Yep
>>>>>>
>>>>>>Oh, I don't bind data that way so I wouldn't even notice. :( Sorry Nick.
>>>>>
>>>>>No problem .
>>>>>
>>>>>Do you see that as an inferior way of working ?
>>>>
>>>>It may depend on the app but it's close-coupling the UI to the backend which is not usually a good idea....
>>>
>>>OTOH I feel that decoupling being somehow essential is a bit of a myth. Whats the supposed benefit for most business. For small and medium sized its irrelevant.
>>
>>I agree, as above, that it may depend on the application. However I don't think that designing in the separation is a major factor in development costs.
>>I also don't think that the size of the business is the factor here - it's the size of the application. A small business that invests heavily in a large application with tightly-coupled design is likely to have more headaches than a big business using a simple quick-and-dirty solution to a simple problem.....
>
>I'm not against n-tier de coupling etc. But with WPF you don't really have choice, ironically WPF is closely coupled to MVVM. Maybe Microsoft see it as a problem and thats why data drag and drop returns in VS2010.

Hmm. It's easy enough to create a tightly-coupled WPF app - just not quite to easy as in WinForms <g>
And MVVM can be used as a general design pattern - it's just very well suited to WPF since the MVVM 'View' can usually be pure XAML.

Maybe Microsoft see it as a problem and that's why data drag and drop returns in VS2010.
I wouldn't believe they see the existing capabilites as a problem - presumably they just want to provide the drag-and-drop as an option for those who want it.

Best,
Viv