New answers tagged

2

I think the worst part of the interface is the fact that there is temporal coupling. Clients of the interface are expected to call methods in the right order, and this order isn't enforced by the type system, so it can only be infered by trial-and-error or by pre-existing domain knowledge. My initial thought is to keep a clean separate interface for the ...


0

Start with some building blocks first: make a class MyConfigData, a simple DTO object, no special logic here. It should hold all the configuration data you want to manage implement methods void SetData(MyConfigData config) and MyConfigData GetData() in your form - these two methods should transfer the data from the DTO object into the form, and vice versa. ...


0

> Is there any clean way of disconnecting the save > logic from the WinForm that will enable me to reuse the save code? Usually this is solved by implementing a Three-tier_architecture Data Object Class with a property of all attributes used in the database and the gui a gui layer that transfers data between Data Object and gui database or ...



Top 50 recent answers are included