Are you porting an old VB6 application to .NET ? If your VB6 application relies on Microsoft's MSComm OCX then many developers tell us that Microsoft's MSComm32 OCX prevents their application building and deploying. Of course 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. But 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) Our brand new Comm64 component is a proper .Net component written in C# targetting the .Net framework 2.0 Our Comm64 component is quite happy stepping back to run on a 32bit x86 application as well as native 64 mode. Comm64 gives you all the old MScomm32 properties, methods and syntax in a proper .Net component which can be used in 32bit, 64bit and 'AnyCPU' modes.
Requirements:
Development environment IDE capable of using .NET components. for example MS Visual Studio 2005 or above
Limitations:
Fully functional in the development environment only
Comments not found