Is there a tool that can convert C# 1.1 Forms design to the more recent standard?

+1 A:

No. Sry to say but there is no such tool, that is still manual work. If you're looking into doing it anyway I would suggest looking into WPF development, since the separation is much easier to realize there.

ntziolis 2010-04-28 22:38:56

Why is the separation any easier with WPF? I've never had any problems keeping separation of concerns with WinForms or WebForms. "Just Say No" to business logic on the page / form.

John Saunders 2010-04-28 22:42:24

For me that mainly relates to the easier and more powerful binding. Yes, a lot of the binding available today in WPF was possible with WinForms but it was way more complicated to setup and it clocked up the codebehind files. But its a personal thing I guess since I consider proper binding and included validation part of the business logic.

ntziolis 2010-04-29 01:04:19

+1 A:

There is no "standard", but lots of standard like ways people separate logic from UI. It forces you to design a particular way. So its a bit impossible to automatically redesign your software.

The best you have is refactoring tools, check out something like Resharper, makes it a bit safer to make some transformations.

Keith Nicholas 2010-04-28 22:42:45

+1, ReSharper 5 has an action "Move declaration(s) to another type part", which moves selected declaration(s) to another partial class.

Jens Granlund 2010-04-28 23:39:24

+1 A:

No tool, but easily accomplished with cut-and-paste text editing. Add a new form to your project. In the Solution Explorer, open the node next to the form and double-click the Designer.cs file. Cut and paste the InitializeComponent() method from your old form to that file. Cut and paste the rest of your code. Remove the old form, change the class name of the new one.

Hans Passant 2010-05-01 19:41:28

ansaurus

tags:

views:

answers:

Is there a tool that can convert C# 1.1 Forms design to the more recent standard?

related questions