Option Explicit In Biml VB

Ben Weissman now has nothing to stop him from writing bad VB code in Biml:

Previously, you had to declare any kind of variable and object type (instead of just using something like “var” in C#):

1 2 3 4 5 6 7 8

<#@template Language="VB" #> <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <# for n as integer = 1 to 25 #>     <Package Name="MyAutomatedBiml<#= n #>"/> <# next#> </Packages> </Biml>

That was true even for the most simple cases like for n as integer = 1 to 25 instead of just for n = 1 to 25, even though it is clear that his can never be anything else in this context.

Now, you can use two new attributes in the template definition: optionexplicit and/or optionstrict

Read the whole thing if you want to write VB code in Biml.  If you want to write C# code in Biml, keep doing your thing.  If you want to write F# in Biml, the pitchfork mob is organizing over here.