on 05-25-2006 12:50 PM
Hi all,
to answer the numerous questions regarding .NET Connector in VS'2005, Reiner Hille-Doering and myself have prepared a guide that describes how to implement a workaround to use the connector in VS'2005.
The guide is available on the main .NET Interoperability page. Enjoy!
Regards,
Anne and Reiner
All,
I believe [Softwise SAPExplorer|http://www.softwise.com.ar/products.php] could be an alternative for those who don't want to use VS 2003 anymore! This Add-On can be used not only with VS 2005 but also VS 2008.
(please reward point if usefull)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Anne & Reiner,
thanks for your PDF with integration steps for usage in VS 2005!
Good work
Regards,
Richard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I am currently looking for a solution to use .Net Connector with VS 2005. However, apart from SAP Proxy Generator Add-in for VS 2005, I didn't find something.
Could you please give me the link to the documentation you are talking about?
Thanks in advance.
Best regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have been using the workround to have SAP .NET Connector work in VS 2005 and it has been OK until now.
I have a problem where the ABAP RFC throws an exception. With VS 2003, this would be caught by catch(SAP.Connector.RfcAbapException ex) but with 2005, this does not work and the exception is caught by catch (System.Exception ex) and gives the message "Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx". Is there an updated SAP .NET Connector 2 or a workround?
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
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.