nal Message-
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of
Sean Greer (SBI-Chico)
Sent: Tuesday, April 23, 2002 4:22 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] AW: [DOTNET] AW: [DOTNET] Load Form by Name
You are using the namespace-qualified name, correct?
If you have
ET] AW: [DOTNET] AW: [DOTNET] Load Form by Name
It's your code:)
01 Dim ty As Type =
System.Reflection.Assembly.GetExecutingAssembly.GetType(strFormName)
02 Dim frm As System.Windows.Forms.Form = Activator.CreateInstance(ty)
The exception raised is System.ArgumentNullException, raised o
To: [EMAIL PROTECTED]
Subject: [DOTNET] AW: [DOTNET] AW: [DOTNET] Load Form by Name
> I found the Activator class a little while ago and played around with
> it, but no luck. Seems that the type info is available, but
> Activator.CreateInstance doesn't create an instance of the form.
It DO
, April 23, 2002 2:59 AM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] AW: [DOTNET] Load Form by Name
Like I said, just had the impression that there were performance issues. Wasn't saying
it was or wasn't a problem.
I found the Activator class a little while ago and played around with it,
> I found the Activator class a little while ago and played around with
> it, but no luck. Seems that the type info is available, but
> Activator.CreateInstance doesn't create an instance of the form.
It DOES create an instance of the form! I use this technique myself for
loading forms dynamicall
ate an instance of the form.
Thanks anyway.
Dan
-Original Message-
From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of
Urs Eichmann
Sent: Tuesday, April 23, 2002 1:42 AM
To: [EMAIL PROTECTED]
Subject: [DOTNET] AW: [DOTNET] Load Form by Name
I can't quite see y
I can't quite see your point not to use reflection. Reflection is VERY fast,
especially compared to the time needed to actually show a form. The
framework uses it all the time, probably without you even noticing. Also, if
you're using Reflection on your own assemblies, there shouldn't be a problem
