Ok Roger I've repreduced the exception.

1. Change Trustlevel to Medium
2. Open web_mediumtrust.config (C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG)
- Remove lines
<SecurityClass Name="ReflectionPermission" Description="System.Security.Permissions.ReflectionPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
AND
<IPermission class="ReflectionPermission" version="1" Flags="RestrictedMemberAccess"/>

Following these steps will produce the exception: Request for the permission of type System.Security.Permissions.ReflectionPermission

Some options:
1. Figure out if and/or why these settings missing in the configuration of 'b b' and Garry
2. See if we can live without Reflection which I doubt. (at least in future versions), but should be considerd.
3. Figure out where exactly the EventList results in a exception.

Later more...

Ralf

some refs:
http://msdn.microsoft.com/en-us/library/tkscy493.aspx > trust Element (ASP.NET Settings Schema)
http://msdn.microsoft.com/en-us/library/bb907622.aspx > Linq and code access security
http://forums.asp.net/t/1211663.aspx > ASP.net forum

Ok think I've solved the problem:
Problems with ReflectionPermission on EventList when binding. For some unknown reason making the EventObject Public solves the problem.

Checked-in the new version of EventList.

Greetings,

Ralf

That was kind of what I was going to test, if only I could get my dev environment to play. I'd seen something about making objects public. I'll try to test, and we'll get this into 5.0.3.

Thanks Ralf!!

Cheers
Roger