[Mono-dev] ASP.NET MVC 3 Preview

[Tomi]

I also think that it is probably issue of the MVC 3 itself. Anyway
thank you all for your help and time, I will report back when the
source code is available.

On 4 August 2010 15:46, Marek Habersack <grendel at twistedcode.net> wrote:
> On Wed, 4 Aug 2010 10:25:21 -0300
> Rafael Teixeira <monoman at gmail.com> wrote:
>
> Hey,
>
>> 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.
> I think it's something more involved. First, System.Web.Mvc references System.Entity.Data which we
> don't have. Second, mvc3 use a service locator implementation which is used internally to locate
> view engines and the locator failing might be the reason why it cannot find the views. Removing
> any [MonoTODO], of course, doesn't matter here.
>
> Until MVC3 source is out, I can't help you more, I'm sorry. When it is out we will have to
> determine whether it can be compiled without System.Data.Entity support and what's going on with
> the service location.
>
> best,
>
> marek
>
>> 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.
>>
>> Fun,
>>
>> 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."
>> Osho
>>
>>
>>
>> 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).
>> >>
>> >> Robert
>> >>
>> >> _______________________________________________
>> >> Mono-devel-list mailing list
>> >> Mono-devel-list at lists.ximian.com
>> >> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>> >>
>> > _______________________________________________
>> > Mono-devel-list mailing list
>> > Mono-devel-list at lists.ximian.com
>> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>> >
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>