OO设计和编程...... [英] OO design and programming...

问题描述

我对vb .net完全不熟悉。我正在使用visual Studio 2005将一个

Access 2000应用程序重做为使用SQL Server 2000的.net OO应用程序 -

所以完全重写并重新思考如何应用程序将工作。


我从来没有完成任何OO编程，虽然我在程序中使用了OO

技术 - 实际上从未真正设计过类

等...


所以我在重写这个Access应用程序时有点紧张，因为它是一个

大型应用程序，我正在学习许多以前从未使用过的新东西，例如vb.net，OO设计，SQL服务器和Crystal！使用所有这些新东西做一个大项目是一个令人难以置信的小想法！


现在我认为最好的起点是查看现有的

应用程序并尝试从中提取我的一些课程将用于新应用程序然后添加新课程。然后，我可以确定所需的每个类的所需数据和方法 - 这将导致

物理SQL Server数据库设计，以方便我的类设计。物理数据库

将与旧的Access 2000设计有所不同。


我想我正在寻找那些在这一切工作的人的一点指导

时间。我是否按照正确的顺序这样做了？


我也在寻找一本关于OO设计原理的神书 - 倾向于

对vb.net很好，但校长都是一样的，所以只需要一个好的.O / b $ b整个OO设计书都会很好。


有没有人知道一个好的 - 或者一些非常好的参考资料

这在互联网上？我不确定有多少课程，例如我需要模仿父子关系。父母

将是一个班级，而孩子们将是另一个班级 - 但是它将是b $ b b b是父母的子类等等。弄清楚有多少课程

和他们的关系 - 什么时候创建新课程或包含所有数据

在一个班级是我很难用的。 （什么时候分类和

什么时候不...）


任何帮助都会非常感激!!!


谢谢，Brad

解决方案

您应首先设计数据结构，这将为您的业务带来
图层类，然后是UI。


为了引用自己，我刚刚向其他人发布了以下推荐

：


Deborah Kurata在1月份出版了一本书，名为在VB2005中做对象

。它解释了GUIDS的分析方法和

设计，然后明确地向您展示如何设置3层。

您最终编写了整个应用程序。我发现这本书很清楚，而且简洁，比阅读整本理论书要容易得多。

它还有很多关于保存你的项目的好东西

设置，代码片段和所有赌注，将数据绑定到对象。


Rockford Lhotka还有一些商业对象书籍

应该是最终的。


Robin S.

------------------ --------------

" Brad Pears" < do ******** @ notreal.comwrote in message

news：％2 **************** @ TK2MSFTNGP04.phx。 gbl ...

>我对vb .net完全不熟悉。我正在使用visual Studio 2005使用SQL Server 2000将一个
Access 2000应用程序重做为.net OO应用程序 -
所以完全重写并重新思考这个应用程序将如何工作。


我从来没有完成任何OO编程，虽然我在程序中使用了OO

技术 - 实际上从未真正设计过

类等...


所以我只是在重写这个Access应用程序时有点紧张，因为它是

a大应用程序而且我正在学习这么多新东西我之前从未使用的东西

，如vb.net，OO设计，SQL服务器和Crystal！这是一个小小的心灵

使用所有这些新东西做一个大项目令人难以置信!!!


现在我认为最好的起点是查看现有的

应用程序并尝试从中提取新应用程序的某些类将为b $ b，然后添加新类。然后我就可以确定每个类所需的数据和方法 - 这将导致

物理SQL Server数据库设计，以方便我的类设计。物理

db将与旧的Access 2000设计不同。


我想我正在寻找那些在这一切工作的人的一点指导

时间。我是否按照正确的顺序这样做了？


我也在寻找一本关于OO设计原理的神书 - 倾向于

对vb.net很好，但校长都是一样的，所以只需

整体的OO设计书会很好。


有没有人知道一个好的 - 或者一些非常好的参考资料

这个在互联网上？我不确定有多少课程这样的事情

我真的需要模仿父子关系。

父母将是一个班级，孩子们将是另一个班级 -

但它是父母等的子类等等。弄清楚如何

许多课程和他们的关系 - 何时创建新课程或

包括一个课程中的所有数据是我很难用的。

（什么时候继承，什么时候不...）


任何帮助都会非常感激!!!


谢谢，Brad

你是如何提前看到这本书的？任何获得它的机会

提前？我现在开始这个，很高兴有一个很好的参考

方便...


感谢您的帮助。

RobinS < Ro **** @ NoSpam.yah.nonewrote in message

news：p8 ************************ ******@comcast.com。 ..

您应该首先设计数据结构，然后将

引导到您的业务层类，然后是UI。


为了引用自己，我刚刚向其他人发布了以下推荐

：


Deborah Kurata有一本书出来在1月份，在VB2005中称为做对象

。它解释了GUIDS的分析方法和

设计，然后明确地向您展示如何设置3层。

您最终编写了整个应用程序。我发现这本书很清楚，而且简洁，比阅读整本理论书要容易得多。

它还有很多关于保存你的项目的好东西

设置，代码片段和所有赌注，将数据绑定到对象。


Rockford Lhotka还有一些商业对象书籍

应该是最终的。


Robin S.

------------------ --------------

" Brad Pears" < do ******** @ notreal.comwrote in message

news：％2 **************** @ TK2MSFTNGP04.phx。 gbl ...

>>我对vb .net完全不熟悉。我正在使用Visual Studio 2005使用SQL Server将一个
Access 2000应用程序重做到.net OO应用程序中 - 所以完全重写并重新思考这个应用程序将如何工作。

我从来没有完成任何OO编程，虽然我当然在程序中使用了OO
技术 - 只是从未真正设计过
类等......

所以我在重写这个Access应用程序时有点紧张，因为它是一个大型应用程序，我正在学习很多我以前从未使用过的新东西，比如vb.net，OO设计， SQL服务器和水晶！使用所有这些新东西做一个大项目是一件令人难以置信的事情！

现在我认为最好的起点是看现有的
应用程序并尝试从新应用程序中提取我的某些类将是什么，然后添加新类。然后我可以确定所需的数据和每个类的方法 - 这将导致物理SQL Server数据库设计，以方便我的类设计。
物理数据库将与旧的Access 2000设计完全不同。

我想我一直在寻找那些在此工作的人的一点指导。我是否按照正确的顺序做了这个呢？

我也正在寻找一本关于OO设计原则的神书 - 倾向于对vb.net很好但是校长们都是同样如此只是一个整体的OO设计书会很好。

有没有人知道一个好的 - 或者一些非常好的参考资料
在互联网上？我不确定有多少课程，例如我真的需要模仿父子关系。
父母将是一个班级，孩子们将是另一个班级 -
但它会是父母的子类等等。弄清楚如何
许多班级及其关系 - 什么时候创建新类或
包含一个类中的所有数据是我很难用的。
（何时进行子类化，何时不...）

谢谢，布拉德

我认识Deborah，因为她是我当地的.Net用户组的负责人。

我有一些额外的时间，并且知道她正在写她的书，所以

我提议阅读内容并通过所有示例工作

work。这对我们双方来说都是一个很好的机会。 :-D所以我是

对不起，但它要到1月份才可用。它确实听起来就像你需要的那样。它真的为我带来了一切

，并且是我从VB $ VB $ VB跳到VB.Net的基础。它解释了类和继承以及对象。

阅读它让我更容易理解其他所有内容

我之后阅读。


好的一面，1月份不是很远吗？


如果你很绝望，你可以查看她的VB6 for Objects书籍;

它可以在亚马逊上获得67美分。它是错误的

版本的语言，但你会得到一般的想法。那个

版本在分析/设计阶段有更多的信息，

来自我的理解。


如果我听到的话关于它的任何事情都会早点出来，或者如果我能够获得预付款，我会在下周告诉你。


罗宾S.

--------------------------


" Brad Pears < do ******** @ notreal.comwrote in message

news：uB ************** @ TK2MSFTNGP06.phx.gbl .. 。

你是如何提前看到这本书的？有机会早点获得
吗？我现在开始这个并且很高兴有一个好的

参考方便...


感谢您的帮助。


RobinS < Ro **** @ NoSpam.yah.nonewrote in message

news：p8 ************************ ******@comcast.com。 ..

>您应首先设计数据结构，然后设置您的业务层类，然后是UI。
<为了引用自己，我刚刚向其他人发布了以下建议：

Deborah Kurata在1月份出版了一本书，名为在VB2005中做对象
。 。它解释了GUIDS的分析和设计方法，然后明确地向您展示了如何设置3层。
您最终编写了整个应用程序。我发现这本书清晰简洁，比阅读一本关于理论的整本书容易得多。
它还有很多关于保存项目设置的简洁设置，代码片段并且打赌所有，将你的数据绑定到对象。

罗克福德Lhotka也有一些商业对象书籍应该是确定的。

Robin S.
--------------------------------
" Brad Pears" < do ******** @ notreal.comwrote in message
新闻：％2 **************** @ TK2MSFTNGP04.phx.gbl ...

>>>我对vb .net完全不熟悉。我正在使用Visual Studio 2005使用SQL Server将一个
Access 2000应用程序重做到.net OO应用程序中 - 所以完全重写并重新思考这个应用程序将如何工作。

我从来没有完成任何OO编程，虽然我当然在程序中使用了OO
技术 - 只是从未真正设计过
类等......

所以我只是在重写这个Access应用程序时有点紧张，因为它是一个大型的应用程序，我正在学习很多我从未使用过的新东西，比如vb.net，OO设计， SQL服务器和水晶！使用所有这些新东西来做一个大项目是一件令人难以置信的事情！

现在我认为最好的起点是看看现有的应用程序，并尝试从新应用程序中提取我的一些类，然后添加新类。然后我可以确定所需的数据和每个类的方法 - 这将导致物理SQL Server数据库设计，以方便我的类设计。
物理数据库将与旧的Access 2000设计完全不同。

我想我一直在寻找那些在此工作的人的一点指导。我是否按照正确的顺序这样做了？

我也在寻找一本关于OO设计原则的神书 -
倾向于vb.net会很好但是校长都是相同的
所以只要一个整体的OO设计书就会很好。

有没有人知道一个好的 - 或者一些非常好的参考资料
这个在互联网上？我不确定有多少类我真的需要模仿父子关系。
父母将是一个班级，孩子们将是另一个班级 -
但它会是父母的子类等等。弄清楚如何
许多班级及其关系 - 什么时候创建新类或
包含一个类中的所有数据是我很难用的。
（何时进行子类化，何时不...）

谢谢，布拉德

I am completely new to vb .net. I am using visual Studio 2005 to redo an
Access 2000 application into a .net OO application using SQL Server 2000 -
so a complete rewrite and re-thinking of how this app will work.

I have NEVER done any OO programming at all although I have used OO
techniques in programs of course - just never actually designed the classes
etc...

So I am just a tad nervous in re-writing this Access application as it is a
large app and I am learning so many new things I have never used before such
as vb.net, OO design, SQL server and Crystal!!! It is a little mind boggling
to be doing a big project using all this new stuff!!!

Right now I figured the best place to start was to look at the existing
application and try to extract from that what some of my classes will be for
the new app and then add new classes. Then from that I can determine the
data required and methods for each class - which will then lead to the
physical SQL Server db design to facilitate my class design. The physical db
will be WAY different than the old Access 2000 design.

I guess I am looking for a little guidance from those who work in this all
the time. Am I doing this in the right order basically ?

I am also looking for a really god book on OO design principals - leaning
towards vb.net would be good but the principals are all the same so just an
overall OO design book would be good.

Does any one know of a good one - or some really good reference material for
this on the internet? I am unsure of things like how many classes do I
really need to mimic a parent child relationship for instance. The parent
would be one class and the children would be yet another class - but would
it be a subclass of the parent etc.. etc.. Figuring out how many classes
and their relationships - when to create new classes or include all the data
in one class is what I am having a hard time with. (when to subclass and
when not to...)

Any help at all would be most appreciated!!!

Thanks, Brad

解决方案

You should design the data structures first, which leads
to your business layer classes, and then the UI.

To quote myself, I just posted the following recommendation
to someone else:

Deborah Kurata has a book coming out in January called "Doing Objects
in VB2005". It explains the GUIDS methodology for analysis and
design, and then shows you explicitly how to set up your 3 layers.
You end up writing an entire application. I found the book clear
and concise, and a lot easier than reading an entire book on theory.
It also had a lot of neat things in it about saving your project
settings, code snippets, and bet of all, binding your data to objects.

Rockford Lhotka also has some business objects books that are
supposed to be definitive.

Robin S.
--------------------------------
"Brad Pears" <do********@notreal.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

>I am completely new to vb .net. I am using visual Studio 2005 to redo an
Access 2000 application into a .net OO application using SQL Server 2000 -
so a complete rewrite and re-thinking of how this app will work.

I have NEVER done any OO programming at all although I have used OO
techniques in programs of course - just never actually designed the
classes etc...

So I am just a tad nervous in re-writing this Access application as it is
a large app and I am learning so many new things I have never used before
such as vb.net, OO design, SQL server and Crystal!!! It is a little mind
boggling to be doing a big project using all this new stuff!!!

Right now I figured the best place to start was to look at the existing
application and try to extract from that what some of my classes will be
for the new app and then add new classes. Then from that I can determine
the data required and methods for each class - which will then lead to the
physical SQL Server db design to facilitate my class design. The physical
db will be WAY different than the old Access 2000 design.

I guess I am looking for a little guidance from those who work in this all
the time. Am I doing this in the right order basically ?

I am also looking for a really god book on OO design principals - leaning
towards vb.net would be good but the principals are all the same so just
an overall OO design book would be good.

Does any one know of a good one - or some really good reference material
for this on the internet? I am unsure of things like how many classes do
I really need to mimic a parent child relationship for instance. The
parent would be one class and the children would be yet another class -
but would it be a subclass of the parent etc.. etc.. Figuring out how
many classes and their relationships - when to create new classes or
include all the data in one class is what I am having a hard time with.
(when to subclass and when not to...)

Any help at all would be most appreciated!!!

Thanks, Brad

How did you manage to see this book ahead of time?? Any chance of getting it
early?? I am starting this now and would be nice to have a good reference
handy...

Thanks for the help.
"RobinS" <Ro****@NoSpam.yah.nonewrote in message
news:p8******************************@comcast.com. ..

You should design the data structures first, which leads
to your business layer classes, and then the UI.

To quote myself, I just posted the following recommendation
to someone else:

Deborah Kurata has a book coming out in January called "Doing Objects
in VB2005". It explains the GUIDS methodology for analysis and
design, and then shows you explicitly how to set up your 3 layers.
You end up writing an entire application. I found the book clear
and concise, and a lot easier than reading an entire book on theory.
It also had a lot of neat things in it about saving your project
settings, code snippets, and bet of all, binding your data to objects.

Rockford Lhotka also has some business objects books that are
supposed to be definitive.

Robin S.
--------------------------------
"Brad Pears" <do********@notreal.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

>>I am completely new to vb .net. I am using visual Studio 2005 to redo an
Access 2000 application into a .net OO application using SQL Server
2000 - so a complete rewrite and re-thinking of how this app will work.

I have NEVER done any OO programming at all although I have used OO
techniques in programs of course - just never actually designed the
classes etc...

So I am just a tad nervous in re-writing this Access application as it is
a large app and I am learning so many new things I have never used before
such as vb.net, OO design, SQL server and Crystal!!! It is a little mind
boggling to be doing a big project using all this new stuff!!!

Right now I figured the best place to start was to look at the existing
application and try to extract from that what some of my classes will be
for the new app and then add new classes. Then from that I can determine
the data required and methods for each class - which will then lead to
the physical SQL Server db design to facilitate my class design. The
physical db will be WAY different than the old Access 2000 design.

I guess I am looking for a little guidance from those who work in this
all the time. Am I doing this in the right order basically ?

I am also looking for a really god book on OO design principals - leaning
towards vb.net would be good but the principals are all the same so just
an overall OO design book would be good.

Does any one know of a good one - or some really good reference material
for this on the internet? I am unsure of things like how many classes do
I really need to mimic a parent child relationship for instance. The
parent would be one class and the children would be yet another class -
but would it be a subclass of the parent etc.. etc.. Figuring out how
many classes and their relationships - when to create new classes or
include all the data in one class is what I am having a hard time with.
(when to subclass and when not to...)

Any help at all would be most appreciated!!!

Thanks, Brad

I knew Deborah because she''s the head of my local .Net User Group.
I had some extra time, and knew she was working on her book, so
I offered to read it for content and work through all the example
work. It was a great opportunity for both of us. :-D So I''m
sorry, but it''s not going to be available until January. It
does sound like exactly what you need. It really brought everything
together for me, and was the foundation for me making the jump from
VB6 to VB.Net. It explained classes and inheritance and objects.
Reading it made it easier for me to understand everything else
I read after that.

On the bright side, January is not very far away?

If you''re desperate, you could check out her VB6 for Objects book;
it''s available on amazon for like 67 cents. It''s in the wrong
version of the language, but you''d get the general idea. That
version has a lot more information on the analysis/design stage,
from what I understand.

If I hear anything about it coming out sooner, or if I can
get my hands on an advance copy, I''ll let you know next week.

Robin S.
--------------------------

"Brad Pears" <do********@notreal.comwrote in message
news:uB**************@TK2MSFTNGP06.phx.gbl...

How did you manage to see this book ahead of time?? Any chance of getting
it early?? I am starting this now and would be nice to have a good
reference handy...

Thanks for the help.
"RobinS" <Ro****@NoSpam.yah.nonewrote in message
news:p8******************************@comcast.com. ..

>You should design the data structures first, which leads
to your business layer classes, and then the UI.

To quote myself, I just posted the following recommendation
to someone else:

Deborah Kurata has a book coming out in January called "Doing Objects
in VB2005". It explains the GUIDS methodology for analysis and
design, and then shows you explicitly how to set up your 3 layers.
You end up writing an entire application. I found the book clear
and concise, and a lot easier than reading an entire book on theory.
It also had a lot of neat things in it about saving your project
settings, code snippets, and bet of all, binding your data to objects.

Rockford Lhotka also has some business objects books that are
supposed to be definitive.

Robin S.
--------------------------------
"Brad Pears" <do********@notreal.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

>>>I am completely new to vb .net. I am using visual Studio 2005 to redo an
Access 2000 application into a .net OO application using SQL Server
2000 - so a complete rewrite and re-thinking of how this app will work.

I have NEVER done any OO programming at all although I have used OO
techniques in programs of course - just never actually designed the
classes etc...

So I am just a tad nervous in re-writing this Access application as it
is a large app and I am learning so many new things I have never used
before such as vb.net, OO design, SQL server and Crystal!!! It is a
little mind boggling to be doing a big project using all this new
stuff!!!

Right now I figured the best place to start was to look at the existing
application and try to extract from that what some of my classes will be
for the new app and then add new classes. Then from that I can determine
the data required and methods for each class - which will then lead to
the physical SQL Server db design to facilitate my class design. The
physical db will be WAY different than the old Access 2000 design.

I guess I am looking for a little guidance from those who work in this
all the time. Am I doing this in the right order basically ?

I am also looking for a really god book on OO design principals -
leaning towards vb.net would be good but the principals are all the same
so just an overall OO design book would be good.

Does any one know of a good one - or some really good reference material
for this on the internet? I am unsure of things like how many classes
do I really need to mimic a parent child relationship for instance. The
parent would be one class and the children would be yet another class -
but would it be a subclass of the parent etc.. etc.. Figuring out how
many classes and their relationships - when to create new classes or
include all the data in one class is what I am having a hard time with.
(when to subclass and when not to...)

Any help at all would be most appreciated!!!

Thanks, Brad

这篇关于OO设计和编程......的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！