[Mono-list] xsp2 and AJAX

Chris Toshok toshok at ximian.com
Mon Jan 9 13:30:35 EST 2006


On Mon, 2006-01-09 at 17:07 +0000, Kevin Flanagan wrote:
> Two related question areas -
> 
> 1.
> 
> We're developing web applications using ASP.NET 2.0. I'd like to ensure
> they'll work under Mono (I know the 2.0 support isn't complete, had good
> experiences with 1.1. though). We'll be using some sort of AJAX-type
> approach (looking at both Atlas and MagicAjax.NET, maybe Anthem and others).
> Does anyone know enough about the various AJAX-on-.NET endeavours to know
> which is most likely to be Mono-friendly? Or is there some particular AJAX
> strategy planned for Mono, or already recommended for use with 1.1? I
> noticed the part in Miguel's mono status blog mentioning Chris Toshok's work
> on an open-source Atlas implementation - does that make Atlas our best bet?

I wouldn't use atlas for a web application anytime soon.  I worked to
implement a bunch of stuff MS put out, and then they went and basically
changed a lot about the way atlas works.  So I'm holding off on working
on it again until things stabilize a bit more, and I'd suggest you do
the same.

I don't really know much about the other ajax-on-.net projects..
certainly not enough to comment on which to use.  That said, they should
all work, and situations where they don't are (probably our) bugs which
we'll of course want to fix :)

> 2.
> 
> Just installed Mono 1.1.12.1 on Windows XP to do some xsp2 tests, using a
> simple single-page C# app - you press an asp:Button and the server side code
> puts the current time in an asp:Label. Runs fine under xsp2. Did the same
> app, but putting both the button and the label in an ajax:AjaxPanel, using
> MagixAjax.NET. Under xsp2, that leads to the following message:
> 
> Server error in '/' application
> 
> ----------------------------------------------------------------------------
> ----
> 
> Description: Error processing request.
> Error Message: HTTP 500.
> 
> Stack Trace: System.MissingMethodException: Method not found:
> 'System.Web.UI.Page.set_EnableEventValidation'.in <0x00000> <unknown
> method>in (wrapper delegate-invoke)
> System.MulticastDelegate:invoke_void_object_EventArgs
> (object,System.EventArgs)in <0x0046f>
> System.Web.HttpApplication+<RunHooks>__3:MoveNext ()
> 
> Presumably MagicAjax.NET happens to be trying to use the
> EnableEventValidation property, which the Mono class-status pages say isn't
> done in Mono yet ... is that one that would be filled in eventually, or not
> implemented for some reason? If the former, any guesses as to whether that
> kind of thing (plus other stuff MagicAjax might use) would be in before
> (say) open-source Atlas fills out?

It'll definitely be in before the atlas implementation is fleshed out.
Could you add a bug for this?

Chris


More information about the Mono-list mailing list