Re: Methodology
- From: "Mark A. Sam" <msam@xxxxxxxxxxxxxxxxx>
- Date: Sat, 25 Mar 2006 10:22:13 -0500
Hello Kevin,
Thank you for the dissertation. I understood it all. I'm going to snip to
where I want to address what you wrote:
It also seems to me however, that
your mindset remains procedural, rather than object-oriented. This is the
most important difference in the .Net platform.
I'm not sure what you mean by procedural. I think I am object oriented
being an Access developer. I'm certainly event oriented. I look at an
object and want to know what events are available and maybe am prodecural
within the events. I don't see programming as a continuous pages of code
with subroutines and goto's.
The difference between a class and an object is that a class is a pattern
or
design for objects. An object is an "instance" (working copy) of a class.
There's a good bit more to it than that,
That helped me a lot. I never had a clue what class was, and now it makes
sense, especially the inheritance part.
but I'm hoping to give you
enough
to get you interested and started, and let you take it from there.
You gave me a lot here. I don't think however that I'll get to intimately
involved the intricacies. I have a couple clients that want websites and
want me to do them, which is the only reason I am in it. After researching
and coming across Visual Web Developer, I saw that I could do what one
client wants and control the output easily with programming. I hope to get
funding to revamp the website you wrote for me years ago and is still
"truckin". When that happens, by programming days are done, because I will
hire it out to people who can do it better than me.
The beauty part is that one can design one's own classes, just as one can
design car or truck engines by combining various engine parts together in
different configurations. Once you develop a good set of configurable (or
"extensible") classes, you can re-use them in various applications which
perform similar work, without having to write them all over again.
Getting back to the code you posted, you may have noticed that similar
code
appears throughout your application. The process of opening a Connection
and fetching data, when using the same database or data source, is almost
identical. The classes of the .Net CLR are designed like engine parts, to
be useful in a large variety of configurations, to connect to any kind of
data source. But *you* Mark, are only connecting to one. So, you can
create your own "Database tier" of custom classes which perform all of
these sequences in the same way without having to rewrite all that code
over and over again.
I guess I'm lost here. I don't write code over and over (other than DAO), I
write it usually once, then copy and past it then modify it. Are you saying
that creating a class is different or more advantageous?
If you want to expand your enterprise, you can get even more
compartmentalized, by creating a business tier, which performs operations
"under the hood" without having any user interface, and a "presentation"
(user interface) tier, which exposes the business objects in a
user-friendly way. This way, you can create, for example, another
interface for the same type of applications, exposed as a Windows Form
executable, or perhaps a Web Service.
It sounds like more than I want to tackle.
At any rate, the link I posted should give you a lot of useful
information,
I'll definitely check it out and thank you for the time and effort in
writing this excellent reply.
and a lot to think about, as well as some really nice, pre-built libraries
for implementing various common "patterns" of applications.
--
HTH,
Kevin Spencer
Microsoft MVP
Professional Numbskull
Show me your certification without works,
and I'll show my certification
*by* my works.
Even so faith, if it hath not works, is dead, being alone.
Yea, a man may say, Thou hast faith, and I have works:
show me thy faith without thy works, and I will show thee my faith by my
works. James 2:17-18 (KJV)
Those that can do, those that can't become talk show hosts. Mark A. Sam
.
- Follow-Ups:
- Re: Methodology
- From: Kevin Spencer
- Re: Methodology
- References:
- Methodology
- From: Mark A. Sam
- Re: Methodology
- From: Kevin Spencer
- Methodology
- Prev by Date: Re: regular expression question
- Next by Date: Re: regular expression question
- Previous by thread: Re: Methodology
- Next by thread: Re: Methodology
- Index(es):
Relevant Pages
|
Loading