[Mono-dev] ASP.NET MVC 3 Preview
monoman at gmail.com
Wed Aug 4 09:25:21 EDT 2010
Can you try to debug it with MonoDevelop? (latest versions enable the
soft debugger for ASP.NET (xsp)).
It sure seems like some path transformation or file-access mishap,
although the responsible to tell the view is available is each view
engine and there should be code that is dependent on something else
that isn't available.
Ideally you should compile ASP.NET MVC from sources, but they seem not
to be available yet, to have debug symbols in Mono's format so you can
step in that code and see what is happening.
Rafael "Monoman" Teixeira
"To be creative means to be in love with life. You can be creative
only if you love life enough that you want to enhance its beauty, you
want to bring a little more music to it, a little more poetry to it, a
little more dance to it."
On Tue, Aug 3, 2010 at 2:30 PM, Tomi <bosak.tomas at gmail.com> wrote:
> 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 <robertj at 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).
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list