ASP.NET MVC 1 and 2 on Mono 2.4 with Fluent NHibernate
Posted
by SztupY
on Stack Overflow
See other posts from Stack Overflow
or by SztupY
Published on 2009-06-13T13:24:46Z
Indexed on
2010/04/21
14:13 UTC
Read the original article
Hit count: 557
Hi!
I'd like to create an application using ASP.NET MVC, that should run under mono 2.4 (compiling will be done on a Windows box). Has anyone getting luck with this? Here is what I've already tried:
- ASP.NET MVC on mono without any persistence model support, and using nhaml as the view engine
- S#aml architecture, which is a quite good framework imho, but it depends too much on stuff, that are not working good under mono (like windsor)
The first part worked fine, I didn't encounter any major problems. But I couldn't get the second part working. It seems it's dependency on Castle.Windsor
breaks the whole mono support (but there might be other parts too).
Therefore I decided to create an alternative framework, that borrows some of the ideas of s#arp-architecture, but designed to be working under mono (and if I'm able to do this I'll release it for the community of course). The controller and view part is working fine (not much magic here though, they have been always working), but I have some questions before I start job on the persistence part:
- What NHibernate versions are working under mono? I've heard 1.2 is working fine. Does 2.0.1/2.1 beta work under mono?
- Does Fluent.NHibernate and NHibernate.Linq work under mono? (for the latter it seems it needs some dependcies that aren't avaialable in mono)
- Are there any good alternatives for persistence support to NHibernate under mono?
Alternative questions:
- Are there any frameworks that have mono+persistence+asp.net mvc support already or am I the first one to think about this?
- If you have already done this: what are your opinions on stability/usability?
Thanks for the answers
EDIT: Updated the framework to support ASP.NET MVC 2: http://shaml.sztupy.hu/
© Stack Overflow or respective owner