I am looking forward to using Open Access but I was (and still am) a little weary about some of it's use when dealing with multi layer architecture on a web application. For instance, my typical setup would be to have the BLL dealing with all the queries and returning the resultant data to the UI and having the UI make changes to the OA entities and passing it back to the BLL for further processing and persistance (would prefer to use DTO in the UI and convert back to OA entities in the BLL).
So I would like to do something as clean as the following
Dim Customer as new OACustomer
Customer.Firstname = "Michael"
Dim Order = bll.OrderManager.GetOrderByID(1)
Order.Amount = 5.00
Now this to me seems really simple, clean and easy to work with, but for the life of me I can't seem to get this to work. It appears that I have to pass the objectscope to the BLL just so I can track the changes and I need to also declare the objectscope in a masterpage or httphandler to get it to work based on best practices. Seems needlessly complex and I dont like the idea of passing the objectscope with my methods. This couples my UI and service layer to tightly to OA for my liking.
Now I saw recently in the Q1 video something that looked like a context object which behaved (or appeared to) more like the Linq2SQL context. For instance in the query I noticed that the word scope of was omitted. I xant find more information about this anywhere and I am very interested indeed. If it simplifies the problem I mentioned above then I am sold.