cdholding image

comm64 home
comm64 download
comm64 forum
buy comm64

Introduction
Install Comm64
Why Not MsComm?

Properties
   .Break
   .CDHolding
   .CommEvent
   .CommPort
   .CTSHolding
   .DSRHolding
   .DTREnable
   .EOFEnable
   .Handshaking
   .InBufferCount
   .InBufferSize
   .Input
   .InputLen
   .NullDiscard
   .OutBufferCount
   .OutBufferSize
   .OutPut
   .ParityReplace
   .PortOpen
   .RThreshold
   .RTSEnable
   .Settings
   .STHreshold


Comm64 Properties
   .RxTimeout
   .TxTimeout

Comm64 Functions
   .readBytes
   .readString

   .writeBytes
   .writeString
   .PortExists

OnComm Event

Hardware/Cables etc
Loopback test plug

Use Comm64 DLL to quickly add Serial Communications capabilities to your .Net applications.

Comm64 is a .Net component which, as the name suggests, is capable of operating in native 64bit mode. But you can also build it into .x86 and 'AnyCPU' projects where it'll operate in whatever mode your own application is targetting. We've provided fully functional sample projects in VB 2005 and c# 2005 to show it's compatible with older versions of visual studio. Our sample projects upgrade just fine to VS2008 and VS2010

Comm64 is compatible with MSComm32 in that it uses the same property names, methods and syntax which means that you can quickly add Comm64 to a .Net project using the same syntax that you're used to using with MSComm32

If you've already got a .Net solution which relies on MSComm32 then you shouldn't have too much trouble removing MSComm and replacing it with Comm64

        

Comm.CommPort = 23
Comm.Settings = "9600,n,8,1"
Comm.PortOpen = True

Comm.Output = "Hello World"

Do While Comm.InBufferCount > 0
     Text1.Text = Text1.Text & Comm.Input
Loop

Comm.PortOpen = False

'// Simple ?
 

'// Use ANY com port
'// Setup the com port
'// Open the com port

'// Send some data

'// Is there any incoming data ?
'// Receive data

'// Close the port

But why not use MSComm32 ?

  
MSComm32 is NOT a .Net component. It's a 32bit OCX. You can use OCX components in .Net projects but .Net Interop wraps them to make two DLL files which you deploy to your users.

Wrapped 32bit ocx components will of course fail if any attempt is made to use them in 64bit mode. (Or 'AnyCPU' mode on a 64 bit OS)

 

 

 
Apart from the problems mentioned above - Anyone who has used MSComm32 for even a short length of time will have identified a number of shortcomings - For example. MSCom only supports comports 1 to 16.

But serious developers will eventually notice other, more problematic, 'features' where applications become unresponsive or appear to 'freeze' for extended periods (or forever !) as well as unexplained data loss etc. More Info >

 
 
Copyright (c) 2010 Axis Controls Ltd