Type.GetType(st ring)

[the fuzz]

yeah g'day..... is it somehow possible to not include the version & public
key token in the call to Type.GetType(st ring)

ie something like

Type.GetType("S ystem.Windows.F orms.ListView, System.Windows. Forms");

instead of

Type.GetType("S ystem.Windows.F orms.TextBox,
System.Windows. Forms,Version=1 .0.5000.0, Culture=neutral ,
PublicKeyToken= b77a5c561934e08 9");

The first version doesn't work because the type
System.Windows. Forms.ListView doesn't reside in the current assembly or
mscorlib, but i don't want to have to include version information when
retrieving a type.

cheers
the fuzz

[Mattias Sjögren]

yeah g'day..... is it somehow possible to not include the version & public
key token in the call to Type.GetType(st ring)

You can use Assembly.LoadWi thPartialName and pass in a partially
qualified assembly name. But see
http://blogs.msdn.com/suzcook/archiv.../30/57159.aspx for good
reasons why you shouldn't do that. Why don't you have a compile time
reference to the assembly instead and use the typeof operator?

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

[the fuzz]

"Mattias Sjögren" <ma************ ********@mvps.o rg> wrote in message
news:%2******** ********@TK2MSF TNGP11.phx.gbl. ..

You can use Assembly.LoadWi thPartialName and pass in a partially
qualified assembly name. But see
http://blogs.msdn.com/suzcook/archiv.../30/57159.aspx for good
reasons why you shouldn't do that. Why don't you have a compile time
reference to the assembly instead and use the typeof operator?

I serialize user controls at design time to an xml document which is stored
in a db, and provide a runtime designer so that our customers can manipulate
the layout of our program (but not add new controls). At runtime when a form
is loaded the xml document is recursed and the child controls properties are
set according to how the customer has modified the layout. kinda simplified
xaml

An xml document in its simplest form looks like the following at the moment:

<Test.Login assembly="Displ ayEngine">
<System.Windows .Forms.ListView assembly="Syste m.Windows.Forms ,
Version=1.0.500 0.0, Culture=neutral , PublicKeyToken= b77a5c561934e08 9"
name="listView1 " view="Details" location="360, 32" tabIndex="7" />
</Test.Login>

I worry that when new versions of the .net framework come out this will pose
an upgrade challenge because of the embedded versioning in the assembly
attribute. eg. my program will want to run on v2 which i know i can enforce
through the <supportedRunti me> & <requiredRuntim e> attributes, but the xml
will still contain references to v1.1. do you think this will be an issue,
also wouldn't third party UI controls on my forms also have the same problem
here?

thanks,
the fuzz

[Mattias Sjögren]

I worry that when new versions of the .net framework come out this will pose
an upgrade challenge because of the embedded versioning in the assembly
attribute. eg. my program will want to run on v2 which i know i can enforce
through the <supportedRunti me> & <requiredRuntim e> attributes, but the xml
will still contain references to v1.1. do you think this will be an issue,
also wouldn't third party UI controls on my forms also have the same problem
here?

The framework's unification feature should ensure that the
System.Windows. Forms assembly version matching the framework version
you're running under is loaded, even if you're requesting an older
version. For more details on unification policy, see

http://weblogs.asp.net/junfeng/archi...23/268388.aspx
http://blogs.msdn.com/alanshi/archiv.../15/73244.aspx

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.