39 reputation
12
bio website
location
age
visits member for 2 years, 4 months
seen Jul 9 '12 at 13:43

Feb
18
awarded  Notable Question
Oct
31
awarded  Popular Question
Jul
7
comment Best Architecture for ASP.NET WebForms Application
(2) Business logic in extended EF objects which had to go in the DAL layer (didn't realise partial classes had to be in the same assembly) (3) Business logic within aspx.cs files in the UI layer. However, it seems that there are often compromises when it comes to architecture but this is certainly a step forward. I feel that this is acceptable for the 1st release and as time goes on we can reassess our approach. Thank you for your help everybody. It is good to get a bit of direction as this area is so subjective.
Jul
7
comment Best Architecture for ASP.NET WebForms Application
What feels messy still is: 1) EF Objects in the UI (code behind files in the UI layer)
Jul
7
comment Best Architecture for ASP.NET WebForms Application
ok that's true, however my concern is, once it is released it will be harder to refactor because of the risk of breaking it when the stakes are much higher. So we would be stuck with code that is not as maintainable and harder to debug etc. I was tempted to learn / convert to MVP but that looked like too much work. So far I have just converted it to DAL, Domain, UI layers which feels more organised yet still allows the inevitable RAD that will be needed while the project is young. One day if necessary I can expand to MVP or MVC I suppose - after I have enough time to learn how it all works.
Jul
3
comment Best Architecture for ASP.NET WebForms Application
Thank you. I will look into using T4.
Jul
3
comment Best Architecture for ASP.NET WebForms Application
Thanks for your helpful tips. Yes, I have certainly been a bit overwhelmed with this. It seems to me that MVC would be the best pattern to use but MVP would be easier to achieve and would be the next best pattern. I have always used code behind files so always scratched my head about how business logic can be separated from presentation...so I should be able to essentially move my .aspx.cs files to the domain layer and have an inherits statement in the aspx? Certainly ending up with 3 layers would make me feel comfortable with releasing the 1st version - then I can improve it from there.
Jul
3
comment Best Architecture for ASP.NET WebForms Application
It seems that converting to MVP would also be a major change. The client wants to release very soon, so do you think the above mentioned architecture DAL / DA / UI (although not as ideal as MVP) would be acceptable for this type of application? Then after release we could look at moving to MVP in v2.
Jul
3
awarded  Student
Jul
3
comment Best Architecture for ASP.NET WebForms Application
oh sorry - I misread. Thank you - I will read about the MVP design.
Jul
3
comment Best Architecture for ASP.NET WebForms Application
The problem is, it would require a lot of work to refactor the project to MVC...if I keep it as a WebForms app with Domain Layer (code first, POCO), Data Access Layer (db context only) and UI, would you consider this an acceptable design for production? At a later date we could consider converting it to MVC I suppose.
Jul
3
asked Best Architecture for ASP.NET WebForms Application