[Mono-list] SerialPort access

Kornél Pál kornelpal at gmail.com
Mon Oct 2 09:07:44 EDT 2006

Microsoft .NET Framework has releases: 1.0, 1.1, 2.0. Note that 3.0 is 
exactly the same as 2.0 but contains some more components.

Each release has different set of functionality.

Mono is released as a single product that contains support multible 
framework versions. Profile 1.0 is intended to be compatible with MS.NET 1.1 
and profile 2.0 is intended to be compatible with MS.NET 2.0.

If you compile you code using MS csc 1.0, 1.1 or Mono mcs it will use 
profile 1.0. If you compiler your code using MS csc 2.0 or gmcs it will use 
profile 2.0. Also note that you can use .config files to override this 
default behavior.


----- Original Message ----- 
From: "Brown, Robert" <rpbrown at GAIC.COM>
To: "Gert Burger" <gburger at cs.up.ac.za>; "Kornél Pál" <kornelpal at gmail.com>
Cc: <mono-list at lists.ximian.com>
Sent: Monday, October 02, 2006 2:52 PM
Subject: RE: [Mono-list] SerialPort access

What is profile 2.0?


-----Original Message-----
From: mono-list-bounces at lists.ximian.com 
[mailto:mono-list-bounces at lists.ximian.com] On Behalf Of Gert Burger
Sent: Monday, October 02, 2006 8:14 AM
To: Kornél Pál
Cc: mono-list at lists.ximian.com
Subject: Re: [Mono-list] SerialPort access

Kornél Pál wrote:
>> I have looked at the System.IO.Ports but have failed to incorporate
>> it with out app(a combination of monodevelop and mcs crashes).
>> Are there any other method to do this or have someone incorporated
>> System.IO.Ports into an .NET v1.x app?
> Why don't you use profile 2.0?
> That way you can use System.IO.Ports on Mono and MS.NET as well
> without any hacks.
> Kornél
I tried this and it seems not to complain. For some reason I did not know 
about the 'profiles' in monodevelop.

Thanks, all sorted, for now.

Gert Burger

Computer Science Department
University of Pretoria

Mono-list maillist  -  Mono-list at lists.ximian.com 

The content of this e-mail message and any attachments are confidential
and may be legally privileged, intended solely for the addressee. If you
are not the intended recipient, be advised that any use, dissemination,
distribution, or copying of this e-mail is strictly prohibited.  If you
receive this message in error, please notify the sender immediately by
reply email and destroy the message and its attachments.

More information about the Mono-list mailing list