Looking for an alternative

  • Thread starter Thread starter Michael Jackson
  • Start date Start date
M

Michael Jackson

Current project is in .NET 2003 using SQL Server 2000. I use strongly typed
datasets in this app, created by dragging a table form Server Explorer to a
design surface, walking thru the SQL Data adapter wizard and generating
Datasets.

The database in the Server Explorer is a db designed and maintained just for
the purpose of generating strongly typed datasets. I also maintain a SQL
Script in one of my projects (generated from the template database) to
create new databases from within my app.

My problem arises when I want to modify the tables in the database. I have
to delete the Dataset, remove the Sql DataAdapter from the design surface,
modify my table, re-drag it back to the design surface and walk thru the
whole process of creating SDA's and Datasets again, and modifying the SQL
script.

Adding a column to a table ends up taking an hour or more.

Is there an alternative, a tool, a utility, etc that can help automate this
or replace it entirely?

NOTE: We will soon be migrating the app to Net 2005 and SQL Server 2005.
Will this problem go away in .NET 2005?

Michael
 
The alternative is to not use the visual studio wizards. I don't like
strongly typed datasets, I don't like using any of the visual studio design
time wizards for this as well as other reasons. You can't write reusable
architecture components to use throughout your project with those - they can
only do 1 set of data at a time for 1 query.

If you take the time to write a data access component that suits your needs,
that can get and update data in a generic manner and integrates well with
the data model of your application, you will be much better off. Then you
can just use your own component every time you need data.

Just my opinion here...
 
Michael,

The approach of the Strongly Typed Dataset from version 2002/2003 is
completely changed from in Version 2005.

In version 2003 I advice you to use a component instead of a form as the
place you drag your wizard (dataadapter) on.

The version 2005 of the Strongly Typed Dataset looks for me more usable and
it looks as well much easier to change. A pity is that there is a different
appraoch between WebTools and Windowforms tools. The strongly typed dataset
will in version 2005 not be generated anymore direct to a class with the
WebTools part of the IDE.

I have however not yet enough expirience to say of it is real usable in
larger projects, what was the Strongly Typed Dataset for me in version
2002/2003 not. However, if that version had been real good, than they would
probably not have changed it.

Just my opinion

Cor
 
I agree with Marina. Don't use strongly typed datasets or the wizards.

I've created an open source component that can help with some of this.
When you modify your table structure, or stored procedure interface
(params, return cols), you only have to update those names in a single
mappings class in your data layer. I have a sample on my web site.

here is the component source code:
http://sourceforge.net/projects/xqs-data/

Here are the samples along with the documentation:
http://www.xquisoft.com/xqsdn/documentation/XQuiSoft.Data.DataManager.html
http://www.xquisoft.com/xqsdn/documentation/XQuiSoft.Data.IDataFactory.html
http://www.xquisoft.com/xqsdn/documentation/index.html (full help index)
 
Back
Top