Mono 2.0!

Congrats to the Mono Team on shipping Mono 2.0!

Mono 2.0

I'm eager to try it myself and am interested to hear from people using mojoPortal on Mono. So if you try it with our latest release package for Mono, let us know how it works for you.

I generally test Mono with a virtual machine where I build Mono from svn to stay up with the latest changes and then I keep another VM for testing the releases. So I downloaded the new VMWare image with openSuse 11 and Mono 2.0, but apparently this vmware image isn't compatible with the older version of VMWare server I have running, so I've got some upgrading to do before I can try it. I have a physical machine running openSuse 10.3 with VMWare server and then I run the testing virtual machines inside it. I also got a new video card I need to install in this machine so I'm installing that first and then upgrading my vmware host machine to openSuse 11 and then I'll install the newer release of VMWare server, and then finally I will be ready to play with the new Mono release.

2.0 is a big milestone for the Mono project so I'm really looking forward to it. Hope you will try it too and share your experiences. If you are a developer and you have MonoDevelop, we include a MonoDevelop solution with the mojoPortal source code, so you can checkout mojoportal from our Subversion repository and compile it with MonoDevelop. So not ony can you run mojoPortal on Mono, you can also do mojoPortal development on Linux with MonoDevelop.

Gravatar Joe Audette is the founder of the mojoPortal project and was the primary developer until February 2017.
Posted by mojoPortal Wednesday, October 8, 2008 8:28:09 AM Categories: Community Development

Comments

Alan

re: Mono 2.0!

Wednesday, October 8, 2008 11:45:49 AM

MonoDevelop has native support for .sln/.csproj, so you don't have to maintain two build systems. It can also integrate with makefiles if you use those.

Joe Audette

re: Mono 2.0!

Wednesday, October 8, 2008 12:08:56 PM

Yes, thats true! But for several reasons we find it advantageous to have separate MonoDevelop projects and Solutions.

It allows us to more easily leave out things like WebParts that aren't implemented in Mono. In some cases we also need to reference differant dlls for Mono than we do for VS on Windows. Basically it gives us flexibility to do things differently in VS vs MonoDevelop.

Stifu

re: Mono 2.0!

Thursday, October 9, 2008 11:49:19 AM

I'm also very enthusiastic about Mono and the recent 2.0 release. :)

I've been working on a C# project for a little while... I tried it with Mono 2.0 just yesterday (using the openSUSE LiveCD), and it works (which surprised me, as I didn't think my GDI code would work outside of Windows), but there's a couple of bugs (including crashes). I also tried Mono 2.0 on Windows, and encoutered the same bugs, apart from the 2 most annoying ones which don't appear on Windows (namely: zoom not working, and crash).

Comments are closed on this post.