Serial Communication (Com1)

  • Thread starter Thread starter mphanke
  • Start date Start date
M

mphanke

Hi,

please don't tell me there is no other posibility to access the serial
port than using the createfile(...) func?
I was so convinced of .NET until this! Can somebody please provide me
with an answer, which shows I'm wrong!?!

Martin
 
mphanke said:
Hi,

please don't tell me there is no other posibility to access the serial
port than using the createfile(...) func?
I was so convinced of .NET until this! Can somebody please provide me
with an answer, which shows I'm wrong!?!

Martin
Click to expand...


The .Net Framwork v1.1 doesn't include a communications class library...

BUT, you can use MSCOMM from visual basic 6 in .Net

Look at this like for details:
http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=320

I'm using this method in one of my projects and it seems to be running
smoothly.

Jamie
 
mphanke said:
Hi,

please don't tell me there is no other posibility to access the serial
port than using the createfile(...) func?
I was so convinced of .NET until this! Can somebody please provide me
with an answer, which shows I'm wrong!?!

Martin
Click to expand...
In this version It's the only way.
 
Hi Martin,

Beside the community's reply, I will provide you another MSDN article about
serial port communication, FYI:
"Use P/Invoke to Develop a .NET Base Class Library for Serial Device
Communications"
http://msdn.microsoft.com/msdnmag/issues/02/10/netserialcomm/

The more I want to point out is that, if you want to specify Serial Ports
larger than COM9, you need different syntax, please refer to:
http://support.microsoft.com/default.aspx?scid=kb;[LN];115831

Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi Martin,

Does our reply make sense to you? Do you still have concern on this issue?

Please feel free to feedback. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi,

decided to use the P/Invoke solution. It works pretty good! Eventhough
it was a little bit hard in the beginning to figure out why the COM1 and
the LCD where not talking with eachother [Dough...] but you shouldn't
communicate Unicode with this type of hardware ;-)

Thanks for your help,

Martin
 
Hi Martin,

Thanks for your feedback.

I am glad we can help you. If you need further help, please feel free to
post.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Back
Top