Should new VB.NET projects default to Option Strict On?
Visual Basic as a language does not implement authentication or credential expiration. Least-privilege enforcement and expired credential detection are provided by the .NET runtime, Windows security and application code, not by VB syntax. The documented language behavior relevant here is VB.NET's permissive type system and late binding, controlled by Option