Good resource to understna and implement OO techniques in my current application?

[pradev]

Hello Friends,
I have been working on ASP.NET for the last 2 and half years. The
bad part of my experience is I have been working alone on all of the
projects and there was no peer around who knows .NET or OOP. So where
ever I go I just get to implement the ones I know or udnerstand. In all
of the projects I never implemented any of the OOP techiniques at all
but just a water fall approach like a classic ASP programming. Except
calling a connection string web.config file and put that in a DL and
BL to call stored proc and put the results in a Datasets or datareaders
as needed. Other than this my mind has no experience on how to take
full advantage of OOP. So I am just looking for a few pages of document
that explains a small project with just 2,3 database table objects and
how to design the components in OOP in .NET and catogorize the
components with the application of Abstraction, Inheritance,
Polymorphism, encapsulation, interfaces(when and why to create them)
and also the remaining things if I have forgotten any thing to mention
here.

Some one could help me with finding a resource like that. In a single
sentence I am confident enough to build web applications using ASP.NET
1.x/2.0 but feel handicapped in using and implementing OOP paradigm in
the application I work on. My objective is once the database folks are
done with database designing job and once its I have every thing ready
from the database I should be able to sit and design components looking
at the datamodel and design the components in .NET using OOP apradigm.
Thats my objective is. How and where do I get this kind of
understanding. I am not looking to happen this over night but a
starting point about how I need to start thinking or working from and
how?

Any help is greatly appriciated,
Thanks in advance,
-L

 

[Michael Nemtsev]

Hello learner,

Try to start from here http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/BOAGag.asp

l> Hello Friends,
l> I have been working on ASP.NET for the last 2 and half years. The
l> bad part of my experience is I have been working alone on all of the
l> projects and there was no peer around who knows .NET or OOP. So where
l> ever I go I just get to implement the ones I know or udnerstand. In
l> all of the projects I never implemented any of the OOP techiniques at
l> all but just a water fall approach like a classic ASP programming.
l> Except calling a connection string web.config file and put that in a
l> DL and BL to call stored proc and put the results in a Datasets or
l> datareaders as needed. Other than this my mind has no experience on
l> how to take full advantage of OOP. So I am just looking for a few
l> pages of document that explains a small project with just 2,3
l> database table objects and how to design the components in OOP in
l> .NET and catogorize the components with the application of
l> Abstraction, Inheritance, Polymorphism, encapsulation,
l> interfaces(when and why to create them) and also the remaining things
l> if I have forgotten any thing to mention here.
l>
l> Some one could help me with finding a resource like that. In a single
l> sentence I am confident enough to build web applications using
l> ASP.NET 1.x/2.0 but feel handicapped in using and implementing OOP
l> paradigm in the application I work on. My objective is once the
l> database folks are done with database designing job and once its I
l> have every thing ready from the database I should be able to sit and
l> design components looking at the datamodel and design the components
l> in .NET using OOP apradigm. Thats my objective is. How and where do
l> I get this kind of understanding. I am not looking to happen this
l> over night but a starting point about how I need to start thinking or
l> working from and how?
l>
l> Any help is greatly appriciated,
l> Thanks in advance,
l> -L
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche