Important question about .NET 2.0 datasets...

[Dave]

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/microsoft.public.dotnet.framework.adon...



http://groups.google.com/group/microsoft.public.dotnet.framework.adon...



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

 

[Lebesgue]

How about trying your code that was broken in .NET 1.1 and telling us if
it's working in 2.0?

 

[Nicholas Paldino [.NET/C# MVP]]

This isn't the first time that you have posted this. You should compile
the code in .NET 2.0 and just see if it has been fixed.

If not, then file the bug at the Product Feedback Center so that they
know it exists (unless it is filed there already). If it is not there, then
it is not in their bug tracking system.

 

[Dave]

Hey Nicholas,

Yes, this is my 2nd post... Our product is in a state where there are
many hacks in place to prevent these bugs from happening. For example,
removing and re-adding DataSet relations before and after Inserts and
Updates seems to fix many of the problems (among other hacks)... It
would take a significant amount of work in order for us to eventually
find out if this was fixed or not. I'm simply trying to see if other
developers have come across this or not, as some initial "due
dillegence".

This bug is already in thier bug tracking system for 1.1.

Tx,
Dave

This isn't the first time that you have posted this. You should compile
the code in .NET 2.0 and just see if it has been fixed.

If not, then file the bug at the Product Feedback Center so that they
know it exists (unless it is filed there already). If it is not there, then
it is not in their bug tracking system.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

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/microsoft.public.dotnet.framework.adon...



http://groups.google.com/group/microsoft.public.dotnet.framework.adon...



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