VB.NET syntax counterpart in C#.

Question

4.00/5 (1 vote)

See more:

What's the counterpart of the following statement in c#?

Try

Catch sqlex As SqlException When sqlex.Number = 547

End Try

Posted 27-Mar-11 5:55am

priyamtheone

Updated 27-Mar-11 8:44am

Sergey Alexandrovich Kryukov

v3

Add a Solution

3 solutions

Solution 1

C#

try {
}
catch (SqlException sqlex) {
    sqlex.Number = 547;
}

Will this do?

Posted 27-Mar-11 6:00am

Dalek Dave

Updated 27-Mar-11 6:08am

v2

Comments

Dalek Dave 27-Mar-11 12:09pm

Oops, fixed.

dan!sh 27-Mar-11 12:12pm

OP doesn't want to set the number. He wants to do something based on the exception number. Generally it is done to show a user friendly message in the application rather than showing exact SQLException.

Dalek Dave 27-Mar-11 13:10pm

And you could tell all that from the question? :)
I just did the straight conversion.

dan!sh 27-Mar-11 13:42pm

I did the conversion too. I am just telling one of the most likely reasons to do that. :)

Sergey Alexandrovich Kryukov 27-Mar-11 14:52pm

That is not it; "=" is not assignment in that VB.NET code, it is a check.
--SA

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

*dan!sh* · Accepted Answer · 2011-03-27T06:03:00

Solution 2

Here it is:

try{
// Some code here
}
catch(SqlException sqlException){
if( sqlException.Number == 547){
// Do something
)
else{
// Do something
}
}

If you are tracking a lot of numbers, then use switch.

Posted 27-Mar-11 6:03am

dan!sh

Comments

priyamtheone 27-Mar-11 12:21pm

Thanks d@nish. Yeah we all know this would be the most basic syntax. Aside from this I was looking whether there's any alternative or workaround for this. Regards.

dan!sh 27-Mar-11 12:38pm

No AFAIK there is no other way. You can probably have this piece of code in a class and then re-use it in your DAL.

Niklas L 27-Mar-11 14:40pm

I don‘t do VB, but should there not be a throw in the else clause?

dan!sh 27-Mar-11 14:45pm

Well, it depends on what OP is doing with the exception. IMHO this catch block will be in DAL so it will anyways be throwing the exception to Business Layer and then to the UI.

Sergey Alexandrovich Kryukov 27-Mar-11 14:51pm

There is not difference between VB.NET and C# in this aspect: to re-throw or not does not really depend on "else" branch; it can be re-thrown in both cases on none of them. "Do something" tells all what can be done :-)
--SA

Niklas L 27-Mar-11 17:59pm

It was actually "When sqlex.Number = 547" that caught my attention. For a non-VB guy, it looks like the exception will be caught only if error number is 547. Maybe that's not the correct interpretation? Or will the exception be caught anyway in the VB version?

Sergey Alexandrovich Kryukov 27-Mar-11 19:01pm

Frankly, I'm not sure.
--SA

Sergey Alexandrovich Kryukov 27-Mar-11 14:51pm

My 5.
--SA

priyamtheone · Accepted Answer · 2011-03-29T06:54:00

To be clear from all further confusions, the idea is the program control will only enter the catch block if the exception number is 547. I was unable to find any counterpart of the When keyword in C#. That's why I posted for. Anyway thanks everyone for the short but informative discussion. Regards.