Visual Basic 2005 introduces new compiler checking options

Visual Basic 2005 introduces new compiler checking options. The /nowarn and /warnaserror options provide more control over how warnings are handled. Each one of these compiler options now takes a list of warning IDs as an optional parameter, to specify to which warnings the option applies.

• CLS Compliance Checking

Visual Basic now generates a warning for each line of code that contains any specification or operation that the Common Language Specification (CLS) does not support.

• Uninitialized Variable Checking

Visual Basic now generates a warning for each potentially uninitialized variable. A variable has this status if there is at least one possible execution path that does not assign any value to the variable before using it.

[

On record.... I planned to post 2.0 changes from today...!

As Beta is out and I felt it's more stable now... after testing various modules....

]