FiveTech Software tech support forums

by **angelo.c** » Wed Jul 08, 2009 12:39 pm

Hello All

I was wondering if anyone has had some success in using the Class SerialPort in the System.IO.Ports Namespace
using FWH CreateObject(...) routine.

I have used the following with success:
//The following all work
//cTry := "ScriptPW.Password"
//cTry := "ADODB.Connection"
//cTry := "CDO.Message"
//cTry := "Wscript.Shell"
//cTry := "InternetExplorer.Application"
cTry := "OUTLOOK.APPLICATION"
try
oLoc := CreateObject( cTry )
catch
MsgAlert("Error from Try/Catch: CreateObject( " + cTry + " ) ")
end

with:
FWH 9.05
xHarbour Compiler build 1.2.1 (SimpLex) (Rev. 6406)
Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland

I have tried with NO success the following:
CreateObject("System.Serialport"), CreateObject("System.IO.Ports"), CreateObject("SerialPort" ),
CreateObject("System.ComponentModel.component.SerialPort"), CreateObject("SerialPort.application"),
CreateObject("System.IO")

Does anyone know the correct string to use?

For background information I have provided the following which is extracted from:
MSDN .NET Framework Developer Center at:
http://msdn.microsoft.com/en-us/library ... lport.aspx

SerialPort Class
Represents a serial port resource.

Namespace: System.IO.Ports
Assembly: System (in System.dll)

[SNIP]

Remarks
Use this class to control a serial port file resource. This class provides synchronous and event-driven I/O, access to pin and break states, and access to serial driver properties. Additionally, the functionality of this class can be wrapped in an internal Stream object, accessible through the BaseStream property, and passed to classes that wrap or use streams.
[SNIP]

Best Regards,
Angelo.c

by **byron.hopp** » Mon Jul 13, 2009 3:10 pm

I believe that the problem is that CreateObject is used to create a comm object, and you are attempting to create this object from a dot.net namespace. I don't think this is going to work. I have not been on this board for a while but I don't believe that FiveWin supports the dot.net framework. In fact many people probably use FiveWin just to avoid the dot.net framework :-)

Thanks,

Byron...

by **angelo.c** » Sun Jul 19, 2009 3:29 am

Hello all.

Firstly, Thanks Byron for your reply. It confirmed what I thought. However I think it is still useful to access DOT.NET from FWH and so the following .....

Since I last posted this question on this forum for access to MS .NET from FiveWin, I have been working on it. I have established a way that works for me. It is not elegant. It requires a few steps, but it works for me. I would like to return some hopefully useful information to the FiveWin community as all of you have help me a lot in solving and getting new ideas/approaches for my application. In sharing my approach with everyone, I hope that it too could be useful to you. I specifically asked for "SerialPort" help since I am writing a custom hosting interface between a PC and a USB device (in my case, a Bar Code Reader ... essentially a USB interface is a serial port ... see: http://msdn.microsoft.com/en-us/library/aa908437.aspx ).

I use Windows XP Pro. I have download FWH 9.06 and use the supplied xHarbour and Borlandc c/c++ compiler for all my "normal" application developement. This approach should work for previous versions of FWH. For the DOT.NET interface, I use the supplied Harbour/[x]Harbour MS libraries and headers with Visual Studio 2008 c/c++ compiler and linker.

I apoligise for the length of the post but I think the detailed information would be useful to someone.

------------------------------------------------------------------------------------------------------------
In General, the step taken are as follows:
(1) Write a c/c++ wrapper that interfaces with Harbour/[x]Harbour.
I called this module: XBase_IF.cpp
This takes care of the communication between FWH source and low level c/c++ code.
Use the FWH supplied Borland C++ V5.5.1 for Win32 compiler/linker on this module.

(2) Use a MS compiler/linker that *suports* DOT.NET. Earlier versions of Visual c/c++
do not support it. (here is where you write your c/c++ code to communicate with
DOT.NET namespaces and classes
I called this module: cfuncs_vs.cpp

(3) Write your cfuncs_vs.cpp "DOT.NET interface c/c++" code that accesses DOT.NET and
compile with the /clr compiler option.
Use Multi-threaded DLL (/MD) for the runtime library.
Ensure your targetted Framework is .NET Framework V2.0 or above.
Set to generate a DLL (/DLL linker option). I generate a STATIC DLL which means I
link in an import library with the FWH code. I think this is the easiest and safest
way to interface with my FWH code.

(4) Now generate an Import Library from the generated DLL file suitable to link in with FWH.
Use the impdef and implib routines to generate an OMF formatted library from the DLL that
lists/defines all the exported functions in the DLL. Execute the following
impdef cfuncs_vs.def cfuncs_vs.dll
implib cfuncs_vs.lib cfuncs_vs.def

(5) Include "cfuncs_vs.lib" in your make/build file that generates your FWH application

(6) If all goes well there are no unresolved symbols and an .exe file is generated.

(7) That's it. Hopefully you made sense of "this general recipe". In any case I have included
a cut down version showing all the above steps that actually compiles and links on my system
--------------------------------------------------------------------------------
Step (1) Harbour/[x]Harbour c/c++ wrapper source code

Code: Select all Expand view: // =========================================================================== // XBase_IF.cpp July 2009 Angelo C // ============================1=============================================== #include <winten.h> // More includes than necessary for this cut down version. #include <stdio.h> // My complete code needs #include <Winsock2.h> #include <stdlib.h> #include <malloc.h> #include <lm.h> #include <Icmpapi.h> #include <Windows.h> #include <psapi.h> #include "hbapi.h" //Need so that FWH can pass parameters back/forth #include "hbapirdd.h" //btween XBase and c/c++ code #include "hbapierr.h" #include "hbapiitm.h" #include "hbvm.h" #include "hbset.h" #ifdef __cplusplus extern "C" { #endif // Prototypes for function in the cfuncs_vs DLL. Also used for accessing DOT.NET framework extern int TEST_NAMESPACE_in_DLL(); //This routine is called from FWH as: TEST_NAMESPACE() HB_FUNC( TEST_NAMESPACE ) { int nResult; OutputDebugString_c("\nIn routine: HB_FUNC( TEST_NAMESPACE ).\n"); nResult = TEST_NAMESPACE_in_DLL(); OutputDebugString_c(Int2Hex((unsigned int) nResult)); } #ifdef __cplusplus } #endif

Part output from my make file is below:

--------------------------------------------------------------------------------

Steps (2) and (3) Write your cfuncs_vs.cpp "DOT.NET interface c/c++" code

stdafx.h : include file follows:

Code: Select all Expand view: // stdafx.h : include file for standard system include files, // or project specific include files that are used frequently, but // are changed infrequently // #pragma once // The following macros define the minimum required platform. The minimum required platform // is the earliest version of Windows, Internet Explorer etc. that has the necessary features to run // your application. The macros work by enabling all features available on platform versions up to and // including the version specified. // Modify the following defines if you have to target a platform prior to the ones specified below. // Refer to MSDN for the latest info on corresponding values for different platforms. #ifndef WINVER // Specifies that the minimum required platform is Windows Vista. #define WINVER 0x0600 // Change this to the appropriate value to target other versions of Windows. #endif #ifndef _WIN32_WINNT // Specifies that the minimum required platform is Windows Vista. #define _WIN32_WINNT 0x0600 // Change this to the appropriate value to target other versions of Windows. #endif #ifndef _WIN32_WINDOWS // Specifies that the minimum required platform is Windows 98. #define _WIN32_WINDOWS 0x0410 // Change this to the appropriate value to target Windows Me or later. #endif #ifndef _WIN32_IE // Specifies that the minimum required platform is Internet Explorer 7.0. #define _WIN32_IE 0x0700 // Change this to the appropriate value to target other versions of IE. #endif #define WIN32_LEAN_AND_MEAN // Exclude rarely-used stuff from Windows headers // Windows Header Files: #include <windows.h> // TODO: reference additional headers your program requires here

--------------------------------------------------------------------
[

dllmain.cpp Source Follows:

Code: Select all Expand view: // dllmain.cpp : Defines the entry point for the DLL application. #include "stdafx.h" BOOL APIENTRY DllMain( HMODULE hModule, DWORD ul_reason_for_call, LPVOID lpReserved ) { switch (ul_reason_for_call) { case DLL_PROCESS_ATTACH: case DLL_THREAD_ATTACH: case DLL_THREAD_DETACH: case DLL_PROCESS_DETACH: break; } return TRUE; }

--------------------------------------------------------------------

cfuncs_vs.cpp "DOT.NET interface c/c++" Module follows:

Code: Select all Expand view: // =========================================================================== // c_funcs.cpp July 2009 Angelo C. // ============================1=============================================== // cfuncs_vs.cpp : Defines the exported functions for the DLL application. // This is CALLED from other C/C++ modules which can be compiled by Borlandc // which interfaces with FWH/[x]Harbour source directly using hb_parYYYY, etc functions // NOTE. Function names that are called from the Borlandc c/c++ wrapper routine MUST HAVE // an underscore "_" included at the start of the name. // Borlandc puts this in automatically. // SUMMARY. Put "_" at start of routines called from Borlandc Wrapper module #include "stdafx.h" #define CFUNCS_VS_API __declspec(dllexport) using namespace System; // Routine converts system strings to another type // compile with: /clr #include <string> #include <iostream> using namespace std; using namespace System; void MarshalString ( String ^ s, string& os ) { using namespace Runtime::InteropServices; const char* chars = (const char*)(Marshal::StringToHGlobalAnsi(s)).ToPointer(); os = chars; Marshal::FreeHGlobal(IntPtr((void*)chars)); } void MarshalString ( String ^ s, wstring& os ) { using namespace Runtime::InteropServices; const wchar_t* chars = (const wchar_t*)(Marshal::StringToHGlobalUni(s)).ToPointer(); os = chars; Marshal::FreeHGlobal(IntPtr((void*)chars)); } //---------------------------------------------------------------- #ifdef __cplusplus extern "C" { #endif #using <System.dll> //A Test for this namespace CFUNCS_VS_API int _TEST_NAMESPACE_in_DLL() { string a = "test"; OutputDebugStringA("\nIn (TEST_NAMESPACE_in_DLL(...): "); using namespace System; using namespace System::IO::Ports; using namespace System::ComponentModel; array<String^>^ serialPorts = nullptr; try { // Get a list of serial port names. serialPorts = SerialPort::GetPortNames(); } catch (Win32Exception^ ex) { OutputDebugStringA("\nError: ex->Message: "); MarshalString(ex->Message, a); OutputDebugStringA(a.c_str()); } OutputDebugStringA("\nThe following serial ports were found:"); // Display each port name to the console. for each(String^ port in serialPorts) { MarshalString(port, a); OutputDebugStringA(a.c_str()); } } //Function prototype descriptions for Windows API functions // lpOutputString is a pointer to string to be displayed in debug window WINBASEAPI VOID WINAPI OutputDebugStringA( LPCSTR lpOutputString ); // Converts an integer (2 or 4 bytes) into a hex string ( 4 or 8 chars) CFUNCS_VS_API char * _Int2Hex_dll( unsigned int wWord ) { static far char sIntHex[ 17 ]; WORD i; if (sizeof(int) == 4) //Platform has 4 byte represenattion for int { i = 9; do { sIntHex[ i ] = 48 + ( wWord & 0x000000000000000F ); if( sIntHex[ i ] > 57 ) sIntHex[ i ] += 7; wWord >>= 4; } while( i-- > 0 ); sIntHex[ 16 ] = 0; } else //Platform has 2 byte represenattion for int { i= 3; do { sIntHex[ i ] = 48 + ( wWord & 0x000F ); if( sIntHex[ i ] > 57 ) sIntHex[ i ] += 7; wWord >>= 4; } while( i-- > 0 ); sIntHex[ 4 ] = 0; } return sIntHex; } /* ============================================================================ * OutputDebugStringCR_DLL( cStr ) * * Purpose: * Send a string the the system debugger window WITH <CR>+<LF> printed first * ========================================================================= */ CFUNCS_VS_API void _OutputDebugStringCR_DLL(char * cMsg) { OutputDebugStringA("\n"); OutputDebugStringA(cMsg); } #ifdef __cplusplus } #endif

Build Log Output from Visual Studio 2008:

--------------------------------------------------------------------------------
Step(4)

Result from impdef and implib calls.

--------------------------------------------------------------------------------
Step(5)

Output from my make file:

--------------------------------------------------------------------------------
Step(6)

Debug Ouput (in the debug window) from my call to TEST_NAMESPACE()

[/list][/list]
--------------------------------------------------------------------------------
There you have it.

Best Regards,
Angelo.c

by **anserkk** » Mon Jul 20, 2009 4:16 am

Dear Mr.Angelo

Very useful information. Appreciate your effort.
You have shown a very good and detailed example. Once again thank you

Regards
Anser

by **jfl@mafact.com** » Sat Mar 03, 2012 12:19 pm

Nice job, Thanks to you

by **Antonio Linares** » Sat Mar 03, 2012 1:01 pm

Angelo,

Here you can see how FiveNet access to .NET:

http://code.google.com/p/fivenet/wiki/architecture

This way you can use C#, etc for your .NET code, and easily access it from FWH/Harbour :-)

FiveTech Software tech support forums

SerialPort Class Using CreateObject (...)

SerialPort Class Using CreateObject (...)

Re: SerialPort Class Using CreateObject (...)

Re: SerialPort Class Using CreateObject (...)

Re: SerialPort Class Using CreateObject (...)

Re: SerialPort Class Using CreateObject (...)

Re: SerialPort Class Using CreateObject (...)

Who is online