Type.GetType(name)
-
I am working on a windows app and having some trouble getting type information by just the name. I have to load a file that will have several different type names (Type.FullName). When I call Type.GetType(fullname), it is always returning null, even for types that I would assume it wouldn't like System.Windows.Forms.TextBox. The only way that I can get it to return a type is if it is a local assembly, put it in format of 'Fullname,AssemblyName'. If it is not a local assembly, then I have to put it in the format of 'AssemblyQualifiedName'. This is ok, but it kinda screws some of the useability of the app. Does any one know a way around this? I know that I can use just the full name of the type if I am doing straight from the assembly reference (Assembly.GetType(fullname)), but I would prefer it if I didn't have to have a reference to the assembly to get the type (even though the assembly will be loaded at this point anyways). Any ideas would be greatly appreciated?
-
I am working on a windows app and having some trouble getting type information by just the name. I have to load a file that will have several different type names (Type.FullName). When I call Type.GetType(fullname), it is always returning null, even for types that I would assume it wouldn't like System.Windows.Forms.TextBox. The only way that I can get it to return a type is if it is a local assembly, put it in format of 'Fullname,AssemblyName'. If it is not a local assembly, then I have to put it in the format of 'AssemblyQualifiedName'. This is ok, but it kinda screws some of the useability of the app. Does any one know a way around this? I know that I can use just the full name of the type if I am doing straight from the assembly reference (Assembly.GetType(fullname)), but I would prefer it if I didn't have to have a reference to the assembly to get the type (even though the assembly will be loaded at this point anyways). Any ideas would be greatly appreciated?
Can I ask what you are attempting to do? Type information is somewhat non-human friendly just because it is designed to be that way. :-) Why are you asking the user for a type which may or may not be in any loaded assembly? Maybe you should instead offer a list of loaded types with a filter?
-
Can I ask what you are attempting to do? Type information is somewhat non-human friendly just because it is designed to be that way. :-) Why are you asking the user for a type which may or may not be in any loaded assembly? Maybe you should instead offer a list of loaded types with a filter?