csla

I am running into an issue with ASP.NET MVC where it is forcing the user to log back in after about 20 mins of inactivity. I am using Forms Authentication and have increased the time-out in the config file as: <authentication mode="Forms"> <forms loginUrl="~/Account/LogOn" timeout="9999999" /> </authentication> I am also setting the session time-out in the config file as: <sessionState timeout="120"></sessionState> I am basing this off of Rockford Lhotka's CSLA ASP.NET MVC example and have the following in my global.asax: protected void Application_AcquireRequestState(object sender, EventArgs

The main web application of my company is crying out for a nifty set of libraries to make it in some way maintainable and scalable, and one of my colleagues has suggested CSLA. So I've bought the book but as : programmers don't read books anymore I wanted to gauge the SOFlow community's opinion of it. So here are my questions: How may people are using CSLA? What are the pros and cons? Does CSLA really not fit in with TDD? What are my alternatives? If you have stopped using it or decided against why? Before I specifically answer your question, I'd like to put a few thoughts down. Is CSLA right

I'm using Automapper to map my NHibernate proxy objects (DTO) to my CSLA business objects I'm using Fluent NHibernate to create the mappings - this is working fine The problem I have is that the Order has a collection of OrderLines and each of these has a reference to Order . public class OrderMapping : ClassMap<OrderDTO> { public OrderMapping() { // Standard properties Id(x => x.OrderId); Map(x => x.OrderDate); Map(x => x.Address); HasMany<OrderLineDTO>(x => x.OrderLines).KeyColumn("OrderId").Inverse(); Table("`Order`"); } } public class OrderDTO { // Standard properties public virtual int