Contact Us
×
How you can contact us:

  • Technical Assistance

    Request product support from SAP

  • Non-Technical Assistance

    Request non-product support or provide feedback on SAP Support Portal site

  1. SAP Support Portal Home
  2. Products
  3. Connectors

SAP Connector for Microsoft .NET

SAP Connector for Microsoft .NET 3.1

SAP Connector for Microsoft .NET 3.1 (NCo 3.1) allows developers to use BAPIs and remote-enabled function modules in any .NET application (inside-out). You can also access .NET components from any ABAP application by implementing an RFC server in .NET (outside-in). It's the successor of SAP Connector for Microsoft .NET 3.0 (NCo 3.0). See SAP note 3152653 for details about availability and platform requirements.

SAP Connector for Microsoft .NET 3.0

SAP Connector for Microsoft .NET 3.0 (NCo 3.0) allows developers to use BAPIs and remote-enabled function modules in any .NET application (inside-out). You can also access .NET components from any ABAP application by implementing an RFC server in .NET (outside-in). See SAP note 856863 for details about availability and platform requirements.

The main differences to NCo 2.0 are:

  • NCo 3.0 no longer distinguishes between a design time and a runtime. Instead of proxy classes and generated coding, you now program RFC calls dynamically. This has advantages (less and more easily understandable coding; robustness against changes on backend side — e.g. it is no longer necessary to re-generate the proxies and re-compile your application if the backend moves from non-Unicode to Unicode; no dependency on a fixed Visual Studio release) as well as disadvantages (no IntelliSense support; you need to know how the ABAP side looks when consuming RFMs in .NET).
  • RFC protocol is re-implemented in C#, so there is no longer a dependency on librfc32.dll. This should result in better performance, as almost no marshalling between managed and unmanaged code is necessary now.

Prerequisites

NCo 3.1

NCo 3.1 supports .NET framework versions 4.6.2 up to 4.8.1 as runtime. It requires the Microsoft C++ Runtime DLLs version 14.x (this version is contained in Visual C++ Redistributable package for Visual Studio 2015, 2017, 2019, and 2022). You can get the installer from the Microsoft download page.

 

NCo 3.0

The .NET 2.0 variant of NCo 3.0 requires the Microsoft C++ Runtime DLLs version 8.x (this version is contained in Microsoft Visual C++ 2005 SP1 Redistributables) Please see SAP note 684106 for details about downloading and installing this runtime.

The .NET 4.0 variant of NCo 3.0 requires the Microsoft C++ Runtime DLLs version 10.x (this version is contained in Microsoft Visual C++ 2010 Redistributables). You can get the installer from the Microsoft download page.

Downloads and Documentation

NCo 3.1

NCo 3.0

Documentation

  • Overview for NCo 3.1, November 2, 2022 (Adobe PDF, 106 KB)
  • Programming Guide for NCo 3.1, November 2, 2022, (Adobe PDF, 609 KB)
  • Overview for NCo 3.0, August 11, 2011 (Adobe PDF, 84 KB)
  • Programming Guide for NCo 3.0, January 16, 2018, (Adobe PDF, 539 KB)
  • Tutorial, September 25, 2018 (ZIP archive, 53 KB)

Support

Report any problems under the following components:

  • BC-MID-CON-NCO for any issues with SAP .NET Connector 3.1
    • For the .NET runtime 4.6.2  binaries support will be offered until December 31, 2028.
  • BC-MID-CON-NCO for any issues with SAP .NET Connector 3.0
    • For the .NET 4.0 variant support will be offered until October 31, 2023.
    • Note that support and maintenance for the .NET 2.0 variant ended on July 31, 2018.
  • Note that support and maintenance for SAP .NET Connector 2.0 (runtime parts) ended on March 31, 2013.
  • Note that support and maintenance for the SAP .NET Connector 2.0 Proxy Wizard for Visual Studio .NET (Visual Studio 2003) expired on December 31, 2009, due to the fact that the Microsoft Visual Studio .NET/2003 is no longer supported.