[.net] First post

Hey, I just found this forum.

odd no one seems to know about it, as .net will be huge. :)

The biggest thing I've tested mono with was a asp.net DB tester app , and it worked perfectly, which is a very good thing :) - and I've been told even directx is handled properly.. (havn't tested this however).

.net is good. tis very good. Especially .net CF. :)

Quote:

Original post by RipTorn odd no one seems to know about it, as .net will be huge. :)

It was created 2 hours ago [grin]

lol

ops :)

I was under the impression it was created when the forum was upgraded :)


But yes. good. .net is good.

:)


ok. I'll try and be more coherent in my next post.

I haven't used Mono too much, but from my experience, it performs favorably, and I've seen videos of it in action, and it worked quite well (the video was from some Novell conference or something, I don't remember exactly).

Currently the main problem with Mono is its lack of a really usable Windows.Forms

Windows.Forms is a library which M$ designed to be as close to user32.dll as possible, presumably to improve performance and make implementation on win32 easier. Unfortunately it's proved a problem for third party implementations on non-win32 platforms.

I hope they will soon have it sorted.

Of everything else, it basically works unless you use really obscure stuff, P/Invoke win32 DLLs (although there may be some support for this), or use APIs which don't exist in Mono (mainly Microsoft.* ?)

Mark

Last time I looked (about a month ago), the TextBox control didn't have a .Text property, though it was listed at 77% done. I think that may give you some indication.

ld

Quote:

Original post by markr Currently the main problem with Mono is its lack of a really usable Windows.Forms Windows.Forms is a library which M$ designed to be as close to user32.dll as possible, presumably to improve performance and make implementation on win32 easier. Unfortunately it's proved a problem for third party implementations on non-win32 platforms. I hope they will soon have it sorted.

They should focus on WinFX more, since that breaks with Win32 more cleanly, and promote Gtk# as the portable option in the interim.

Quote:

Original post by liquiddark Last time I looked (about a month ago), the TextBox control didn't have a .Text property, though it was listed at 77% done. I think that may give you some indication.

Yes, of their level of Windows.Forms implementation. Oh, wait, they stated that it is far from complete. Hmmm...

Knee-jerk reactions are exactly that: jerk reactions.

Quote:

Original post by Oluseyi Yes, of their level of Windows.Forms implementation. Oh, wait, they stated that it is far from complete. Hmmm... Knee-jerk reactions are exactly that: jerk reactions.

If you're using .NET for anything and not leveraging WinForms, you don't know what you're doing. That's just my opinion, but I've been working with the tech professionally for nearly 2 years now, so I know of which I speak.

ld

Quote:

Original post by liquiddark Quote: Original post by Oluseyi Yes, of their level of Windows.Forms implementation. Oh, wait, they stated that it is far from complete. Hmmm... Knee-jerk reactions are exactly that: jerk reactions. If you're using .NET for anything and not leveraging WinForms, you don't know what you're doing. That's just my opinion, but I've been working with the tech professionally for nearly 2 years now, so I know of which I speak. ld

And what does that have to do with what you quoted from Oluseyi?