Re: Immediate Window and DBNull
- From: "Bryan Phillips" <bphillips@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 15 Oct 2006 18:24:00 +0000
The difference is that the VS2005 immediate window is showing the ToString result of System.DBNull.Value which happens to be String.Empty.
Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
"john armitage" <johnarmitage@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6CBE72CB-BD64-4E64-97B9-573F6B1FE792@xxxxxxxxxxxxx:
Quick question about DBNull in the immediate window. Not sure if it is the
framework or the tool...but I'm betting that there is a setting in the tool.
I'm using Visual Studio .NET 2003 with the 1.1 framework, and Visual Studio
.NET 2005 with the 2.0 Framework.
I notice that while debugging in VS2003, in the Immediate window, if I type
System.DBNull.Value I see the following:
System.DBNull.Value
{System.DBNull}
System.Object: {System.DBNull}
Value: {System.DBNull}
BUT, while debuggin in VS2005, in the Immediate window, if I type
System.DBNull.Value what I see is:
System.DBNull.Value
{}
What changed? I ask because it seems like the app is acting different when
I set a SqlParameter.Value = DBNull.Value.
.
- Prev by Date: Re: preventing dos window close upon program termination
- Next by Date: Re: Unable to debug mixed-mode under x64. Any suggestions?
- Previous by thread: Re: preventing dos window close upon program termination
- Next by thread: Re: Unable to debug mixed-mode under x64. Any suggestions?
- Index(es):
Relevant Pages
|
Loading