I am really unhappy about the heaviness of implementing the model-view-controller (MVC) concept on an .NET GUI application. Is the only reason to have a application class on top of the Application.Run() and that starts the GUI to setup the global exception handler? If I modify the definitions within the GUI designer code region to get the tool and menu buttons implements a ICommands (the pattern) interface, I get stack overflow errors on closing the designer of my modified form. Ok, there is a comment to NOT do so, but how I should apply this? Ok, I can write a library project that encapsulates the tools and buttons as GUI components and then I can drag and drop it to my form to work around this limitation. So I made it by hand (oh my good)... Now I think about throw away the most of my work and keep the GUI Form class as big as it will be by implememting all of the stuff by itself. As my experiences with VB6 showed: this is usually not the best way to go.