Use the MVP (model, view presenter) to reduce the code in your webform code behind files. 1. it allows you to test the logic behind the webform 2. it seperate concerns (the code behind is still focused on presentation. don't let anyone tell you differently) 3. is isolates the ugliness created by web forms.
then place the transactional attributes on the selected presenters and members. the presenters will be registered in the IoC. If your familiar with the Rhino.Tools stack check out Rhino.Igloo. It does most of this work for you. I'm currently using it on my projects and love it (since I'm not using MVC). On Oct 21, 9:26 am, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > 2008/10/21 karron <[EMAIL PROTECTED]> > > > > > Which solution is better? The transaction boundary is not very clear > > in the first one, but there are many extra codes in the second one. > > Extra "testeable" code. > > Write "business code" in the code-behind is not a good idea to maintain the > future of your app. > > -- > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
