Topic: OOP database use in .net, and MVC pattern

[jmaeding]

I am getting to the point where I can understand how expoerienced people separate out their prog to pieces that become adaptable to change.  This set of three articles seems good because he explains the steps pretty well:
http://www.codeproject.com/KB/database/AdoNetForOopPart2.aspx

Curious if any of it is outdated, as it was written Jan 19th, 2006. thx

[Draftek]

nTier is good way to break up an application logically.

I'm starting to lean away from Class Inheritance to Interface design as I evolve as a developer.
Basically building up an API for long term use.

[Glenn R]

Use inheritance and interfaces where they make sense...that's the best of both worlds.

[Draftek]

As far as MVC.
I used that architecture for a big project a few years ago.

Not sure it really applies to a small shop.

[n.yuan]

As far as MVC.
I used that architecture for a big project a few years ago.

Not sure it really applies to a small shop.

UI in Acad programming is mainly dialog box that collect user inputs in a "per-document" context. Patterns like MVP/MVC make this kind of UI development unnecessarily complicated in most cases, if the UI itself is not that too complicated. It may make sense when the app lives in Acad's application context, such as a modeless form/paletteset that deals with data accross drawings, or holds data from sources other than loaded Acad drawing...