on 07-08-2004 8:58 AM
The SAP .NET Connector uses either RFC or SOAP to communicate with the SAP Application server.
Is for this communication any other library necessary besides the generated proxy.DLL and the SAP.Connector.dll.
I mean, is the <b>librfc32.dll</b> (that can be used with C++ to connect via RFC to SAP) somehow necessary for the .NET Connector or is all funtionallity within the proxy.dll and SAP.Connetor.dll ?
Thanks
elko
Hi,
The .NET Connector requires librfc32.dll version 62XX.xxx or higher and makes calls to the native functions over PInvoke.
Regards,
Guangwei
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi another question regarding LIBRFC32.dll:
I use the LIBRFC32.dll as an entrypoint DLL in VB6.0 (using Keyword DECLARE).
But now I found out, the DLL is also usable as COM Component (see Dependency Walker utility).
How is that ? Who uses the COM functionallity and where is the documentation.
Which type (COM / entrypoint) is used by the .NET Connector for the RFC communication?
elko
Hello,
Librfc32.dll also contains some undocumented COM components for SAP internal use. For example, a part of the DCOM Connector is implemented inside this DLL. Just as already answered before, the .NET Connector use the dll through PInvoke, similar to what you use with VB6.
Regards,
Guangwei
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.