Linked by Eugenia Loli on Wed 15th Mar 2006 16:41 UTC, submitted by M-Saunders
Mono Project What makes a Mono developer tick? Linux format has a brief interview with Edd Dumbill and Niel Bornstein, two prominent Mono coders who've just written a book on the open source .NET implementation. They explain the advantages of C# over other languages, and give a bit of advice for budding Mono app developers.
Thread beginning with comment 104843
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: WinForms
by umccullough on Thu 16th Mar 2006 00:28 UTC in reply to "RE: WinForms"
umccullough
Member since:
2006-01-26

Usually when I go find a winforms app to test in mono - it's NOT winforms support that is lacking - but usually something else. Many of the apps I try to run under mono just simply die with no error in the console (even with verbose and debug output on)

Mono is still missing some non-winforms support that prevents many VStudio-built apps from running properly.

But otherwise, I love the project, and I try out new versions when they're available!

Reply Parent Score: 2

RE[3]: WinForms
by nzjrs on Thu 16th Mar 2006 02:47 in reply to "RE[2]: WinForms"
nzjrs Member since:
2006-01-02

I agree. Its usually stupid little things like people hard coding path seperators (/ vs ) and network stuff (have to run as sudo).

But on the whole I agree that mono is there in most part (and getting there) for the rest.

Its the damn 80/20 rule - 80% of the work takes 20% of the time!

Reply Parent Score: 1

RE[4]: WinForms
by calberto on Thu 16th Mar 2006 08:31 in reply to "RE[3]: WinForms"
calberto Member since:
2006-01-30

I agree. Its usually stupid little things like people hard coding path seperators (/ vs ) and network stuff (have to run as sudo).

Well, we need to know such things to fix them. You use it, it fails, we fix it. A lot of times, the documentation in msdn is not very clear, and we have to make some assumptions, and have a first implementation. Then, when colaborators come and use the code, we have the chance to know if the implementation is wrong.

That's one of the problems implementing a compatible product of MS ;-)

Reply Parent Score: 1