Best approach for migrating projects.

Hello All,

I am migrating some VB.NET 1.1 code to WPF C# (.NET 3.0). Here is what I have done till now:

Before we move on, remember that the existing application is GDI intensive application and we are migrating JUST the graphics part to WPF for performance reasons.

So the approach has been,

1.) Migrate from VB.NET 1.1 to C# (I have used some conversion utility to do this job, although the result have been not so good, it has helped me get a basic structure ready)

2.) This C# code is at most .NET 2.0 compliant, because of the namespaces it uses. Namespaces like System.Windows.Forms, System.Drawing, System.Drawing.Drawing2D etc have no place in WPF based applications (or .NET 3.0).

3.) I am finding the equivalent namespaces in .NET 3.0 and figuring out what needs to be ported/re-written in 3.0 and doing so. But there are some classes within my application which interact with the graphics engine and pass the graphics engine object of these 2.0 namespaces like System.Drawing.Point, System.Drawing.Graphics as an example. I will not be able to change the types of arguments that these classes pass to the graphics engine.

I am in a dillema as to what the 3.0 WPF graphics engine should accept as parameters Should I take 2.0 inputs and convert them internally and do the processing OR should I have an interface that will accept the 2.0 parameters and convert them to 3.0 equivalents and pass these 'now-converted' parameters to a pure WPF graphics engine Which approach is better Are there any other approaches What are the pitfalls in either of them Do I have some tools/utility/code to do the conversions or I have to do them manually

Please guide. Thanks in advance.

Best Regards,

Kanhaiya.