Can't instantiate XOA

Hello,

I'm trying to consume the web service in C#, and the XOA is not a valid class. I'm using http://premconn.premiereconnect.com/2007/02?WSDL. I have both the downloads for the sample authenticate C# projects, but even when I refresh the WSDL, XOA is removed from the sample app.

Can someone please help me?

Find more posts tagged with

Comments

skamens

I recommend looking at our sample project for Authenticate - you can find it here: https://apiforums.easylink.com/content/c-sample-authenticate-complete-project.

I suggest using the sample that is marked for the 2.5 version of the API (in this zip file: https://apiforums.easylink.com/system/files/CSharp_Authenticate 2.5.zip).

Note that with the current versions of the software, the different API functions are broken up into separate namespaces. You can find a full list of the different namespaces here: https://apiforums.easylink.com/emapidocs/25/Introduction/Namespaces.html. You should also be sure to look at our API documentation - the site for the 2.5 version is here: https://apiforums.easylink.com/emapidocs/25/index.html

dentalplans

I'm copying the authentication code from the 2.5 sample. If you right click the web reference in the sample project and click "Update", even your sample removes the XOA class and it's no longer present. I've looked at the documentation, and I'm not seeing the XOA class.

If someone can just tell me which WSDL to use or a namespace or something, I can at least get past the first part. I've been looking at this all day, so I've read the posts, the manuals and all the other online docs and all of them have the class present, and I've used the URLs given on the forums and in the document sent to me by the sales rep.

skamens

Links to all of the WSDLs are on the namespaces page I referenced earlier: https://apiforums.easylink.com/emapidocs/25/Introduction/Namespaces.html .

For Authenticate, the link to the WSDL can be found here: http://ws.easylink.com/Authenticate/2011/01?WSDL

dentalplans

For anyone else having the problem, I had to add a reference to system.web.services in my project.