业务对象与数据集 [英] business objects vs. datasets
问题描述
你好，
我正在非常严肃的.net重新设计/重写一个旧的VB6
应用程序。
我被要求制作.NET 2.0，并想询问几个关于数据访问的问题，因为这个应用程序是以数据为中心的
围绕MSDE数据库。
使用自定义业务对象或为我的类扩展
数据集/数据表会更好吗？
这就是我在想的，只是想知道它是否正确。
自定义总线。对象：
- 开发/测试它的时间更长。
- 与DataLayer松散耦合。
- 可扩展。
数据集
- 更快/更容易。
- 与DataLayer紧密结合。
我是害怕微软正在放弃ADO.NET并推动WPF / Linq
计划，并且不想在2 - 3年内重写业务层，以便
调整它目前的框架。
想听听你的意见和经验...
谢谢......
嗨Penelope Dramas，
如果你想用Business Objects重写它，那就有新书了
$ b $下个月由Deborah Kurata（微软MVP）出来，它确切地说明了如何做到这一点。我读了它，并且正在使用这种方法。它被称为在VB2005中执行
对象。
您可以采用任何一种方式。我认为用商业
对象来做这件事比较困难，但数据访问更严格，因为你可以更好地控制
吧。
然而我知道另一个MVP领导一个大型项目，他使用强大的
类型数据集。她的设计仍然是3层，但她的数据层
传回强类型数据集，以便在UI中使用。
她自己生成数据集从存储过程中删除表适配器的
因为它们*仅*使用存储过程。我不是很好的确定她是怎么做到的，这是我想跟进的事情
找出来的。
所以我没有给你一个确定的答案，但也许这个信息
会有所帮助。其他人一定会有意见，我很肯定。
肯定。
Robin S.
Ts''i mahnu uterna ot twan ot geifur hingts uto。
---------------------------------- -------------
Penelope Dramas < penelopeDOTdramasATpro-transportDOTcomwrote in message
news：eB ************** @ TK2MSFTNGP05.phx.gbl ...
您好，
我正在非常严肃的.net重新设计/重写旧的VB6
应用程序。
我被要求制作.NET 2.0，并想询问几个关于数据访问的问题，因为这个应用程序非常重要
围绕MSDE数据库以数据为中心。
使用自定义业务对象或为我的类扩展
数据集/数据表会更好吗？ br />
这就是我在想的，只是想知道它是否正确。
自定义总线。对象：
- 开发/测试它的时间更长。
- 与DataLayer松散耦合。
- 可扩展。
数据集
- 更快/更容易。
- 与DataLayer紧密结合。
我是害怕微软正在放弃ADO.NET并推动WPF / Linq
计划并且不想在2 - 3年内重写业务层
来调整它目前的框架。
想听听你的意见和经验...
谢谢......
Penelope Dramas < penelopeDOTdramasATpro-transportDOTcomwrote in
news：eB ************** @ TK2MSFTNGP05.phx.gbl：
自定义巴士。对象：
- 开发/测试它的时间更长。
- 与DataLayer松散耦合。
- 可扩展。
数据集
- 更快/更容易。
- 与DataLayer紧密结合。
看看LLBLGen。 LLBLGen Pro是第三方DAL，非常好用于自动生成自定义业务对象的
。
LLBLGen Pro的开发人员计划将其设为LINQ兼容性。
所以从某种意义上说，你现在可以获得LINQ的功能了 - 以及未来的linq
的兼容性！
到这里
http://sholliday.spaces.live.com/blog/
6/5/2006
Custom对象和分层开发II // 2.0
和
5/24/2006
自定义对象/集合和分层开发
然而第二个是1.1。
运行一段时间以查看填充定制业务之间的区别
带有IDataReader的对象与填充强大的DataSet。
你会感到惊讶。
我在底部提到了MS KB 1.1文章鸟瞰图。多次阅读
那个东西。
在我需要保养的系统上，我99％的时间都在使用自定义对象。
在报告中，我回到强大的数据集。
Penelope Dramas < penelopeDOTdramasATpro-transportDOTcomwrote in message
news：eB ************** @ TK2MSFTNGP05.phx.gbl ...
您好，
我正在非常严肃的.net重新设计/重写旧的VB6
应用程序。
我被要求制作.NET 2.0，并想询问几个关于数据访问的问题，因为这个应用程序很多是
以数据为中心
围绕MSDE数据库。
是不是更好地使用自定义业务对象或为我的类扩展
数据集/数据表？
这就是我在想的，只是想知道它是否是这是正确的方法。
自定义巴士。对象：
- 开发/测试它的时间更长。
- 与DataLayer松散耦合。
- 可扩展。
数据集
- 更快/更容易。
- 与DataLayer紧密结合。
我是害怕微软正在放弃ADO.NET并推动WPF / Linq
计划并且不想在2 - 3年内重写业务层
到
将其调整为当前框架。
想听听您的意见和经验.. 。
谢谢......
Hello,
I''m in a front of very serious .net redesign/rewrite of an old VB6
application.
I had been asked to make it .NET 2.0 and would like to ask couple of
questions regarding data access as this application is heavily data-centric
around MSDE database.
Would it be better to use custom business objects or extend
datasets/datatables for my classes?
This is what I''m thinking and just wanted to know if it''s correct way.
Custom Bus. Object:
- Longer time to develop/test it.
- Loosely coupled with DataLayer.
- Extensible.
Datasets
- Faster/Easier.
- Tightly coupled with DataLayer.
I''m afraid that Microsoft is dropping ADO.NET and pushing WPF/Linq
initiative and don''t want to end up rewriting business layer in 2-3 years to
adjust it to current framework.
Would like to hear your opinion and experiences...
Thanks ...
Hi Penelope Dramas,
If you want to rewrite it using Business Objects, there''s a new book coming
out next month by Deborah Kurata (Microsoft MVP) that shows exactly how to
do that. I read it, and am using that methodology. It''s called "Doing
Objects in VB2005".
You can kind of go either way. I think it''s harder to do it with business
objects, but the data access is tighter because you have more control over
it.
And yet I know of another MVP leading a large project who uses strongly
typed datasets. She still has her design in 3-layers, but her data layer
passes back strongly typed datasets for use in the UI.
She generates the datasets herself from the stored procedures and removes
the table adapter because they *only* use stored procedures. I''m not
exactly certain how she does that, it''s something I want to follow up on to
find out.
So I don''t have a definitive answer for you, but maybe this information
will help in some way. Other people will definitely have an opinion, I''m
sure.
Robin S.
Ts''i mahnu uterna ot twan ot geifur hingts uto.
-----------------------------------------------
"Penelope Dramas" <penelopeDOTdramasATpro-transportDOTcomwrote in message
news:eB**************@TK2MSFTNGP05.phx.gbl...Hello,
I''m in a front of very serious .net redesign/rewrite of an old VB6
application.
I had been asked to make it .NET 2.0 and would like to ask couple of
questions regarding data access as this application is heavily
data-centric around MSDE database.
Would it be better to use custom business objects or extend
datasets/datatables for my classes?
This is what I''m thinking and just wanted to know if it''s correct way.
Custom Bus. Object:
- Longer time to develop/test it.
- Loosely coupled with DataLayer.
- Extensible.
Datasets
- Faster/Easier.
- Tightly coupled with DataLayer.
I''m afraid that Microsoft is dropping ADO.NET and pushing WPF/Linq
initiative and don''t want to end up rewriting business layer in 2-3 years
to adjust it to current framework.
Would like to hear your opinion and experiences...
Thanks ...
"Penelope Dramas" <penelopeDOTdramasATpro-transportDOTcomwrote in
news:eB**************@TK2MSFTNGP05.phx.gbl:
Custom Bus. Object:
- Longer time to develop/test it.
- Loosely coupled with DataLayer.
- Extensible.
Datasets
- Faster/Easier.
- Tightly coupled with DataLayer.Take a look at LLBLGen. LLBLGen Pro is a third party DAL which is very good
at auto-generating custom business objects.
The developer of LLBLGen Pro is planning to make it LINQ compatible too.
So in a sense, you get the feature of LINQ now - and with future linq
compatibility!
Go here
http://sholliday.spaces.live.com/blog/
6/5/2006
Custom Objects and Tiered Development II // 2.0
and
5/24/2006
Custom Objects/Collections and Tiered Development
The second one is 1.1, however.
Run some times to see the difference between populating your custom business
objects with an IDataReader vs populating strong DataSets.
You ~~will be surprised.
I mention a MS KB at the bottom on the 1.1 article "bird''s eye view". Read
that thing several times.
On a system I need to upkeep, I 99% of the time go with Custom Objects now.
On reports, I go back to strong datasets.
"Penelope Dramas" <penelopeDOTdramasATpro-transportDOTcomwrote in message
news:eB**************@TK2MSFTNGP05.phx.gbl...Hello,
I''m in a front of very serious .net redesign/rewrite of an old VB6
application.
I had been asked to make it .NET 2.0 and would like to ask couple of
questions regarding data access as this application is heavilydata-centric
around MSDE database.
Would it be better to use custom business objects or extend
datasets/datatables for my classes?
This is what I''m thinking and just wanted to know if it''s correct way.
Custom Bus. Object:
- Longer time to develop/test it.
- Loosely coupled with DataLayer.
- Extensible.
Datasets
- Faster/Easier.
- Tightly coupled with DataLayer.
I''m afraid that Microsoft is dropping ADO.NET and pushing WPF/Linq
initiative and don''t want to end up rewriting business layer in 2-3 yearsto
adjust it to current framework.
Would like to hear your opinion and experiences...
Thanks ...
这篇关于业务对象与数据集的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
