Visual Studio stops debugging when SqlCommand.ExecuteScalar() is executed

Question

I have this code in my application

SqlConnection sqlConnection1 = new SqlConnection(connectionString);

SqlCommand cmd = new SqlCommand();
cmd.CommandType = System.Data.CommandType.Text;

sqlConnection1.Open();

cmd.CommandText = "SELECT S2 FROM CDUSR WHERE N100 = " + N100.ToString()  ;

var HashStr = cmd.ExecuteScalar();
sqlConnection1.Close();

When I reach at the line

var HashStr = cmd.ExecuteScalar();

Visual Studio 2015 stops debugging my application without any error.

connectionString contains a valid connection string (I have tested)

This query SELECT S2 FROM CDUSR WHERE N100 = 6369 executes successfully in SSMS.

I want to know what the problem is. S2 contains the following string:

a4sd4545ag5645sdfa55sdf45fv5er5cfvg5s45

SQL Injection alert - you should not concatenate together your SQL statements - use parametrized queries instead to avoid SQL injection — marc_s
– marc_s, Commented Jun 20, 2016 at 11:16
yes you are right but i am not getting this from user input and i know 100% whats inside N100 — Ali Shan
– Ali Shan, Commented Jun 20, 2016 at 11:18
add a try catch block for that line. is N100 column varchar type? — riteshmeher
– riteshmeher, Commented Jun 20, 2016 at 11:21

pijemcolu · Accepted Answer · 2016-06-20 11:25:57Z

2

Are you using the correct constructor for the SqlCommand? It seems to me that you are atleast missing:

cmd.Connection = sqlConnection1

You might as well do that in the constructor when you create the command:

SqlCommand cmd = new SqlCommand("SELECT S2 FROM CDUSR WHERE N100 = " + N100.ToString()), sqlConnection1)

a using block would be nice as well:

using(SqlCommand cmd = new SqlCommand(blah blah)) { cmd.ExecuteScalar; }

answered Jun 20, 2016 at 11:25

pijemcolu

2,6521 gold badge29 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

PrfctByDsgn · Accepted Answer · 2016-06-21 08:23:43Z

1

I guess Visual Studio stops debugging because your code throws an exception (your SqlCommand is not associated with the SqlConnection you use) ... maybe you have "Common Language Runtime Exceptions" disabled in your "Exception Settings" so you don't actually see the exception being thrown ...

answered Jun 21, 2016 at 8:23

PrfctByDsgn

1,0621 gold badge15 silver badges21 bronze badges

Collectives™ on Stack Overflow

Visual Studio stops debugging when SqlCommand.ExecuteScalar() is executed

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related