No. This is sort of the modern day late-binding.
It appears you can't without having to turn Option Strict off. I'll research some more though. Edit After going through some documentation on the ExpandoObject, it appears it is used in C# for COM and Office Interop.
Traditionally, in VB. NET, the Object was used for such purposes and that would require you turn off Option Strict. To answer your question this means that you can use dynamic types in VB.NET by using the Object type instead of the ExpandoObject if such a type exists in VB.
NET, set Option Infer On and Option Strict On or Off. You could also consider using partial classes to localise your non Option Strict code to particular files. Suggested Reading Dynamic Type in C#, Equivalent in VB Using Type Dynamic (C# Programming Guide).
I haven't tried this, and it wouldn't be pretty, but you ought to be able to use CallByName. Adapting your example Partial Public Class ClassX Public Sub TestDynamic() Dim dyn As Object = New System.Dynamic.ExpandoObject() Dim a As String = "1" ''# Option Strict is on Dim obj As Object = "999" ''# dyn. Str = a CallByName(dyn, "Str", CallType.
Set, a) Console. WriteLine("dyn. Str = {0} : Type = {1}", CallByName(dyn, "Str", CallType.
Get, a), CallByName(dyn, "Str", CallType. Get, a).GetType().ToString() ) ''# etc etc... I can't face any more of that As I said, it's not pretty.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.