RE: [ndoc-devel] Beta 2 problem loading assemblies

[Pascal B. <Bou...@xc...>]

Interesting!

Well, I think I'll go with the workaround suggested in the user's guide,
which is to compile a special build of our assemblies without this
attribute for the purpose of generating the documentation.

Thanks for your support! :-)

Pascal=20

-----Original Message-----
From: Kevin Downs [mailto:kd...@op...]=20
Sent: October 14, 2004 6:56 PM
To: Pascal Bourque
Cc: ndo...@li...
Subject: RE: [ndoc-devel] Beta 2 problem loading assemblies

Yes! We have an answer.... This is a 'known issue' (see Users Guide)

Assemblies decorated with the StrongNameIdentityPermission attribute can
only be called by other assemblies that are marked with the specified
key.=20

Now, 'called' is a somewhat vague term that includes some of the
functionality within reflection. When reflection attempts GetTypes(), a
demand is triggered and the stack walk hits the NDoc assemblies. These
assemblies obviously do not have the same key, and so a
SecurityException is thrown :(

I can think of two possible work-arounds, and both are unpleasant...

1. disable CAS on the machine running Ndoc - most definitely not
recommended 2. recompile NDoc using the same key as your assemblies -
possibly not too bad if you always use the same key file for all your
work...


Obviously, our error reporting is rubbish for this type of error - I
will look at rewriting the offending code ASAP=20


regards,
Kevin

---
"Never attribute to malice that which can be adequately explained by
stupidity"