> No it wouldn't have. We use NetTiers at Chase, and while maybe not ideal, > it works well, and we add custom logic to generated derived classes.
I've been using a similar setup (except using CSLA, not NetTiers) for a while now, also using base + derived classes. > This is legacy from before we had generated partial classes. I'm a little bit surprised that everybody seems to be saying that partial classes > inheritance. I'm not saying that inheritance is a perfect fit for the whole "reverse engineer DB into a persistence layer" scenario, but I prefer to at least have some buffer between the generated code and the business logic. There are certain things in the generated code that you should see / touch, and inheritance helps ensure that you do not. In cases where you do need to do muck around with the plumbing, the override keyword at least helps indicate that you have done so. What good arguments pro-partial classes am I missing? -- Daniel. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
