views:

132

answers:

1

I have a medium sized WinForm App (1 Form that hosts 40 user controls) that we use in house. I want to migrate over to WPF but I cannot do a Mass ReRelease.

My idea was, for now, to recreate the App 1 User Control at a time in WPF and have that hosted in the existing WinForm App. I would make them look nearly identical, at this point, so there would be no need for mass retraining.

My question is more to the point of, has any one else tried this and how does the data portion work.

I have recreated one of the WinForms User Controls as a WPF user Control. Do I need to publish that as a User Control Library?

How, then, would I access the DAL for that UC? I use a Linq to Sql data layer.


To clarify, user controls for me are a "Page", so Demographics is a user control.

Also, my DAL is a separate library. Would I want that in my WPF solution as well and then set up the data binding there and when I import it into the winform app it will come with it or it will just be able to find it at that same location...

+1  A: 

I am in the middle of a migration from a Win Form version to a WPF version of a program at the moment. I am using pretty standard controls, so there is not a whole lot of user control programming needed. I am finding it pretty easy. My back end is some ORM mapping from SQL2008, and it is pretty easy to work out.

WPF does have a bit of a different databinding technique, though, so you might have to spend some time looking at MSDn figuring out the CollectionView classes and whatnot.

as far as your user controls are concerned, are the controls accessing your Data driectly? Or are they instead accessing data through an intermediate interface?

Previously, my only user controls have been pretty simple (masked textbox, numeric up/down etc). These were all hosted in a control library. For what you are talking about, I would assume that importing your DAL reference, would still work. Otherwise I am unsure of what might be the problem.

Cory

OffApps Cory
They are accessing a LINQ layer that in turn access's the data. The LINQ layer is it's own dll. Thanks
Refracted Paladin
Ahh I see. Seems like it should work as a control library so long as the control code can access the DAL. Earlier today, I made a little test control that checked a package status (from FedEx) via the package tracking web service and included all of that in the control library. Everything appeared to go off without a hitch. In my case I just made a web reference, so likely you can just have a reference/import to the LINQ layer, and I imagine it will be alright.Cory
OffApps Cory
That would be epic beyond imagine! I will give it a go tonight and report backe
Refracted Paladin