Skip to Content
avatar image
Former Member

Updated .NET Connector SDK for VS 2005?

OK, it is has been a couple years since VS 2005 has been released...any estimated availability of a new SDK/add-in? 😉

Seriously though, it is long overdue. Any plans to release an update?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • avatar image
    Former Member
    Apr 13, 2007 at 03:32 PM

    The .Net connector is being replaced by SAP ES Explorer (currently in development) or at least that's what I gather from the following article:

    http://www.sap.info/index.php4?ACTION=noframe&url=http://www.sap.info/public/INT/int/index/PrintEdition-1061945a104e313da2/0/articlesVersions-933545a0e04ec8819

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      I'm aware the ES Explorer, but as I understand, it is to invoke services, not BAPIs and RFCs. Many of the apps I need the .NET connector for will require interfacing with legacy SAP systems for which this is the only option.

      In any case, there still should be a refresh to the .NET connector just to make it install on VS 2005!

      - Rick

  • avatar image
    Former Member
    May 15, 2007 at 05:29 AM

    hi,

    Web services is the best way to connect between SAP and .Net. SAP even came up with.NET connector. .NET connector works well with vs2003 as it was developed in around 2003. but it has certain complication when working with vs2005. Web services will be good option as it does not need any .net connectors to deal with.

    check this link for more details about .net and sap connection using web services

    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/1615ef47-0a01-0010-a7a8-b8a2a7b78776 [original link is broken]

    please reward points if it is useful to u

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Rick,

      there are no plans from SAP providing VS 2005 support for the SAP Connector for Microsoft .NET, the future direction is connectivity by using Web Services, an example for providing support for this type of connectivity is the ES Explorer. However there are a couple of alternatives for connecting to older SAP releases by using VS 2005:

      - Using VS 2003 for building the proxies and using this proxies from VS 2005

      - Using BizTalk Server or XI for connecting to the SAP system and exposing this then as Web Service

      - A couple of solutions were build by smaller companies for integrating the NCo into VS 2005

      - Using a adapter solution like IQL Studio from Sitrion for connecting from VS 2005 to older SAP releases.

      Thanks,

      - Juergen

  • avatar image
    Former Member
    Mar 07, 2008 at 01:59 PM

    Hi,

    Can anybody let me know of the drawbacks or disadvantages for Enterprise explorer for .NET 2.0?

    Does the Enterprise explorer support invoking Standard/Custom BAPI's ?

    I am not able to find any material on this from the web.

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      I forgot to answer one more thing.

      The ESE is connecting to SAP Services Registry (SR) which gives him the API to Search & Browse for Services.

      I see no barrier to expose the BAPI's you are intersted on as Web Services, Publish them to the organization SR and then they will be exposed to the ESE and can be consumed as .NET Web Services.

      Regards,

      Nadav

  • avatar image
    Former Member
    Mar 10, 2008 at 08:41 AM

    Hi,

    Thanks Nadav, for the quick reply once again. So to make it clear we cannot use SAP 5.6 version or a lower version with SAP ES Explorer . The SAP config has to be a minimum of SAP Net Weaver 7.1.

    To be able to use WCF/VS 2005 and any SAP version prior to 7.1, Is .NET Connector. the only option?

    As for the webcast, I have registered for it and awating further info.

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      The answer to your question is YES.

      ESE is working against the SR (Services Registry) which exists only on Netweaver as part of the mentioned versions.

      1. SAP NW PI 7.1 (contains Integration Directory and Integration Server)

      2. SAP NW CE 7.1

      you can't use ESE on SAP 5.6 or lower versions, you need the NetWeaver stack with the SR component.

      Regards,

      Nadav

  • avatar image
    Former Member
    May 27, 2008 at 04:35 AM

    Hi Rick!

    I believe that there are still guys out there who still aren't used to web services, so in my oppinion it's OK if you stick with the old - but works - RFC way.

    Currently I'm using Visual Studio 2008, and still using RFC to interface the R/3.

    How do I do that? I generate the Remote Enabled Functions to my VS thru Softwise's SAPExplorer.

    It works well with VS 2008, but still needs a little trick to do in order to get your hands on it with VS 2008.

    Believe me 😉

    Add comment
    10|10000 characters needed characters exceeded