cancel
Showing results for 
Search instead for 
Did you mean: 

.NET Connector in VS'2005

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

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)

Former Member
0 Kudos

Hello Anne & Reiner,

thanks for your PDF with integration steps for usage in VS 2005!

Good work

Regards,

Richard

Former Member
0 Kudos

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,

rima-sirich
Advisor
Advisor
0 Kudos

Hi Gregory,

Here is what are you looking for:<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/92333e6b-0b01-0010-9cbf-fecd62d6c895">Using SAP Connector for MS .NET in Microsoft Visual Studio 2005</a>.

Regards,

Rima

Former Member
0 Kudos

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?