Would like to be able to use nullable types with Typed Dataset - by Chris Robinson- MSFT

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


33
1
Sign in
to vote
ID 383175 Comments
Status Closed Workarounds
Type Bug Repros 24
Opened 11/20/2008 11:14:01 AM
Access Restriction Public

Description

I am using typed dataset in my current project.I came to know that currently there is no support for nullable types in typed dataset and visual studio code generator also does not generate nullable types for columns.I would prefer if a primitive datatype like int that allow nulls in database level can be specified as nullable types in typed dataset.

I am reopening a previously closed issue.
Sign in to post a comment.
Posted by Robert Heinig II on 10/24/2011 at 12:33 AM
Let me tell you how this looks to someone who hasn't tried wizard-generated code in Visual Studio since the good old VS6 days: Simply ridiculous. I can only assume that the marketing department actively prevents the dev team from trying to establish some unsability baselines...
Posted by arash ghasemi on 10/30/2010 at 12:22 AM
I 've got VS2010 hoping that this problem is resolved,but it is still resist,this is really an awful bug,
don't know how to fix it
Posted by Belinda H.1 on 10/30/2009 at 12:02 PM
We've got a bunch of applications built around DataSets. There's just no way that we have the resources to rewrite these using e.g. the Entity Framework. It's likely that these apps will be using DataSets for many years to come (some of them will likely never be rewritten).

I'd love to see nullable types supported directly - it would make my life so much easier.
Posted by Microsoft on 12/1/2008 at 2:01 PM
Hello,

Thanks for contacting us regarding nullable types in Typed Dataset. This is a known limitation of the Typed Dataset. Unfortunately, we will not be able to fix this in the next release of Visual Studio.

Please let us know if you have more feedback on Typed Dataset or any other Visual Studio features.

Thanks!

Visual Studio
Posted by David A Nelson on 11/21/2008 at 1:08 PM
The reason that nothing is happening on this issue is that, for better or worse, typed datasets are essentially a deprecated technology (I personally think better, but I understand that people who already have significant investments in them see it differently). Microsoft has already stated that the recommended data access technology for the foreseeable future will be the Entity Framework (essentially deprecating LINQ to SQL). The ADO.NET team is hesitant to go back and put and invest any significant effort in a technology that in their minds has already been replaced.
Posted by Daniel Smith on 11/20/2008 at 2:36 PM
This is obviously the number one request for typed datasets and it's been bugged countless times on Connect, going as far back as 2004.

We really need to push this hard and get things moving. We've done all the right things - posted and voted on bugs on Connect, we've chased this up over the years in the MSDN forums, and we've had PMs do follow up blog posts on the issue promising changes, but we don't seem to get any closer to actually actioning some sort of resolution. What more can we do?
Posted by JasonBoland on 11/20/2008 at 1:22 PM
But how can it be resolved if we are having to do it again?
Posted by Chris Robinson- MSFT on 11/20/2008 at 11:42 AM
The connect bug you talked about is a closed issue and it was directed at orcas. We need something to track this request for .net 4.0
Posted by JasonBoland on 11/20/2008 at 11:29 AM
You should import all the validations from https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=284009 since it's not resolved...