Quote:
Originally Posted by Toxaris
We are there yet to be honest. Mono is quite stable and MS has been contributing to it for quite a while. The newer and really fancy .Net functions are not yet into Mono, but most programs can run on Mono without much trouble. It is usually not the support in Mono that is the problem, but the programmer... For example hard-coding slashes instead of using DirectorySeperator and things like that. If you program smart, you can compile on Windows and run it on Linux/OSX. In fact, most of my programs run on Linux/OSX without me altering anything. There is one that won't run, but that is due to an external factor, not Mono.
|
That
is good news, and I'm delighted to hear it.
Any general idea of things that work in .NET under Windows, but don't yet work under Mono? What sort of constructs are problems?
Quote:
I am looking forward to .Net Core, but it will not help ignorant programmers that hard code things.
|
Directory separators have been a bane of my existence for decades, and it's nice the language runtime has constructs you can use to let the runtime figure out the proper usage on the platform the code is running on and do the right thing.
Getting programmers to Do the Right Thing is beyond the reach of language designers.

______
Dennis