on 09-30-2004 9:33 AM
The final version of SAP .NET Connector 2.0 is available for all SAP customers for download from
http://service.sap.com/connectors
Note that Visual Studio 2003 Professional (or higher) is required - pure Visual Basic or Visual C# will work, but only in the "Profession" edition (for the case that this is available).
Compared to the Beta there is not a lot of change in it - mostly bug fixes. Compared with 1.x version, there is a lot of new features that are described in the Release Notes or in my former posts.
Hello Reiner:
Where can novices in .NET connector can find information (manuals, white papers, newsletters, notes, etc) to begin using and what is more important, to use apropriately the 2.0 version?
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Reiner,
I could not see the 'run time' version of it for deployment server. Is there a plan to provide it later ?
cheers
Ramesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The runtime installer is planned to available later.
For inhouse-use you can freely distribute everything you need to run your .NET Connector based applications.
This is normally:
-Your application files
-SAP.Connector.DLL or SAP.Connector.Rfc.DLL (install to app dir or GAC)
- LIBRFC32.DLL 6.20 or higher (install best to System32).
Note that from 6.40 the file LIBRFC32.DLL is compiled using Visual Studio 2003, which adds a couple of DLL dependencies that earlier versions of LIBRFC32.DLL do not have.
This is not a problem if the target PC already has SAPGUI 6.40 installed, but if not, there is a good chance you'll need to install the additional DLL files as well.
There is an OSS note that describes this situation, which points to a special setup program to install just the missing DLL's. Can't remember what the note number is.
Scott
Librfc32 contains some COM inproc server, but this is not used for .NET connector - so it would work have it side-by-side in your app dir.
Unfortunately there is some special feature in LIBRFC32 (I don't remember, I think it was some shared memory usage) that could anyway can cause serious problems if you have more then one LIBRFC32 on your machine. So SAP strongly recommends to put it to System32 - and promises that all LIBRFC32 version are backward compatible.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.