Introduction
Every Command object has a public CommandTimeout property. A DataAdapter has (up to) four public references to Command objects. Visual Studio 2005 introduced the concept of a TableAdapter, which encapsulates a DataAdapter. The encapsulated DataAdapter is private, and there is no public access to it and its contents.
The result is that you have no access to the Command objects used by the TableAdapter (quite rightly so too). But that allows no access to the CommandTimeout properties!
The code that defines the TableAdapter gets generated automatically (in C#, the file is named xxxDataSet.Designer.cs). Modifying this file is not the solution because any changes to this file will be lost the next time the code is generated.
Solution
.NET V2.0 (or is it just C#?) also introduced "partial classes". The TableAdapter class is a partial class (and you have the source code for it) so you can add any additional functionality to it. Simply create (and include in your project) a file containing whatever code you want to add to the class.
The following code adds public properties for the CommandTimeouts of the Command objects. (Look in your xxxDataSet.Designer.cs file for the name of the class and the namespace for your TableAdapter.)
namespace xxx.xxxDataSetTableAdapters
{
public partial class xxxTableAdapter
{
public int InsertCommandTimeout
{
get
{
return ( this._adapter.InsertCommand.CommandTimeout ) ;
}
set
{
this._adapter.InsertCommand.CommandTimeout = value ;
}
}
public int UpdateCommandTimeout
{
get
{
return ( this._adapter.UpdateCommand.CommandTimeout ) ;
}
set
{
this._adapter.UpdateCommand.CommandTimeout = value ;
}
}
public int DeleteCommandTimeout
{
get
{
return ( this._adapter.DeleteCommand.CommandTimeout ) ;
}
set
{
this._adapter.DeleteCommand.CommandTimeout = value ;
}
}
public int SelectCommandTimeout
{
get
{
return ( this._commandCollection[0].CommandTimeout ) ;
}
set
{
for ( int i = 0 ; i < this._commandCollection.Length ; i++ )
{
if ( ( this._commandCollection [ i ] != null ) )
{
((System.Data.SqlClient.SqlCommand)
(this._commandCollection [ i ])).CommandTimeout = value;
}
}
}
}
}
}
Then you can access them like this:
this.xxxTableAdapter.SelectCommandTimeout = 0 ;
In closing
You can use this technique to add whatever you like to generated partial classes, but be careful what you do!
History
BSCS 1992 Wentworth Institute of Technology
Originally from the Boston (MA) area. Lived in SoCal for a while. Now in the Phoenix (AZ) area.
OpenVMS enthusiast, ISO 8601 evangelist, photographer, opinionated SOB
---------------
"If you need help knowing what to think, let me know and I'll tell you." -- Jeffrey Snover [MSFT]
"Typing is no substitute for thinking." -- R.W. Hamming
"I find it appalling that you can become a programmer with less training than it takes to become a plumber." -- Bjarne Stroustrup
ZagNut’s Law: Arrogance is inversely proportional to ability.
"Well blow me sideways with a plastic marionette. I've just learned something new - and if I could award you a 100 for that post I would. Way to go you keyboard lovegod you." -- Pete O'Hanlon
"linq'ish" sounds like "inept" in German -- Andreas Gieriet
"Things would be different if I ran the zoo." -- Dr. Seuss
"Wrong is evil, and it must be defeated." – Jeff Ello
"A good designer must rely on experience, on precise, logical thinking, and on pedantic exactness." -- Nigel Shaw
"Omit needless local variables." -- Strunk... had he taught programming
"DON'T BE LIBERAL IN WHAT YOU ACCEPT!"
"Software Engineers don't have Trophy Wives; they have Presentation Layers."
"We learn more from our mistakes than we do from getting it right the first time."
"I'm an old dog and I like old tricks."
"Sometimes the envelope pushes back and sometimes you get a really nasty paper cut."
"A method shall have one and only one return statement."
My first rule of debugging: "If you get a different error message, you're making progress."
My golden rule of database management: "Do not unto others' databases as you would not have done unto yours."
My general rule of software development: "Design should be top-down, but implementation should be bottom-up."
"Today's heresy is tomorrow's dogma."
or
"Today's dogma is yesterday's heresy."