Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / May 2008

Tip: Looking for answers? Try searching our database.

MSDataSetGenerator VS2005 vs VS2008 issues

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kyle Jedrusiak - 12 May 2008 18:52 GMT
We have complete strongly typed datasets that were created in VS2005 and as
long as we don't make any changes thay continue to work.

The minute we add a table or coulmn in VS2008, it re-runs the
MSDataSetGenerator which doesn't generate the same set of code.

We lose the IEnumerator interface on all of the tables.

What's going on?

Kyle Jedrusiak
Kyle Jedrusiak - 12 May 2008 19:06 GMT
And the xsd schema from VS2005 is generally not valid in VS2008.

Do we really have to rebuild evey DataSet schema that we need to change?

Kyle Jedrusiak

> We have complete strongly typed datasets that were created in VS2005 and
> as long as we don't make any changes thay continue to work.
[quoted text clipped - 7 lines]
>
> Kyle Jedrusiak
blackdoguh@gmail.com - 30 May 2008 14:30 GMT
Hi Kyle

      I just came across that same problem. I lost some valuable time
since i did not read carefully the error I got:

The type 'MySchemas.SimpleDataset' is defined in an assembly that is
not referenced. You must add a reference to assembly 'MySchemas,
Version=1.0.3072.27689, Culture=neutral, PublicKeyToken=null'.

     Later I noticed that the tables that are part of
MySchemas.SimpleDataset dataset inherit from TypedTableBase class
which is defined as

Namespace:  System.Data
Assembly:  System.Data.DataSetExtensions (in
System.Data.DataSetExtensions.dll)

public abstract class TypedTableBase<T> : DataTable, IEnumerable<T>,
IEnumerable where T : DataRow

     To solve your problems you should reference this assembly
(System.Data.DataSetExtensions.dll) in every project where you use
your custom datasets - that at least worked for my case. I suppose
there are more elaborate ways to solve this problem, but as a fast fix
this could do it.

Regards, Yavor Naumov

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.