Also the argument that it’s a code smell and that OO is supposed to get rid of switch statements isn’t necessarily valid – if i replaced every switch statement or if construct with polymorphism my code would become signifantly larger and difficult to maintain. While switch statements do increase the cyclomatic complexity of the code, but when you introduce polymorphism the complexity becomes an unknown quantity.

That may be, but all the time we have a switch statement, does it really have to be such a retarded, akward bastard?

Why is the start of the block marked with a colon? Why not use the curly bracket block any other construct use?

And why isn’t the break statement optional? Automatic fallthrough is prohibited, so it does nothing.

http://www.refactoring.com/catalog/replaceConditionalWithPolymorphism.html

OO languages were INVENTED to get away from switch statements.

http://video.google.com/videoplay?docid=-2058469682761344178&q=Dan+Ingalls

Rather, register the forms for each entity in a Dictionary static dictionary. Then the switch becomes:

IForm form = formFactory[e.EntityType];
form.Do();

You have to enumerate them somewhere to add them to the Dictionary, but if you do it this way, you can drive that enumeration from anything ranging from walking all loaded assemblies looking for the form to an XML/config file. This way everything just works.