| Groups | Blog | Home |
dotnet ado.net : Datatables and TableAdapters in separate files
I've been using the VS 2005 wizards to generate strongly-typed datasets,
datatables, and table adapters for a client/server application. I use the table adapters on the server to connect to the database and retrieve datatables. I then return those datatables to the client. I would really like to have the datatable definitions in one assembly (distributed with the client application) and the tableadapters in another assembly (only needed on the server, has a bunch of code and connection strings). It was fairly easy to split them up manually and compile them into separate assemblies. Of course, once I do that the designer can't handle the tableadapters any more so it makes it very difficult to upgrade and maintain them. It would be nice if the VS designer allowed us to generate them separately so they could be compiled into separate assemblies. Anybody have any thoughts/ideas on this? What is the underlying tool that VS uses to generate table adapters? Perhaps it supports this kind of thing. Joel
Download the Orcas beta. See if their new approach is easier to use.
-- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP INETA Speaker www.betav.com/blog/billva www.betav.com Please reply only to the newsgroup so that others can benefit. This posting is provided "AS IS" with no warranties, and confers no rights. __________________________________ Visit www.hitchhikerguides.net to get more information on my latest book: Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ----------------------------------------------------------------------------------------------------------------------- [quoted text, click to view] "Joel Lyons" <joell_REMOVE_@novarad.net> wrote in message news:OmosvL1vHHA.2352@TK2MSFTNGP03.phx.gbl... > I've been using the VS 2005 wizards to generate strongly-typed datasets, > datatables, and table adapters for a client/server application. I use the > table adapters on the server to connect to the database and retrieve > datatables. I then return those datatables to the client. I would really > like to have the datatable definitions in one assembly (distributed with > the > client application) and the tableadapters in another assembly (only needed > on the server, has a bunch of code and connection strings). > > It was fairly easy to split them up manually and compile them into > separate > assemblies. Of course, once I do that the designer can't handle the > tableadapters any more so it makes it very difficult to upgrade and > maintain > them. > > It would be nice if the VS designer allowed us to generate them separately > so they could be compiled into separate assemblies. > > Anybody have any thoughts/ideas on this? What is the underlying tool that > VS uses to generate table adapters? Perhaps it supports this kind of > thing. > > Joel
Using VS 2005, do the following.
1) Create a separate project 2) Create a new component 3) Drag data adapters onto it - mark each adapter as public 4) Optionally generate a dataset. Now your frontend can reference the dataset and the backend can reference both the dataset and adapter component. This is the way it was done in VS 2003 and is still supported in VS 2005. Your data adapters are separated from the dataset. [quoted text, click to view] "Joel Lyons" <joell_REMOVE_@novarad.net> wrote in message news:OmosvL1vHHA.2352@TK2MSFTNGP03.phx.gbl... > I've been using the VS 2005 wizards to generate strongly-typed datasets, > datatables, and table adapters for a client/server application. I use the > table adapters on the server to connect to the database and retrieve > datatables. I then return those datatables to the client. I would really > like to have the datatable definitions in one assembly (distributed with > the > client application) and the tableadapters in another assembly (only needed > on the server, has a bunch of code and connection strings). > > It was fairly easy to split them up manually and compile them into > separate > assemblies. Of course, once I do that the designer can't handle the > tableadapters any more so it makes it very difficult to upgrade and > maintain > them. > > It would be nice if the VS designer allowed us to generate them separately > so they could be compiled into separate assemblies. > > Anybody have any thoughts/ideas on this? What is the underlying tool that > VS uses to generate table adapters? Perhaps it supports this kind of > thing. > > Joel
I guess I'm not following you Jim. I've created a new project and added a
new component (right click project, "Add", then "Component". I end up with a Component1 class opened in design view. I then try to find "data adapter" in the toolbox to no avail. I then try to drag tables or stored procs from the data connection (in server explorer) onto the design surface and nothing happens. What am I missing? Thanks for your patience. [quoted text, click to view] "Jim Rand" <jimrand@ix.netcom.com> wrote in message
news:uaIjhV9vHHA.4384@TK2MSFTNGP02.phx.gbl... > Using VS 2005, do the following. > > 1) Create a separate project > 2) Create a new component > 3) Drag data adapters onto it - mark each adapter as public > 4) Optionally generate a dataset. > > Now your frontend can reference the dataset and the backend can reference > both the dataset and adapter component. > > This is the way it was done in VS 2003 and is still supported in VS 2005. > Your data adapters are separated from the dataset. > > > "Joel Lyons" <joell_REMOVE_@novarad.net> wrote in message > news:OmosvL1vHHA.2352@TK2MSFTNGP03.phx.gbl... >> I've been using the VS 2005 wizards to generate strongly-typed datasets, >> datatables, and table adapters for a client/server application. I use >> the >> table adapters on the server to connect to the database and retrieve >> datatables. I then return those datatables to the client. I would >> really >> like to have the datatable definitions in one assembly (distributed with >> the >> client application) and the tableadapters in another assembly (only >> needed >> on the server, has a bunch of code and connection strings). >> >> It was fairly easy to split them up manually and compile them into >> separate >> assemblies. Of course, once I do that the designer can't handle the >> tableadapters any more so it makes it very difficult to upgrade and >> maintain >> them. >> >> It would be nice if the VS designer allowed us to generate them >> separately >> so they could be compiled into separate assemblies. >> >> Anybody have any thoughts/ideas on this? What is the underlying tool >> that >> VS uses to generate table adapters? Perhaps it supports this kind of >> thing. >> >> Joel >
Ah, I see!
Thanks Jim [quoted text, click to view] "Jim Rand" <jimrand@ix.netcom.com> wrote in message
news:u2AQlGAwHHA.4592@TK2MSFTNGP05.phx.gbl... > Hi Joel, > > With the component surface open, > > 1) Right click the Data tab of the toolbox > 2) Select "Choose items..." This will open the Choose Toolbox Items > dialog box > 3) On the .NET Framework components, check the SqlDataAdapter and > SqlConnection items. They are in the Namespace System.Data.SqlClient. > 4) Press the OK button. > > Drag the SqlDataAdapter onto your designer and you are on the way. > > Enjoy. > > Jim > > > "Joel Lyons" <joell_REMOVE_@novarad.net> wrote in message > news:e$Txtw%23vHHA.4480@TK2MSFTNGP02.phx.gbl... >>I guess I'm not following you Jim. I've created a new project and added a >>new component (right click project, "Add", then "Component". I end up >>with a Component1 class opened in design view. I then try to find "data >>adapter" in the toolbox to no avail. I then try to drag tables or stored >>procs from the data connection (in server explorer) onto the design >>surface and nothing happens. >> >> What am I missing? Thanks for your patience. >> >
Hi Joel,
With the component surface open, 1) Right click the Data tab of the toolbox 2) Select "Choose items..." This will open the Choose Toolbox Items dialog box 3) On the .NET Framework components, check the SqlDataAdapter and SqlConnection items. They are in the Namespace System.Data.SqlClient. 4) Press the OK button. Drag the SqlDataAdapter onto your designer and you are on the way. Enjoy. Jim [quoted text, click to view] "Joel Lyons" <joell_REMOVE_@novarad.net> wrote in message news:e$Txtw%23vHHA.4480@TK2MSFTNGP02.phx.gbl... >I guess I'm not following you Jim. I've created a new project and added a >new component (right click project, "Add", then "Component". I end up with >a Component1 class opened in design view. I then try to find "data >adapter" in the toolbox to no avail. I then try to drag tables or stored >procs from the data connection (in server explorer) onto the design surface >and nothing happens. > > What am I missing? Thanks for your patience. >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |