on 05-12-2009 9:44 PM
I have an application that runs with SAP .Net connector 2.0 built with Visual studio 2003. I read somewhere that says ES Explorer is the replacement especially if you use VS 2008.
Is ES Explorer compatible with our current SAP setup below (provided by our BASIS group)?
EA-APPL 110
EA-FINSERV 110
EA-GL_TRADE 110
EA-HR 110
EA-IPPE 110
EA-PS 110
EA-RETAIL 110
PI_2004_1_470
PI_BASIS_2006_1_2006
SAP_ABA 620
SAP APPL 470
SAP BASIS 620
SAP HR 470
SAP IS-U/CCS 471
SAP KERNEL 6.40 EX2 64-BIT
some people saying this because .net connector is not supporting VS.net2008
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
you can still use the NCo but you would have to build the proxies in VS 2003, they can then be used in VS 2008. The problem is the design time component, it's only supporte din VS 2003 whereas the runtime component also works in newer VS releases. As an alternative you can use the WCF LOB Adapter from Microsoft, it works directly from VS (it's branded as BizTalk but BizTalk is not required), it uses RFC/BAPI for accessing the SAP system. You can find more information at http://www.microsoft.com/downloads/details.aspx?familyid=F3EA0659-B0ED-4D5A-891E-53268128A5F0&displa....
- Juergen
Hello Teo,
ES Explorer for .NET doesn't replace SAP .NET Connector as RFC-based connector. ES Explorer for .NET is the next generation of connectors based on SOA architecture. You can read more ES Explorer for .NET related content [here|https://www.sdn.sap.com/irj/sdn/dotnet?rid=/webcontent/uuid/60b5ac7e-94a9-2b10-a4a8-90417051e216] [original link is broken];.
Best Regards,
Rima.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.