As part of this effort, I've recently tested all the non-data samples in the .Net QuickStarts set (available either online at http://quickstarts.asp.net/ or with the .NET SDK) and fixed quite a few little bugs or incompatibilities. Unfortunately the changes aren't part of the Mono 1.2.4 release but, as before, I recommend that you use the svn trunk version of Mono (or a daily snapshot) for your 2.0 development and testing. The data controls will be tested as soon as we update our SqlClient implementation with some features that'll help in the testing.
A note about testing the QuickStarts with xsp2 on Mono. The online QuickStarts site uses probably virtual directories in IIS to make sure that the samples which are fully-contained applications get their configuration and paths right. If you run xsp2 in the aspnet/ QuickStarts directory and notice that some don't work, just go to their source folder and run xsp2 from there.
Currently, again as part of the .NET conformance testing, I'm porting several ASP.NET 2.0 applications (starter kits and others) to use PostgreSQL instead of MS SQL - this will allow them to be fully hosted on Unix. I will blog about the ports as they happen.
3 comments:
Why don't you contribute patches to those projects for using NHibernate (so as to use any database), and that way you don't make forks.
The idea is to modify the project as little as possible, just enough to make them fully working under Mono/Unix. They are supposed to test Mono ASP.NET 2.0 stack for compliance with the .NET one.
I tried this on IIS 8.0
http://blogs.homelinux.org/2007/03/09/openid-for-your-site-provides-3-states-by-default/
works fine,
tried it with the latest XSP2,
it loads but throws nasty exception after control is handed back to the site (by the OpenID provider)
tried it with the latest mod_mono
simply states it can't find the assemblies
(ran XSP2 on the same directory)
So there are still a few problems here and there, also XSP2 is awfully slow on windows systems, not that I care about that :p
Post a Comment