Search

Can not specify reference data types in dataset designer by tpelletier

Closed
as Postponed Help for as Postponed

13
Sign in to vote
0
Sign in to vote
Sign in
to vote
Type: Bug
ID: 93616
Opened: 7/19/2005 11:14:01 AM
Access Restriction: Public
0
Workaround(s)
9
User(s) can reproduce this bug
My organization has a scenario where we need to have the datatype of a column in a dataset be of type 'System.Data.DataSet'. To give some background, we use the dataset to hold the state of our domain entities. Each entity is backed by a dataset. We organize them hierarchically by linking the datasets together at a column level (Account dataset has a Contacts row that holds a Contacts dataset). If you need more background please contact me.

This is a very crucial scenario for our entity framework and currently, even though the dataset designer allows for that datatype to be specified, the other critical properties like NullValue, DefaultValue, etc. can not be set in a way that makes sense for that datatype. When attempted we receive the exception:
"For columns not defined as System.String, the only valid value is (Throw exception). "

Additionally, if we try to set the default value to 'null' we get an error. But it is possible if you use System.String.

In general, if the designer followed the same rules for all reference types that it does for System.String, I think we would be fine.
Details (expand)
Product Language
English
Version
Visual Studio 2005 Beta 2
Category
Data
Subcategory
 
Operating System
Windows XP Professional
Steps to Reproduce
1) Create a new dataset
2) Create a new column in the dataset
3) Manually type in the datatype of 'System.Data.DataSet'
4) Try to change the 'NullValue' to anything but '(Throw Exception)' - error
5) Try to set the DefaultValue property to 'null' - error
Actual Results
Errors.

Forces us to use System.Object which is not strongly typed.

In general, going beyond System.Data.DataSet, it would be nice to be able to sucessfully specify other (possibly even custom) reference datatypes.
Expected Results
I would expect to be able to set the dataset column datatypes to be any datatype that I want. This is critical to our project. Please contact me for any additional details or questions. Thanks!
File Attachments
1 attachments
Sign in to post a comment.
Posted by Microsoft on 7/20/2005 at 5:43 AM
Thanks for reporting this issue, for some reason I am not able to reproduce the problem with the steps provided. If you have any additional information that could help me repro it would be much appreciated.

Can you please provide us with the project/solution in which the problem is occurring and the corresponding repro steps?

Thank you,
Prabhu, VS2005 Product Team
Posted by Microsoft on 7/21/2005 at 12:37 AM
The Microsoft Sub-status is now "Reproduced"

Thanks for the repro project, we have been able to repro this issue and are investigating.

Thank you,
Prabhu, VS2005 Product Team.
Posted by Microsoft on 8/12/2005 at 1:41 PM
The Microsoft Sub-status is now "Working on solution"
Posted by Microsoft on 8/13/2005 at 2:54 PM
Dear Customer,

Thank you for report the issue. Unfortunatly this issue will not be fixed in Whidbey timeframe as we are locked down to fix only critical issues in order to ship the product on time.
I have written a FAQ for you to work around this, See http://blogs.msdn.com/smartclientdata/archive/2005/08/13/NullValueForTypedDataSet.aspx

We will look into it in next version to provide a better user experience on this matter.

JohnChen (VBData dev)
Posted by Microsoft on 10/24/2005 at 7:02 PM
This issue has been reactivated as we begin planning for the next version of Visual Studio. Over the coming months we will reconsider feedback that was previously postponed. We welcome your comments and participation in this process. See http://blogs.msdn.com/productfeedback/archive/2005/10/21/483563.aspx for more information.

-- Visual Studio Team
Posted by Microsoft on 11/9/2005 at 9:42 AM
Hi,
This is something we'll be looking at post Whidbey