MBR IT/.NET 247 : Dynamiclly loaded assemblies and IsDefined on microsoft.public.dotnet.framework.clr

Dynamiclly loaded assemblies and IsDefined

Messages

Related Types

This message was discovered on microsoft.public.dotnet.framework.clr.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.

Post a new message to this list...

Patrik Löwendahl [C# MVP] (VIP)

Hi,

I'm running laps around this, need some fresh input.

I'm writing a component that runs in asp.net 1.1 (no sp) which dynamically
loads assemblies from a shared store. Each of theese assemblies contains one
or types marked with a custom attribute. When iterating and checking theese
types IsDefined won't return true even for types where the attribute is
present.

Retrieving the attributes and manually iterating them will show that the
attribute truely is present, but no luck with IsDefined.

Where's my head at??

<code>
// ExportDescriptionAttribute is a standard custom attribute, with Attribute
target set to class.
// there's no inheritance issues either.
string path = HttpContext.Current.Server.MapPath("bin/admin.export.dll");
Assembly expAss = Assembly.LoadFile(path);
foreach(Type exportType in expAss.GetTypes()) {
if(exportType.IsDefined(typeof(ExportDescriptionAttribute), false)){
}
}
</code>

--
Patrik Löwendahl [C# MVP]
www.cshrp.net - "Elegant code by witty programmers"

Reply to this message...

Robert Jordan

Patrik Löwendahl [C# MVP] wrote:

[Original message clipped]

I encountered the same problem a couple of months ago (.NET 1.1).
Thought it was my bug, I've rewritten the code using
GetCustomAttributes.

bye
Rob

Reply to this message...

Richard Blewett

So you are saying that if you use
GetCustomAttributes(typeof(ExportDescriptionAttribute), false); you get a
collection of the attributes back OK?

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

"Patrik Löwendahl [C# MVP]" <Click here to reveal e-mail address> wrote in
message news:Click here to reveal e-mail address...
[Original message clipped]

Reply to this message...

Patrik Löwendahl [C# MVP] (VIP)

No, asking for the type don't do it,

But doing a foreach(object attr in t.GetCustomAttributes(true))

will let me find it manually.

--
Patrik Löwendahl [C# MVP]
www.cshrp.net - "Elegant code by witty programmers"

"Richard Blewett" <Click here to reveal e-mail address> wrote in message
news:Click here to reveal e-mail address...
[Original message clipped]

Reply to this message...

Richard Blewett [DevelopMentor] (VIP)

Are you sure that the assemblies you are loading weren't built against a
version of the attribute assembly other than the one you are testing for?

The runtime considers the same type from two different versions of an
assembly to be two distinct types and so would cause the behaviour you are
seeing.

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

"Patrik LÃ¶wendahl [C# MVP]" wrote:

[Original message clipped]

Reply to this message...

	System.Reflection.Assembly
	System.Web.HttpContext

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com