How much segregation is too much in this design?
We are working on ASP.NET webforms application developed using WCSF (MVP pattern). In the application, there is a search screen that allows the user to enter some fields and display the results.
Again MVVM / MVP story , passing interface of a view to its view model why it is bad?
I have used WPF for an Enterprise solution (hundreds views heavily used Data inputs and validation) in MVP pattern (it was a clean solution usually small amount of code behind forms and main code was in pretension layer which we called it user interface process or UIP layer )
Again MVVM / MVP story , passing interface of a view to its view model why it is bad?
I have used WPF for an Enterprise solution (hundreds views heavily used Data inputs and validation) in MVP pattern (it was a clean solution usually small amount of code behind forms and main code was in pretension layer which we called it user interface process or UIP layer )
Again MVVM / MVP story , passing interface of a view to its view model why it is bad?
I have used WPF for an Enterprise solution (hundreds views heavily used Data inputs and validation) in MVP pattern (it was a clean solution usually small amount of code behind forms and main code was in pretension layer which we called it user interface process or UIP layer )
Again MVVM / MVP story , passing interface of a view to its view model why it is bad?
I have used WPF for an Enterprise solution (hundreds views heavily used Data inputs and validation) in MVP pattern (it was a clean solution usually small amount of code behind forms and main code was in pretension layer which we called it user interface process or UIP layer )
How to design console application with good seperation of UI from Logic
Is it considered an overkill for console application to be design like MVC , MVP or N tier architecture? If not which is more common and if you can link me to simple example of it.
How to design console application with good seperation of UI from Logic
Is it considered an overkill for console application to be design like MVC , MVP or N tier architecture? If not which is more common and if you can link me to simple example of it.
How to design console application with good seperation of UI from Logic
Is it considered an overkill for console application to be design like MVC , MVP or N tier architecture? If not which is more common and if you can link me to simple example of it.
DAL Exception handling in a MVP application
In a MVP win forms application I’m handling exceptions as follows in DAL.
DAL Exception handling in a MVP application
In a MVP win forms application I’m handling exceptions as follows in DAL.