Why do additional class attributes in VB.NET have weird syntax?

Question

I'm just wondering why the class / property attributes in VB.NET have weird optional syntax, like this:

<TestAttr("a", "abc", Optional1:="foo", Optional2:=3)>

VB.NET allows you to set optional parameters like this to avoid order restrictions (this is great), but in this case it forces you to do this.

For example, this is not possible:

<TestAttr("a", "abc", "foo", 3)>

even if the parameters are in the same order as the original definition.

Is there a good reason for this? Or was it just that the .NET developers were lazy on this?

Answer 1

, . / , . VB.Net , .

TestAttr , , , , 2 2 Optional1 Optional2.

Answer 2

. . , . .