Re: [Mono-list] Mono and its limitations
Danny-113 wrote: You English seems pretty OK to me. To your question (which others may be able to answer with greater detail): I've been successfully writing code on Windows and running it on Linux (Ubuntu+Mono) for over a year now. It seems that the Mono guys have done a pretty good job at making a runtime that is compatible with any CLR assembly - at least those produced with current C# and VB compilers. Thank you both for your kind answers. I still have a doubt: In my application I often use serial ports or read/write access to files: how the code could successfully run either on Windows or Linux? They are quite different: for example Windows calls the serial ports COM but in Linux I have to look under /dev... So I can't understand how the same code could run on both systems. Marco -- View this message in context: http://www.nabble.com/Mono-and-its-limitations-tp22799220p22846599.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono and its limitations
On Thu, 2009-04-02 at 05:20 -0700, Marco Trapanese wrote: Danny-113 wrote: You English seems pretty OK to me. To your question (which others may be able to answer with greater detail): I've been successfully writing code on Windows and running it on Linux (Ubuntu+Mono) for over a year now. It seems that the Mono guys have done a pretty good job at making a runtime that is compatible with any CLR assembly - at least those produced with current C# and VB compilers Thank you both for your kind answers. I still have a doubt: In my application I often use serial ports or read/write access to files: how the code could successfully run either on Windows or Linux? They are quite different: for example Windows calls the serial ports COM but in Linux I have to look under /dev... So I can't understand how the same code could run on both systems. I think System.IO.Ports is available in Mono http://www.mono-project.com/HowToSystemIOPorts (I have no idea how current or out-of-date that page is). There doesn't seem to be many open bugs https://bugzilla.novell.com/buglist.cgi?quicksearch=System.IO.Ports but googling about makes it seem iffy. Port makes are arbitrary, don't hard-code them and that shouldn't be a problem. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono and its limitations
Hey, In my application I often use serial ports or read/write access to files: how the code could successfully run either on Windows or Linux? They are quite different: for example Windows calls the serial ports COM but in Linux I have to look under /dev... So I can't understand how the same code could run on both systems. .Net calls them System.IO.Ports.SerialPort. That's all you need to use to guarantee yourself cross platform code ;) Alan. Marco -- View this message in context: http://www.nabble.com/Mono-and-its-limitations-tp22799220p22846599.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono and its limitations
You can sometimes use environment paths, such as System.Environment.GetFolderPath(DesktopDirectory)... This is not always possible, though (see: http://www.go-mono.com/docs/index.aspx?link=T%3ASystem.Environment.SpecialFolder). When defining your paths yourself (and that they are the same for all OSes), make sure to define your separators the right way rather than hard coding them as anti-slashes, as that would only work on Windows (see this: http://www.mono-project.com/Guidelines:Application_Portability#Path_Separators). Also, you can fork your code if needed, like if (OS == Windows) do this, else if(...) do that, which ensures you can solve any problem you encounter. Marco Trapanese wrote: Danny-113 wrote: You English seems pretty OK to me. To your question (which others may be able to answer with greater detail): I've been successfully writing code on Windows and running it on Linux (Ubuntu+Mono) for over a year now. It seems that the Mono guys have done a pretty good job at making a runtime that is compatible with any CLR assembly - at least those produced with current C# and VB compilers. Thank you both for your kind answers. I still have a doubt: In my application I often use serial ports or read/write access to files: how the code could successfully run either on Windows or Linux? They are quite different: for example Windows calls the serial ports COM but in Linux I have to look under /dev... So I can't understand how the same code could run on both systems. Marco -- View this message in context: http://www.nabble.com/Mono-and-its-limitations-tp22799220p22847002.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono and its limitations
You English seems pretty OK to me. To your question (which others may be able to answer with greater detail): I've been successfully writing code on Windows and running it on Linux (Ubuntu+Mono) for over a year now. It seems that the Mono guys have done a pretty good job at making a runtime that is compatible with any CLR assembly - at least those produced with current C# and VB compilers. It stands to reason that they would also produce compatible assemblies with their development tools, so the reverse (Running code on Windows FW that was created on Linux+Mono) should be true as well. There have been a few small 'gotchas' but overall very easy. Marco Trapanese wrote: Hello, I'm from Italy and I'm sorry if my English is not so good. I hope it's good enough to explain whatever I'm going to say :-) I'm new to Mono and I read through the forum and the website. Anyway I'm not sure I understood all its qualities and limitations. To simplify the question, let me to use an example: I install the Mono IDE on a Windows machine and a Debian Linux one. I can develop code in VB.NET on both ones and the compiled files will be executed on both as well. I can also use my .NET third-party library (eg. http://www.dundas.com/Products/Gauge/NET/index.aspx) on Linux machines. The sentences I've just write are true? Otherwise what I can't do? I'd like to use Mono instead of Visual Basic .NET Express in order to develop cross-platform application. Thanks in advance Marco Trapanese Femtotech Italy ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
