[Mono-list] Run ASP.Net 4.0 profile

[Abe Gillespie]

Guys, totally my bad, sorry for all the spam today.  It turns out when
you set MonoServerPath in the general mod_mono.conf file it does not
then become the default for all your VirtualHosts.

In other news, 2.8 is running fantastically. It's faster and running
more smoothly than my other sites on previous version.

Thanks for all the great work, Team Mono!  Have a great weekend.

-Abe

On Fri, Oct 8, 2010 at 6:27 PM, Abe Gillespie <abe.gillespie at gmail.com> wrote:
> OK, a little more information.  I have these in my mod_mono.conf:
> MonoAutoApplication disabled
> MonoServerPath "/usr/local/mono/2.8/bin/mod-mono-server4"
>
> But despite these (and I'm sure the mod_mono.conf file is called from
> httpd.conf), my yellow screen of death is reporting this in the
> footer:
> Version information: Mono Runtime Version: 2.8 (tarball Fri Oct 8
> 18:40:28 UTC 2010); ASP.NET Version: 2.0.50727.1433
>
> So those directives are either being ignored or mod-mono-server4 isn't
> actually working with the correct runtime.
>
> -Abe
>
> On Fri, Oct 8, 2010 at 1:15 PM, Abe Gillespie <abe.gillespie at gmail.com> wrote:
>> This is the error I get if I copy the 4.0 System.Web assembly to the
>> local bin dir:
>>
>> System.TypeInitializationException: An exception was thrown by the
>> type initializer for System.Web.Configuration.WebConfigurationManager
>>
>> Server stack trace:
>>  at System.Web.Hosting.ApplicationHost.SetHostingEnvironment () [0x00000] in <f
>> ilename unknown>:0
>>  at System.AppDomain.DoCallBack (System.CrossAppDomainDelegate callBackDelegate
>> ) [0x00000] in <filename unknown>:0
>>  at (wrapper remoting-invoke-with-check) System.AppDomain:DoCallBack (System.Cr
>> ossAppDomainDelegate)
>>  at (wrapper xdomain-dispatch) System.AppDomain:DoCallBack (object,byte[]&,byte
>> []&)
>>
>> Exception rethrown at [0]:
>>  ---> System.MissingMethodException: Method not found: 'System.Type.op_Inequalit
>> y'.
>>  --- End of inner exception stack trace ---  at (wrapper
>> xdomain-invoke) System.AppDomain:DoCallBack
>> (System.CrossAppDomainDelegate)  at (wrapper
>> remoting-invoke-with-check) System.AppDomain:DoCallBack (System.Cr
>> ossAppDomainDelegate)
>>  at System.Web.Hosting.ApplicationHost.CreateApplicationHost
>> (System.Type hostType, System.String virtualDir, System.String
>> physicalDir) [0x00000] in <filename unknown>:0
>>  at Mono.WebServer.VPathToHost.CreateHost
>> (Mono.WebServer.ApplicationServer server, Mono.WebServer.WebSource
>> webSource) [0x00000] in <filename unknown>:0
>>  at Mono.WebServer.Apache.Server.RealMain (System.String[] args,
>> Boolean root, IApplicationHost ext_apphost, Boolean quiet) [0x00000]
>> in <filename unknown>:0
>>  at Mono.WebServer.Apache.Server.Main (System.String[] args)
>> [0x00000] in <filename unknown>:0
>>
>>
>> On Fri, Oct 8, 2010 at 11:18 AM, Abe Gillespie <abe.gillespie at gmail.com> wrote:
>>> How do you instruct Mono to run the 4.0 profile for an ASP.Net MVC2
>>> site?  I'm using the
>>>
>>> MonoServerPath "/usr/local/mono/2.8/bin/mod-mono-server4"
>>>
>>> directive but this doesn't seem to be enough.  During startup I get:
>>> System.TypeLoadException: Could not load type
>>> 'System.Web.Routing.RouteCollection' from assembly 'System.Web,
>>> Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
>>>
>>> I can't use this in the Web.config:
>>> <compilation debug="true" targetFramework="4.0">
>>> because the targetFramework attribute is not recognized.
>>>
>>> I've also tried adding:
>>> <add assembly="System.Web, Version=4.0.0.0, Culture=neutral,
>>> PublicKeyToken=b03f5f7f11d50a3a" />
>>> to the <compilation><assemblies> collection of the Web.config but this
>>> doesn't seem to help either.
>>>
>>> Now if I manually copy the gac's 4.0 System.Web assembly into the
>>> site's bin then I can get a little further than the above stated error
>>> but other badness happens.
>>>
>>> Any ideas?
>>>
>>> Thanks.
>>> -Abe
>>>
>>
>