Yesterday I got a question from a developer asking whether or not we could add something called “Option Strict Warn” to the language. This would give a developer a warning when using something like late binding or an implicit conversion, rather than disabling it altogether (through an error).<\/p>\n
As it turns out the ability to set custom custom values for Option Strict is actually already in Visual Studio. To test this out double click on “My Project” and click on the Compile tab of the Application Designer.<\/p>\n
The top 3 lines of the grid (under “Warning configurations”) contain the following options:<\/p>\n
– Implicit Conversion<\/p>\n
– Late binding; call could fail at runtime<\/p>\n
– Implicit type; object assumed<\/p>\n
When you change Option Strict to On you’ll see that all 3 of these change to “Error.” When you change it to Off they all change to “None.” If you change the dropdown to “Warning” you’ll see the Option Strict box updates to “(custom)”.<\/p>\n
If you open up a .vbproj file you can see how this information gets passed through the project system to the compiler. There’s a <NoWarn> element that takes a comma-separated list of warnings to disable, which gets passed to the compiler (through the \/nowarn:<number_list> switch).<\/p>\n
While we don’t recommend manually editing the .vbproj file, you can actually use this mechanism to disable other warnings which aren’t displayed in the grid. Anything inside the <NoWarn> or <WarningsAsErrors> elements will get passed to the compiler.<\/p>\n
If you want to find out a warning’s ID just right-click it in the Error List and click “Show Error Help.”<\/p><\/p>\n","protected":false},"excerpt":{"rendered":"
Yesterday I got a question from a developer asking whether or not we could add something called “Option Strict Warn” to the language. This would give a developer a warning when using something like late binding or an implicit conversion, rather than disabling it altogether (through an error). As it turns out the ability to […]<\/p>\n","protected":false},"author":260,"featured_media":8818,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[192,195],"tags":[83,166],"class_list":["post-5413","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-featured","category-visual-basic","tag-jonathan-aneja","tag-vb2008"],"acf":[],"blog_post_summary":"
Yesterday I got a question from a developer asking whether or not we could add something called “Option Strict Warn” to the language. This would give a developer a warning when using something like late binding or an implicit conversion, rather than disabling it altogether (through an error). As it turns out the ability to […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/posts\/5413","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/users\/260"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/comments?post=5413"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/posts\/5413\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/media\/8818"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/media?parent=5413"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/categories?post=5413"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/vbteam\/wp-json\/wp\/v2\/tags?post=5413"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}