Hot answers tagged


I don't think it's unreasonable for your abstract base class to provide an empty implementation of the IDisposable interface, and for subclasses to implement their own implementation as required. That seems to me a commonly used and understood pattern.


Brian Agnew's suggestion is very much applicable, but I'd like to point out something else: I get the feeling that maybe the actors (the plugged-in behavior you mentioend) on your model are carrying two very different responsibilities. Alternatively, you could design your framework to have a separate registration mechanism, exclusively for disposable ...


As Robert Harvey commented, MVP (model-view-presenter) is the architectural pattern of choice for Winforms. MVP is really just a flavor of MVC though. Your form (view) should implement an interface defining the public API of the view. FooForm : IFooView, Form And it will expose some of its elements via properties, say maybe a textbox input. public ...


Have a look in HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\NewProjectDialog where the FxVersion key will contain the default framework choice. You could change it to a higher version and find out if it's a mistake or not. Probably not. You'll get a bunch of features & fixes in any case. Here are the Release Notes for .NET Framework 4.6.1, the ...

Only top voted, non community-wiki answers of a minimum length are eligible