Search

DataRow Access with Column Name Case Sensitive only for boolean by Vasanthadevi Kasirajan

Active

1
0
Sign in
to vote
Type: Bug
ID: 776910
Opened: 1/18/2013 9:29:05 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Example :

the code Convert.ToBoolean(_content["isRelease"] is throwing an exception because the store procedure returns column name as "IsRelease". but shouldnt matter Convert.ToBoolean(_content["isRelease"] and Convert.ToBoolean(_content["IsRelease"] .. When i check with other columns like "Title" , "Summary" , works fine, only the column starts with i and the column is boolean then VS 2010 throwing an exception.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

What category (if any) best represents this feedback?

 

Steps to reproduce

the code Convert.ToBoolean(_content["isRelease"] is throwing an exception because the store procedure returns column name as "IsRelease". but shouldnt matter Convert.ToBoolean(_content["isRelease"] and Convert.ToBoolean(_content["IsRelease"] .. When i check with other columns like "Title" , "Summary" , works fine, only the column starts with i and the column is boolean then VS 2010 throwing an exception.

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

Getting an exception

Expected results

Should work without changing the column name

Locale

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 1/21/2013 at 1:56 AM
The product team itself no longer directly accepting feedback for Microsoft Visual Studio 2010 and earlier products. You can get support for issues with Visual Studio 2010 and earlier by visiting one of the resources in the link below:
<http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx>

Sorry for the inconvenience.
Posted by Microsoft on 1/18/2013 at 9:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.