| Groups | Blog | Home |
dotnet ado.net : One DataTable class in two datasets - design-time support
Hi, I created two datasets in dataset designer in VS 2005. Both of them
contain the same datatable. I think, having two classes for one DB datatable is stupid and badly maintaining. So I need manually add DataTable class from first dataset to second. So I modified designer.cs of second dataset and I added datatable from first dataset: I added this code to InitClass() method of second Dataset: this.UCET = new ageu.DataLayer.dsFakturace.UCETDataTable(); base.Tables.Add(this.UCET); Ucet is DB table, which I need in both datasets. dsFakturace is first dataset. This is working solution, design -time databinding is working. But, designer sometimes regenerate designer.cs and my changes are lost. Is there any better approach to do this? Thank you.
You should never change the designer code, because when it gets
regenerated, you lose your changes. As you've found. Can't you just add the first datatable to the second dataset? Can you copy and paste it, or (better yet) just recreate the dataset with the two tables in it? Seems like that would take less time than you've already spent on it. Robin S. -------------------------- [quoted text, click to view] "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message news:ugOFWfRRHHA.3412@TK2MSFTNGP05.phx.gbl... > Hi, I created two datasets in dataset designer in VS 2005. Both of them > contain the same datatable. I think, having two classes for one DB > datatable is stupid and badly maintaining. So I need manually add > DataTable class from first dataset to second. So I modified designer.cs > of second dataset and I added datatable from first dataset: > I added this code to InitClass() method of second Dataset: > this.UCET = new ageu.DataLayer.dsFakturace.UCETDataTable(); > base.Tables.Add(this.UCET); > > Ucet is DB table, which I need in both datasets. dsFakturace is first > dataset. This is working solution, design -time databinding is working. > But, designer sometimes regenerate designer.cs and my changes are lost. > Is there any better approach to do this? > > Thank you. > >
I guess I don't understand your problem. I thought you said you have two
strongly typed datasets, each with one table, and you wanted to combine them. So do you want to combine them at run time rather than at design time? Is that the point? And I'll repeat this: you should never change the designer code, because if it gets regenerated, your changes will be lost. If the designer code is a partial class, you can probably *add* to it by adding another class to your project and declaring it a partial class with the same name. This will not be wiped out if the designer code is regerated, and will be considered part of the same class. If I'm completely offbase, please post more information. Robin S. Ts'i mahnu uterna ot twan ot geifur hingts uto. ------------------------------------------- [quoted text, click to view] "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message news:%23PBeaPgRHHA.1228@TK2MSFTNGP06.phx.gbl... > No, why should I have one datatable 2 times (or more) in code??? I need > add other methods to this datatable, so in your approach I need write > this methods twice! (or more). And any change (and bug repair) I have to > do on two places! This is the worstest approch I could choose.... > > "RobinS" <RobinS@NoSpam.yah.none> pí¹e v diskusním pøíspìvku > news:n5GdnQyNDJRFe13YnZ2dnUVZ_tGsnZ2d@comcast.com... >> You should never change the designer code, because when it gets >> regenerated, you lose your changes. As you've found. >> >> Can't you just add the first datatable to the second dataset? Can you >> copy and paste it, or (better yet) just recreate the dataset with the >> two tables in it? Seems like that would take less time than you've >> already spent on it. >> >> Robin S. >> -------------------------- >> "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message >> news:ugOFWfRRHHA.3412@TK2MSFTNGP05.phx.gbl... >>> Hi, I created two datasets in dataset designer in VS 2005. Both of them >>> contain the same datatable. I think, having two classes for one DB >>> datatable is stupid and badly maintaining. So I need manually add >>> DataTable class from first dataset to second. So I modified designer.cs >>> of second dataset and I added datatable from first dataset: >>> I added this code to InitClass() method of second Dataset: >>> this.UCET = new ageu.DataLayer.dsFakturace.UCETDataTable(); >>> base.Tables.Add(this.UCET); >>> >>> Ucet is DB table, which I need in both datasets. dsFakturace is first >>> dataset. This is working solution, design -time databinding is working. >>> But, designer sometimes regenerate designer.cs and my changes are lost. >>> Is there any better approach to do this? >>> >>> Thank you. >>> >>> >> >> > >
No, why should I have one datatable 2 times (or more) in code??? I need add
other methods to this datatable, so in your approach I need write this methods twice! (or more). And any change (and bug repair) I have to do on two places! This is the worstest approch I could choose.... "RobinS" <RobinS@NoSpam.yah.none> pí¹e v diskusním pøíspìvku news:n5GdnQyNDJRFe13YnZ2dnUVZ_tGsnZ2d@comcast.com... [quoted text, click to view] > You should never change the designer code, because when it gets > regenerated, you lose your changes. As you've found. > > Can't you just add the first datatable to the second dataset? Can you copy > and paste it, or (better yet) just recreate the dataset with the two > tables in it? Seems like that would take less time than you've already > spent on it. > > Robin S. > -------------------------- > "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message > news:ugOFWfRRHHA.3412@TK2MSFTNGP05.phx.gbl... >> Hi, I created two datasets in dataset designer in VS 2005. Both of them >> contain the same datatable. I think, having two classes for one DB >> datatable is stupid and badly maintaining. So I need manually add >> DataTable class from first dataset to second. So I modified designer.cs >> of second dataset and I added datatable from first dataset: >> I added this code to InitClass() method of second Dataset: >> this.UCET = new ageu.DataLayer.dsFakturace.UCETDataTable(); >> base.Tables.Add(this.UCET); >> >> Ucet is DB table, which I need in both datasets. dsFakturace is first >> dataset. This is working solution, design -time databinding is working. >> But, designer sometimes regenerate designer.cs and my changes are lost. >> Is there any better approach to do this? >> >> Thank you. >> >> > >
Hi,
I have in my database datatable called for example employee. I have two dataset classes (two xsd schema files), where are some tables (dataset are differents) and I need in both of them employee datatable. Easiest way is to drag and drop this datatable from server explorer to both datasets, but in this case I will have this datatable in my code twice. So if I add some methods to employee datatable in first dataset, then I have to add the same code to employee datatable in second dataset....Is this clear? Now imagine situation, I have 10 datasets (which are completely different)...and I need in all of them my employee datatable, so If I add one method to first's dataset employee datatable, I have to copy and paste this code to next nine employee datatable classes... "RobinS" <RobinS@NoSpam.yah.none> pí¹e v diskusním pøíspìvku news:VYmdnb4YVODHuF_YnZ2dnUVZ_oupnZ2d@comcast.com... [quoted text, click to view] >I guess I don't understand your problem. I thought you said you have two >strongly typed datasets, each with one table, and you wanted to combine >them. > > So do you want to combine them at run time rather than at design time? Is > that the point? > > And I'll repeat this: you should never change the designer code, because > if it gets regenerated, your changes will be lost. > > If the designer code is a partial class, you can probably *add* to it by > adding another class to your project and declaring it a partial class with > the same name. This will not be wiped out if the designer code is > regerated, and will be considered part of the same class. > > If I'm completely offbase, please post more information. > > Robin S. > Ts'i mahnu uterna ot twan ot geifur hingts uto. > ------------------------------------------- > "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message > news:%23PBeaPgRHHA.1228@TK2MSFTNGP06.phx.gbl... >> No, why should I have one datatable 2 times (or more) in code??? I need >> add other methods to this datatable, so in your approach I need write >> this methods twice! (or more). And any change (and bug repair) I have to >> do on two places! This is the worstest approch I could choose.... >> >> "RobinS" <RobinS@NoSpam.yah.none> pí¹e v diskusním pøíspìvku >> news:n5GdnQyNDJRFe13YnZ2dnUVZ_tGsnZ2d@comcast.com... >>> You should never change the designer code, because when it gets >>> regenerated, you lose your changes. As you've found. >>> >>> Can't you just add the first datatable to the second dataset? Can you >>> copy and paste it, or (better yet) just recreate the dataset with the >>> two tables in it? Seems like that would take less time than you've >>> already spent on it. >>> >>> Robin S. >>> -------------------------- >>> "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message >>> news:ugOFWfRRHHA.3412@TK2MSFTNGP05.phx.gbl... >>>> Hi, I created two datasets in dataset designer in VS 2005. Both of them >>>> contain the same datatable. I think, having two classes for one DB >>>> datatable is stupid and badly maintaining. So I need manually add >>>> DataTable class from first dataset to second. So I modified designer.cs >>>> of second dataset and I added datatable from first dataset: >>>> I added this code to InitClass() method of second Dataset: >>>> this.UCET = new ageu.DataLayer.dsFakturace.UCETDataTable(); >>>> base.Tables.Add(this.UCET); >>>> >>>> Ucet is DB table, which I need in both datasets. dsFakturace is first >>>> dataset. This is working solution, design -time databinding is working. >>>> But, designer sometimes regenerate designer.cs and my changes are lost. >>>> Is there any better approach to do this? >>>> >>>> Thank you. >>>> >>>> >>> >>> >> >> > >
I do understand what you're saying, and there's no easy way to do what
you're talking about. Maybe you could create the strongly typed datasets yourself manually and not in the designer, and add in the code for the second datatable yourself into each dataset. I was talking to a Microsoft MVP last week about strongly typed datasets versus business objects. She said she uses the datasets, but they generate their own (Dave Sceppa explains it in his book, has something to do with XML; if you can't find anything in MSDN or Google, post back and I'll see if I can post some info about it) and then they remove the table adapter, because they use all stored procs to do the updates. Presumably if that was possible, then you could automate that (as she has) and then add in the code for the datatable. Sure, it would be replicated, but if it was in an automated procedure, who cares? If you need more info, post back, and I'll track her down and ask her more q's about this. I probably won't be able to get an answer from her until next week though, just FYI. Robin S. Ts'i mahnu uterna ot twan ot geifur hingts uto. ----------------------------------------------- [quoted text, click to view] "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message news:uWXs0BqRHHA.2256@TK2MSFTNGP02.phx.gbl... > Hi, > I have in my database datatable called for example employee. I have two > dataset classes (two xsd schema files), where are some tables (dataset > are differents) and I need in both of them employee datatable. Easiest > way is to drag and drop this datatable from server explorer to both > datasets, but in this case I will have this datatable in my code twice. > So if I add some methods to employee datatable in first dataset, then I > have to add the same code to employee datatable in second dataset....Is > this clear? > Now imagine situation, I have 10 datasets (which are completely > different)...and I need in all of them my employee datatable, so If I add > one method to first's dataset employee datatable, I have to copy and > paste this code to next nine employee datatable classes... > > "RobinS" <RobinS@NoSpam.yah.none> pí¹e v diskusním pøíspìvku > news:VYmdnb4YVODHuF_YnZ2dnUVZ_oupnZ2d@comcast.com... >>I guess I don't understand your problem. I thought you said you have two >>strongly typed datasets, each with one table, and you wanted to combine >>them. >> >> So do you want to combine them at run time rather than at design time? >> Is that the point? >> >> And I'll repeat this: you should never change the designer code, because >> if it gets regenerated, your changes will be lost. >> >> If the designer code is a partial class, you can probably *add* to it by >> adding another class to your project and declaring it a partial class >> with the same name. This will not be wiped out if the designer code is >> regerated, and will be considered part of the same class. >> >> If I'm completely offbase, please post more information. >> >> Robin S. >> Ts'i mahnu uterna ot twan ot geifur hingts uto. >> ------------------------------------------- >> "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message >> news:%23PBeaPgRHHA.1228@TK2MSFTNGP06.phx.gbl... >>> No, why should I have one datatable 2 times (or more) in code??? I need >>> add other methods to this datatable, so in your approach I need write >>> this methods twice! (or more). And any change (and bug repair) I have >>> to do on two places! This is the worstest approch I could choose.... >>> >>> "RobinS" <RobinS@NoSpam.yah.none> pí¹e v diskusním pøíspìvku >>> news:n5GdnQyNDJRFe13YnZ2dnUVZ_tGsnZ2d@comcast.com... >>>> You should never change the designer code, because when it gets >>>> regenerated, you lose your changes. As you've found. >>>> >>>> Can't you just add the first datatable to the second dataset? Can you >>>> copy and paste it, or (better yet) just recreate the dataset with the >>>> two tables in it? Seems like that would take less time than you've >>>> already spent on it. >>>> >>>> Robin S. >>>> -------------------------- >>>> "Jiøí Neu¾il" <meuzil@seznam.cz> wrote in message >>>> news:ugOFWfRRHHA.3412@TK2MSFTNGP05.phx.gbl... >>>>> Hi, I created two datasets in dataset designer in VS 2005. Both of >>>>> them contain the same datatable. I think, having two classes for one >>>>> DB datatable is stupid and badly maintaining. So I need manually add >>>>> DataTable class from first dataset to second. So I modified >>>>> designer.cs of second dataset and I added datatable from first >>>>> dataset: >>>>> I added this code to InitClass() method of second Dataset: >>>>> this.UCET = new ageu.DataLayer.dsFakturace.UCETDataTable(); >>>>> base.Tables.Add(this.UCET); >>>>> >>>>> Ucet is DB table, which I need in both datasets. dsFakturace is first >>>>> dataset. This is working solution, design -time databinding is >>>>> working. But, designer sometimes regenerate designer.cs and my >>>>> changes are lost. Is there any better approach to do this? >>>>> >>>>> Thank you. >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
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 |