Security problem with Web Part Connection

From: Achim Domma (SyynX Solutions GmbH) (achim.domma_at_syynx.de)
Date: 11/16/05 

Date: Wed, 16 Nov 2005 17:35:26 +0100

Hi,

I have a problem with Web Part Connection which seems to be a security
problem, but I don't understand what happens:

I have an assembly controls.dll which implements some asp.net controls
and a logging facility. Based on this assembly I have part.dll which
implements a web part. The web part displays controls from controls.dll
and uses the logging facility from controls.dll.

The web part consumes a parameter and I have to web parts which can
provide a paramter for the web part from part.dll:

The first one is a simple demo web part which has a text box and a
submit button. The entered value is provided as parameter to the
consuming web part. If the parameter is provided by this demo web part,
I can see log messages written by controls.dll and part.dll in my logfile.

Then I have a third party web part which can provide the data for
part.dll. If I connect this part with my consuming web part, I see only
log messages from controls.dll in my log files. All messages which are
written in part.dll simply do not appear. But I did not get any error!?

The trust level is set to 'full'. Can somebody give me a hint why
part.dll can not write to the logfile and why no exception is raised?
Even if there are inhertited security settings (which I probabyl don't
understand), these settings should be inherited to control.dll also!?

I have read about code access security but I have no glue what's going
on here. Any hint in any direction would be very appreciated.

regards,

Achim