|visits||member for||2 years, 4 months|
|seen||Sep 7 '13 at 21:57|
Developer at mola.com
|bio||website||alvaromb.com||visits||member for||2 years, 4 months|
|location||Spain||seen||Sep 7 '13 at 21:57|
What is the right way to develop ASP.NET applications in order to separate data access from data visualization?
The problem is that it's not possible to switch to ASP.NET MVC. My main goal is to mantain similar separation between data access and UI layer, but simplifying the actual structure. Like always, there is a deadline for this development, so making an strong radical change is not an option actually. We're also switching from 2.0 to 3.5, so maybe things are developed in a different way in 3.5+, I don't know.