[Mono-list] Mono and its limitations

[Danny]

All of the answers so far are right on.  And it's funny that you should 
ask about those specific things because right now that's about ALL my 
application does.  It polls data from COM ports (soon to be USB ports 
too) and stores it in a home-grown XML data store, which makes heavy use 
of streams for file read and write access.  Other than that it also 
provides a client interface via remoting, which is the only part I had 
any portability issues with.

For things such as you mention - port names and file paths - I push them 
out to configuration where the 'platform-specificness' of them doesn't 
matter.

Hope that helps,
Danny

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
>