Spring on Mono 2.4?

[superciccio]

Is there anybody that is trying to use Spring.NET on the latest official release of Mono?
Mono is a very interesting initiative and is at a mature stage (it implements some WCF functionalities AFAIK).
I think Mono/Spring could be a valid alternative to other award-winning commercial products.
Let me know if you agree with me.

Bye

[Mark Pollack]

Hi,

There have been some users over the course of the project that gotten Spring.NET working on Mono. To my knowledge the core DI, AOP and web functionality is working on mono (2.0). The build scripts are setup to build with mono but I've run into trouble I think getting the tests to run, it has been a while. I remember getting frustrated and simply stopping work on it for some reason. I know that is vauge and not so nice to say, but I've historically had a hard time using mono. I've spoken with people at Novell directly regarding having Spring.NET work on mono and they are quite supportive of this happening. If you come up with any issues, I can contact them directly if normal channels to get things fixed don't work out as expected (unlikely I'd say)

Cheers,
Mark

[superciccio]

Great!
I've got Spring.NET IoC+Data+NHibernate 2.0 working on Mono 2.2/2.4 in Windows/Linux (there were some problems on Mono 2.0 with XMLApplicationContext).
Next step will involve Web Services + WCF + Spring.Integration. Last time I tried it I had some problems with WCF (problems running WCF quickstart).
I'm happy to know that other people are interested in this argument.

Regards

[.ben]

This is completely off topic but in what environment are working with Mono (Mac, Linux distro?) ? And what are you using to develop (MonoDevelop?)?

[superciccio]

Windows XP/.NET 3.5/Mono/Visual Studio 2008 STD/SharpDevelop 3 and openSUSE 11/MonoDevelop.

Bye

[kibbled_bits]

Windows XP/.NET 3.5/Mono/Visual Studio 2008 STD/SharpDevelop 3 and openSUSE 11/MonoDevelop.

Bye

It would be nice if we provided downloads in Mono or at least build scripts for Mono.

[Mark Pollack]

Hi,

The build scripts already support mono and come with the distribution. You just need to comment in the line to build mono in the target "build-all-function" in Spring.build. I'm downloading now mono 2.4 for windows and will try the build. I've never had much luck, I think folks on unix fair better. Lets see how it goes...

Mark

[Mark Pollack]

Hi,

I made a few tweaks to the build scipts to get it to compile (complaints about XML formatting of comments). Had to copy over the libs from \lib\Net\2.0 to \lib\mono\2.0 I don't think any of those .dlls are mono specific. The compilation went well but running the nunit tests didn't work. It failed silently inside testing of Spring.Core. I'm using the nunit2 nunit task. (NAnt 0.86 (Build 0.86.2898.0; beta1) and nunit 2.4.1 (yes it is old). Not really sure how to debug it more, '-v' didn't help...

Mark

[Mark Pollack]

Hi,

I've had some better luck using <exec> for running nunit but now get compiliaton errors like this

     [nant] L:\projects\spring-net\trunk\test\Spring\Spring.Data.Integration.Tests\Spring.Data.Integration.Tests.build test
            Buildfile: file:///L:/projects/spring-net/trunk...egration.Tests.
build
            Target framework: Mono 2.0 Profile
            Target(s) specified: test

            build:
                  [csc] Compiling 51 files to 'L:\projects\spring-net\trunk\build\mono\2.0\debug\Spring.Data.Integration.Tests.dll'.
                  [csc] L:\projects\spring-net\trunk\test\Spring\Spring.Data.Integration.Tests\Data\Generic\GenericAdoTemplateTests.
cs(27,19): error CS0234: The type or namespace name `Common' does not exist in the namespace `System.Data'. Are you missing an assem
bly reference?

I run the build inside the mono 2.4 command window.

Any suggestions?

Mark

[Mark Pollack]

Hi,
Well false alarm, I forgot I need to explicitly specify each dependent .dll in the build (*.dll works for .NET MSoft builds) That said, even though I include a reference to System.Web.Services.dll I still get a similar error for Spring.Services.Tests... calling it a day for this 2 hr round...but it is looking better.

Mark