function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
matt_wmatt_w 

Partner WSDL generates code that doesn't match the API docs - it's missing the SForceService class

I am getting started on experimenting with SalesForce.com integration, and imported the Partner WSDL to start playing with it.  When I add a Service reference to the partner.wsdl (Partner Web Services API Version 20.0) I get a dll that contains a class SoapClient but the API docs suggest I should have a SForceService class.  

 

The SoapClient does seem to have the methods necessary to interact with SalesForce.com, but the methods don't match the methods listed in the API.  For example SoapClient has the following method:

 

 

public DescribeGlobalResult describeGlobal(SessionHeader, CallOptions, PackageVersion[])

 

 

whereas the API seems to say the method should be

 

DescrineGlobalResult describeGlobal();

 

I can't help but think I imported this wrong somehow and am going down the wrong path.  Can anyone suggest where I may have gone wrong?

SuperfellSuperfell

Add Service Reference generates a WCF based client, the samples are based on the older web services stack in .NET, and require you to do add web reference instead (last time i looked, there was a button to add web reference from the add service reference dialog)
PaladyrPaladyr
I had this problem. I'm using Visual Studio 2008 and you have to go to add service reference, then click the advanced button, and then you can add a web service there. When you try to add it as a service reference only you encounter this problem.