How should one handle a Parent-Child relationship using MVP?
In a conventional MDI WinForms application, one would go like this:
How should one handle a Parent-Child relationship using MVP?
In a conventional MDI WinForms application, one would go like this:
What is the best way to allow a user to specify a SQL server and database from a Windows application?
I am working on building a Windows application that will require a connection to at least two different Microsoft SQL Server databases (for example, a source and a target), which may or may not be on the same server.
Would redrawing controls in c# give more performance?
Now I realize this is a kind of weird question but here it is:
Let us assume I redraw all the controls by myself rather than using the default provided ones (Obviously I’m talking of winforms as WPF is already a custom drawn control set and winforms are just a way to access the Win32 API). Now I make an application with my custom-drawn controls. Then I make an application with winforms, which, in turn, uses the Win32 API. Now, when I run both the applications, will there be any performance difference? If yes, which will perform better?
Choosing the right design pattern/architecture for a scenario
I have a situation, in which I would like your opinion about the best approach that I should take.
Choosing the right design pattern/architecture for a scenario
I have a situation, in which I would like your opinion about the best approach that I should take.
How do you separate view from logic in a Winform application?
I know there are patterns like MVC to separate view from logic, however, I don’t know how common they are in Winform applications.
How do you separate view from logic in a Winform application?
I know there are patterns like MVC to separate view from logic, however, I don’t know how common they are in Winform applications.
How do you separate view from logic in a Winform application?
I know there are patterns like MVC to separate view from logic, however, I don’t know how common they are in Winform applications.
How do you separate view from logic in a Winform application?
I know there are patterns like MVC to separate view from logic, however, I don’t know how common they are in Winform applications.