relnotes201.txt

SAP公司的erp软件相关c++的软件开发包

================================================================
SAP connector for Microsoft .NET 2.0.1
================================================================
Release Notes
================================================================

1. Installation
===============
- Uninstall previous versions of SAP connector for Microsoft .NET before you install the SAP connector for Microsoft .NET 2.0.1. 
  Also delete the "SAP Proxy" toolbox tab with all items.

- Deinstallation of SAP connector for Microsoft .NET 1.x can cause problems with Visual Studio. To fix them, execute the following command: 

  regsvr32 "%ProgramFiles%\Microsoft Visual Studio .NET 2003\Vc7\vcpackages\csproj.dll"


- This version of SAP connector for Microsoft .NET requires Visual Studio .NET 2003 Professional or higher. 
  The standard editions of Visual Studio, Visual Basic or Visual C# are not supported.

- This version of SAP connector for Microsoft .NET requires and includes a new version of the native RFC library, librfc32.dll version 6.40, 
  and a new version of the Java Connector, Jco 2.51.

- The new version of the native RFC library, librfc32.dll version 6.40, requires several Microsoft Runtime DLLs (msvcr71.dll and msvcp71.dll), 
  which are shipped with Microsoft Visual Studio .NET 2003. When deploying librfc32.dll with your applications that use .NET Conenctor, you may 
  also need to deploy the Microsoft runtime DLLs mentioned above either manually or by applying SAP Note 684106.       

- If you have problems with the installation, open a command prompt and run the installation with the following options: 
  "msiexec /l*v install.log  /i SAP.Net.Setup_2.0.msi". 
  See the install.log file for error messages and and provide this file to SAP for analysis.

- A Java VM is required to generate proxies from the SAP system. The Java VM is not required once the proxy is generated. 
  To use a Java VM other than the Sun Java VM, you need a registry key pointing to your Java VM. 
  You can copy the registry information below into a .reg file and run it to change "JavaHome" accordingly.

------------------------------------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft]

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment]
"CurrentVersion"="1.3"

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.3]
"JavaHome"="C:\\Program Files\\IBM\\Java13\\jre"
------------------------------------------------------------------------------


2. What is New (2.0.1)
======================

2.1 Support to Long, Case-Sensitive Passwords
================================================ 

Previours versions of the SAP connector for Microsoft .NET and the underlaying native RFC library (librfc32.dll) and 
Java Connector (Jco) support only passwords with a maximum length of 8 characters and convert all characters into uppercase automatically. 
As of this version, the SAP connector for Microsoft .NET supports passwords with a maximum length of 40 characters and no longer 
converts the characters to uppercase automatically. 

This change may break your existing .NET applications with a logon error when running them against a SAP server on which the ABAP kernel 
has not been updated according to SAP Note 792850.  For more information about the reasons and solution for this breaking behaviour,
see this note.

In the case your application breaks and you do not want to update the ABAP server, you either have to enter 
the password in uppercase or use the property Destination.ConvertPasswordToUppercase, which is a new property added to the class Destination 
by this version, to convert the password to uppercase when constructing the connection string. 

2.2 Runtime
===========

2.2.1 Bug fixes 

- Serveral code page conversion issues related to the following SAP code pages have been fixed
  SAP code page 1401 for Central European languages
  SAP code page 1500 for Cyrillic
  SAP code page 6300 for Japanse
  SAP code page 8340 for Traditional Chinese for Hong Kong HKSCS

- Reflection problem related to the built-in type BAPIRET1 has been fixed.
- Built-in type BAPIRETURNTable required by some BAPIs is added. 


2.3 Design Time
===============

2.3.1 Bugs fixes 

- For proxies with several functions, the following runtime error had occured under certain circumstances: "Method xyz can not be reflected."
- The SAP wizard table did not work. Existing tables are not recognized.
- SAPRouter string was not correctly used when during proxy generation.
- When using SAP Server Explorer with Unicode SAP system, VisualStudio crashed.


3. What is New (2.0)
====================


3.1 Runtime
===========
- The old SAP connector for Microsoft .NET assembly was split into two assemblies. The new SAP connector for Microsoft .NET assembly is now free 
  of unsafe code and can be used in partial trusted environments. 
- Support for ".NET Remoting".
- New unified connection management for both Rfc and Soap connections.
- Improved "Destination" classes, for example new "Properties" for Soap support, for SAPRouter strings and the new "CombinedDestination" 
  and "ConfigDestination" classes.
- Improved connection pool allows, for example, the limitation of active connections.
- Support for RFC callbacks



3.2 Design Time
===============

- Full Visual Basic