Donn, yes, please send it over - having a way to reproduce and work with it on my machine would make it a lot easier to diagnose. Thanks,
kind regards, Krzysztof Donn Felker wrote: > Krzysztof, > > I just downloaded the latest tonight and built the code with this > command: > > build.cmd -D:assembly.allow-partially-trusted-callers=true > > This outputs the version to be: 2.0.1000.0 > > Upon firing up the app I receive the following security exception: > > ---------------------------------------START > EXCEPTION--------------------------------------------------- > Security Exception > Description: The application attempted to perform an operation not > allowed by the security policy. To grant this application the > required permission please contact your system administrator or change > the application's trust level in the configuration file. > > Exception Details: System.Security.SecurityException: Request for the > permission of type 'System.Configuration.ConfigurationPermission, > System.Configuration, Version=2.0.0.0, Culture=neutral, > PublicKeyToken=b03f5f7f11d50a3a' failed. > > Source Error: > > An unhandled exception was generated during the execution of the > current web request. Information regarding the origin and location of > the exception can be identified using the exception stack trace below. > > Stack Trace: > > [SecurityException: Request for the permission of type > 'System.Configuration.ConfigurationPermission, System.Configuration, > Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' > failed.] > System.Security.CodeAccessSecurityEngine.Check(Object demand, > StackCrawlMark& stackMark, Boolean isPermSet) +0 > System.Security.CodeAccessPermission.Demand() +58 > System.Configuration.BaseConfigurationRecord.CheckPermissionAllowed > (String configKey, Boolean requirePermission, Boolean > isTrustedWithoutAptca) +99 > > > Version Information: Microsoft .NET Framework Version:2.0.50727.4918; > ASP.NET Version:2.0.50727.4918 > > ---------------------------------------END > EXCEPTION--------------------------------------------------- > > I turned on CLR exceptions in VS and an exception was thrown here (see > link for VS Screenshot): http://www.twitpic.com/mfkyz/full > > It looks like the recent change did not work in this instance. > > I have a demo project if you'd like to see it. Let me know and I can > zip it up and send it over. > > Thanks, > > Donn > > On Oct 1, 12:51 pm, Krzysztof Koźmic <[email protected]> > wrote: > >> To anyone interested - this issue is (hopefully) fixed in the trunk. >> Get it, test it - tell us if you find cases where it does not work. >> >> On 22 Wrz, 20:39, Krzysztof Koźmic <[email protected]> wrote: >> >> >>> Yes, basically that's right. >>> >>> Donn Felker wrote: >>> >>>> Let me make sure I have this down correctly. >>>> >>>> I have two options right now. >>>> >>>> 1. Change the DP code to include the code snippet(s) above. >>>> 2. Have my entities implement an empty unsigned interface. >>>> >>>> Correct? >>>> >>>> Thanks! >>>> >>>> Donn >>>> >>>> On Sep 12, 12:52 am, Krzysztof Koźmic <[email protected]> >>>> wrote: >>>> >>>>> Yes in the DP, >>>>> The only workaround that would make it work right now, is if your >>>>> entity implemented an interface (even empty) that comes from an >>>>> unsigned assembly >>>>> >>>>> 2009/9/11 Donn Felker <[email protected]>: >>>>> >>>>>> Krzysztof, >>>>>> >>>>>> Thank you for looking into it. I opened a ticket. Where should this >>>>>> code change be, in the DP code? >>>>>> >>>>>> Thanks >>>>>> >>>>>> Donn >>>>>> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
