I'm trying to go through a DataTable, checking each row against a database to see if it is a duplicate or not, but all my comparisons show they aren't even though some are. I noticed when I look at my datarows, on Items that should be Null the value is {}. If I put that into a SQL Parameter, will that equal Null, or some kind of empty string?
View 8 RepliesWhen in the degug mode stepping through code a line at a time, I want to monitor a variable that was created public on another form. It adds the request, but won't shoe me the data. It says I have to ahve an object reference. I don't know what it wants exzactly or how to give it. Here is an example:
I have on form 1 one a variable, Crec. I am in the debugger debugging code in form 2. To access the variable on form one in my code on form 2, I have to use this syntax: form1.crec Now when I put this quickwatch request in, while debugging form 2, it will not let me see the value for form1.Crec It says I need an object reference. Can you tell me I am doing wrong and how to correct it? I'm sure it something simple.
My colleague and I have recently upgraded our projects from .NET Framework 1.0 and VS2002 to .NET Framework 2.0 and VS2005. We also applied the latest VS2005 service pack.
Our problem: normally when debugging we use the QuickWatch window to drill down into and view collections of objects belonging to the parent object we are "watching". THIS NO LONGER WORKS...instead, we get a message in the value line against the object collection saying:"In order to evaluate an indexed property, the property must be qualified and the arguments must be explicitly supplied by the user."This is incredibly frustrating, particularly when we have large nested collections of objects.We are pretty sure this feature was working fine after we upgraded, but we are not so sure that it was working after we applied the VS2005 service pack.
When viewing a dates Kind property in the watch windows the value "unspecified" will always be return regardless of the actual value.I'm kinda guessing this could be more of a general bug relating to the quick watch window evaluating the shared "Date.Kind" property rather than the specific date instances property.
View 4 Replies