By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,997 Members | 1,098 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,997 IT Pros & Developers. It's quick & easy.

Important question about .NET 2.0 DataSets

P: n/a
We've created a robust client server application over the past 3 years
on the .NET framework version 1.1 using c#. We layed all of our
marbles in creating strongly typed datasets and for the most part we
are extremely happy we did that.

However, there's an incredibly huge bug (in my opinion) that has cost
us probably on the order of at least 40 hours of development time in
tracking down this bug and doing several small scale re-writes. I
don't even know the name of the bug, but it shows itself if you meet
the following requirements:
- Use Datasets
- Use DataRelations
- Use Expression columns

The bug occurs when you perform database Inserts and Updates on tables
that use expression columns and have datarelations. There is an
exception that get's thrown from within the .NET framework... there
have been many posts about it, but unless you meet all the requirements
above, you may not even know this bug exists. It's been a while, so i
don't remember what the specific Exception was...

Here's some people who have the same problem...
http://groups.google.com/group/micro...57513ff901e513

http://groups.google.com/group/micro...f5c420d084d62d

Microsoft has acknowledged this as a bug.

We waited and waited 2+ years for a fix for this and I'm absolutely
amazed that it was never addressed. My only guess is that it was too
big of a re-write and they decided to wait until 2.0 to fix it (I
hope). I'm amazed because of how much Microsoft want's everyone in the
world to switch to .NET and Datasets lie at the heart of the .NET
codebase.

Anyway my question is, does anybody know if this is fixed in .NET 2.0?

Thanks,
Dave

May 11 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Dave,

Have you tried it in .NET 2.0? If you already have your codebase in
place, what is preventing you from compiling it in .NET 2.0 and then trying
it to see if it works or not?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Dave" <ch********@yahoo.com> wrote in message
news:11**********************@q12g2000cwa.googlegr oups.com...
We've created a robust client server application over the past 3 years
on the .NET framework version 1.1 using c#. We layed all of our
marbles in creating strongly typed datasets and for the most part we
are extremely happy we did that.

However, there's an incredibly huge bug (in my opinion) that has cost
us probably on the order of at least 40 hours of development time in
tracking down this bug and doing several small scale re-writes. I
don't even know the name of the bug, but it shows itself if you meet
the following requirements:
- Use Datasets
- Use DataRelations
- Use Expression columns

The bug occurs when you perform database Inserts and Updates on tables
that use expression columns and have datarelations. There is an
exception that get's thrown from within the .NET framework... there
have been many posts about it, but unless you meet all the requirements
above, you may not even know this bug exists. It's been a while, so i
don't remember what the specific Exception was...

Here's some people who have the same problem...
http://groups.google.com/group/micro...57513ff901e513

http://groups.google.com/group/micro...f5c420d084d62d

Microsoft has acknowledged this as a bug.

We waited and waited 2+ years for a fix for this and I'm absolutely
amazed that it was never addressed. My only guess is that it was too
big of a re-write and they decided to wait until 2.0 to fix it (I
hope). I'm amazed because of how much Microsoft want's everyone in the
world to switch to .NET and Datasets lie at the heart of the .NET
codebase.

Anyway my question is, does anybody know if this is fixed in .NET 2.0?

Thanks,
Dave

May 11 '06 #2

P: n/a
No I have not... I'm just curious if this issue has been addressed or
not. Does anybody have any insight on this issue?

Thanks,
Dave

May 16 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.