Linked by Eugenia Loli on Mon 4th Jun 2007 05:01 UTC
Mono Project The amount of effort required to get an existing Winforms app running on Mono can vary greatly. Although many small apps will run on Mono unmodified, many apps will require some work on the developer's part to run smoothly on Mono. This guide will attempt to port a non-trivial open source application to document several of the issues a developer may run into while porting their app to Mono.
Thread beginning with comment 245137
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Porting?
by segedunum on Mon 4th Jun 2007 13:54 UTC in reply to "RE[4]: Porting?"
segedunum
Member since:
2005-07-06

You could just as easily say that Windows will always be behind Mono, because it also has some libraries and abilities that the Windows .NET implementation doesn't have.

Because the weight of development and installed applications behind .Net is with Microsoft and Windows. That's why the Mono people feel the need to come up with a Windows.Forms implementation (and Windows.Forms is just one part of .Net on Windows and has been deprecated in favour of Avalon remember) and why Microsoft probably hasn't even heard of GTKSharp.

Mono is continually limited in its usefulness as a cross platform environment in how much of the .Net and surrounding Windows component environment it can reproduce, in a way which will make it transparent to ported applications. That's a big, big ask, and you need an awful lot of time, developers and resources to make it feasibly achievable. Remember that Windows.Forms is just one area within .Net and Windows to be implemented by Mono, and Microsoft now recommends everyone use Avalon instead.

Basically, you're just going to be treading water at best with this approach. Trying to re-implement Microsoft's technology with the huge numbers of developers, time, resources and money that is required is not exactly the smartest move one could be doing. It's one the the weapons Microsoft uses to stop you from coming up with something that will work properly outside of Windows.

Reply Parent Score: 4

RE[6]: Porting?
by MightyPenguin on Tue 5th Jun 2007 03:25 in reply to "RE[5]: Porting?"
MightyPenguin Member since:
2005-11-18

Who says Mono has release all the same functionality 2 days after MS launches it?

Yeah with .Net 1.1 that was very true since all the foundation was being laid there, but with 2.0 it wasn't nearly as important. Many developers targeting windows used 1.1 a year or more after 2.0 came out.

I don't understand this infatuation I see over and over again with posts on here about "OMG the sky is falling cause you can't release the same features at the same time". Microsoft is not going to, and can't afford to, redesign all of .Net every two years just to mess up Mono. The base of code out there will stay largely the same with some additions here and there which are of smaller and smaller significance. Look at 3.0 it's a smaller amount of new code then 1.1 -> 2.0 and already Mono is getting support for it.

Reply Parent Score: 1