I'm just going off of what's on the web:
http://msdn2.microsoft.com/library/w3f99sx1(en-us,vs.80).aspx
Funny enough Type.GetNestedType notes to use the backtick.
Regardless, the format of the type name (Type`N<>) isn't an "undocumented
feature", just not quite documented correctly in all of the v
> > It's actually the `1 that is currently undocumented in
> > Type.GetType in MSDN
> > (so he'd still be relying on undocumented naming conventions).
>
> Hmmm. I know I read that somewhere at sometime - it wasn't just from
> looking at IL or anything. I'll dig around and see if I can
> find wher
> It's actually the `1 that is currently undocumented in
> Type.GetType in MSDN
> (so he'd still be relying on undocumented naming conventions).
Hmmm. I know I read that somewhere at sometime - it wasn't just from
looking at IL or anything. I'll dig around and see if I can find where I
read abou
> You might want to consider using MakeGenericType instead to
> get your hands on the constructed type:
>
> // Lookup List
> Type genericList = Type.GetType("List`1");
>
> // Setup List
> Type listOfStrings = genericList.MakeGenericType(typeof(string));
>
> That approach should prevent you from hav
> it works. Thank you. As I wanted a concrete type, I have to use
> "Gereric`1[System.String]". But this is not what the documentation of
> "Type.GetType" says ...
>
> Andreas
>
You might want to consider using MakeGenericType instead to get your hands
on the constructed type:
// Lookup List
Type
