This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Why is the unit of work that each entity belong to not exposed for us to use (now that I know it is already a private property on the base Entity)? It sure would make some things easier. I remember this being a fequntly asked for feature of Linq-to-SQL. |
|
|
It is a protected property on the base entity, so it is accessible if you really need it. The reason for making it protected rather than public is to discourage casual use, for reasons discussed at http://www.mindscape.co.nz/forums/Thread.aspx?ThreadID=1402 |
|
|
That is awesome. Like I said before just the right amount of hoops to jump through. sorry for not researching this before I posted. |
|