Salesforce的.NET API集成 [英] Salesforce .net API integration

查看:233
本文介绍了Salesforce的.NET API集成的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有点困惑。我们从Salesforce下载的WSDL文件,并使用所建议的文件路径创建一个Web引用。它创造了我的理解是代理类,而不是SforceService类。

I'm a little confused. We downloaded the WSDL file from Salesforce and created a web reference to it using a file path as suggested. It created what I understood to be the proxy classes, but not the SforceService class.

别人认为你必须使用WSDL.EXE产生,我做到了类文件,它现在的作品。

Someone else suggested that you have to use the WSDL.exe to generate the class file which I did and it now works.

我不明白的是为什么呢?

What I don't understand is why?

不作为需要创建一个Web引用配置代理服务器的过程?为什么额外的步骤?

Didn't the process of created a web reference configure the proxies as needed? Why the extra step?

有什么建议?

推荐答案

该SforceService类时,才生成,如果你做添加Web引用(从附加服务引用对话框中的高级按钮)如果您添加服务引用,你会得到一个不同集合的对象,以及不同的编程模型。

The SforceService class is only generated if you do add web reference (from the advanced button on add service reference dialog) if you do add service reference, you get a different set of objects, and a different programming model.

在销售人员现场所有的.NET示例使用添加Web引用样式的代理,但如果你宁愿使用WCF(又名服务引用)风格的东西,而不是,那也没关系。

All the .NET samples on the salesforce site use the add web reference style proxies, but if you'd rather use the WCF (aka service reference) style stuff instead, that's fine too.

这篇关于Salesforce的.NET API集成的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆