ODP.NET OracleCommand.CommandText conversion error

[pieps86]

I am running the following lines...

            OracleConnection connection=new OracleConnection("myConnectionStringIsHere");
            connection.Open();
            var startValueParameter=new OracleParameter {ParameterName="@START_VALUE", Value=0};
            var chunkSizeParameter=new OracleParameter {ParameterName="@CHUNK_SIZE", Value=10};
            var command=new OracleCommand
                            {
                                Connection=connection,
                                CommandType=CommandType.Text
                            };
                command.CommandText = "select EmployeeID, test_id from ExampleTable where (test_id > :START_VALUE) AND (rownum <= :CHUNK_SIZE)";

The error I get is on the very last line where I try to set command.Command Text.

System.InvalidC astException: Unable to cast object of type 'System.String' to type 'Oracle.DataAcc ess.Client.Orac leConnection'

This is very strange, as it suddenly started happening out of the blue. Any suggestions? Thanks.

[Plater]

Is the colorization of the text abnormal in your visual studio? If one of those quotes is not closed, it could be trying to interpret a whole section of your code as a connection string.

Is this not c#? Because "var" isn't a normal object type in C#. Are you getting mixed up with javascript?

[pieps86]

C# var

'var' is new to C# 3.0

http://msdn.microsoft.com/en-us/library/bb383973.aspx

Also, it is not including anything abnormal in the connectionstrin g or the commandtext. All quotes are accounted for.

[Plater]

'var' is new to C# 3.0

http://msdn.microsoft.com/en-us/library/bb383973.aspx

I thought of that after I had posted.
Hmm and you have debug stepped through to make sure nothing is mangling your objects?

[pieps86]

Nope, nothing is getting skewed anywhere along the way. I even compared this code with older versions in Team Explorer to see if I could find anything that had been changed recently that would cause this error. Also, the problem only seems to be when I debug the project from within Visual Studio. I can put the DLL with this code in an engine and it runs fine.

[ssnaik84]

"var" is introduced for LINQ and you can use it in case of lazy binding; where you dont know the data type at compile time.
if you will use it, application will run.. but you cant debug...

[pieps86]

I don't know about that. I am, in fact, debugging to get this error. Using the 'var' keyword is not the issue. I can explicitly declare all types and still get the same result. Nonetheless, using 'var' does not prevent debugging. I'm in VS2008, btw.

[Plater]

So the error ONLY comes up in debugging, and not in a regular release?
That is very strange. Only thing I can think of is if you are pulling and values from the Properties section, they will be different between regular and debug runs.