Search

I recommend to never use InProc sessions for real apps. I have used a State Server to handle sessions in a web farm. It is a pretty good solution and you avoid the appdomain recycle problem for InProc. I had a large web app where we used session variables and passed them from form to form exactly as you described. The only thing to add is that once

You can't save a child object directly. So doc=doc.Save should not work. You need to save the root which saves its children: activity = activity.Save() Joe

I do not like the additional dependency. As I recall there was a huge backlash about this type of dependency in earlier work you did. For that reason alone I would not make the change. If DataAnnotation exception was in a standard .Net .dll that is always referenced anyway then I would be for it. Joe

In any class derived from it you have access to all the broken rules. Even rules that are set up in the abstract class. You should have an intermediate Base class which inherits from each CSLA type so that you can do custom work without altering CSLA. Then all your business objects inherit from your intermediate classes. This way you can add code to

I had this exact problem with creating a PO from a PO request. I also have to create it from a previous PO, a catalog, a PO on Hold, etc. In general I solved it like this: The PO business object has a method: Public Sub CreateFromReq( ByVal reqnumber As String , ByVal vendno As String , ByVal shipcode As String ) Inside this method you use the reqnumber