0

I'm turning On Option Strict on all project in my newly inherited VB.NET application. I'm mostly adding alot of CStr, CBool, CType statements to get rid of all the compile errors.

Dim x As String = someObject
dim val As SomeEnumType = 1

becomes

Dim x As String = CStr(someObject) ' Not .ToString() because someObject could be Nothing
Dim val As SomeEnumType = CType(1, SomeEnumType)

etc.

I'm doing everything pretty much by hand one error at a time and have a test application to test the Nothing, ... bordercases.

But is it possible I'm missing something that is going to generate exceptions at runtime? And what kind of code is being generated due to Option Strict? Is it just some conversions that are going to be added or does OptionStrict do other things aswell?

Laoujin
  • 9,962
  • 7
  • 42
  • 69

1 Answers1

2

Option Strict On does not generate any extra code, it merely tells the compiler to generate errors when your vb.net statements are relying on implicit type conversions. Like assigning an object to a string. What you've written in your snippet is exactly what the compiler does with Option Strict Off so no extra code is generated by your type conversion operators.

But of course, there's always a non-zero chance that you use the wrong conversion and break the existing code. You'll have to do what's always required when you make changes to code, you'll have to re-test it.

Hans Passant
  • 922,412
  • 146
  • 1,693
  • 2,536
  • From the MSDN link below, I figured these implicit conversions are the only code that is being generated. So the code being added is always CStr, CBool, ... ? If I thus add the correct CStr() etc statements, nothing should be broken (but as you mentioned, I obviously do need to retest) – Laoujin Nov 15 '12 at 14:58