I didn't remove that attribute to fix the exception permanently. According to documentation, the assembly should be now loaded with full trust, which probably shouldn't break anything (I may be wrong of course). Broken environment would probably affect also MVC 2 application targeted to run on .net 4.0 which however work as expected. The only difference in deployed web application is System.Web.Mvc.dll in bin folder.
On 3 August 2010 19:07, Robert Jordan <robe...@gmx.net> wrote: > On 03.08.2010 18:25, Tomi wrote: >> Hi folks, >> >> I wanted to try out preview version of ASP.NET MVC 3 on trunk version >> of mono, so I downloaded it from git (mono, xsp, mod_mono). Then I >> removed [MonoTODO] attribute on line 806 (IsFullyTrusted property) in >> Assembly.cs >> (http://github.com/mono/mono/blob/master/mcs/class/corlib/System.Reflection/Assembly.cs) >> because otherwise I would get "Method not found" error. After setting >> up this "modified" parallel environment and configuring >> apache/mod_mono to use mod-mono-server4 I get this stuff: > > This makes absolutely no sense. Removing [MonoTODO] does not fix > "Method not found" exceptions. I believe you've got a broken > development/testing environment (mixed 2.0 and 4.0 assemblies). > > Robert > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
