Comments on: Web Service Stumper: "Ambiguous Type" http://www.csharp411.com/web-service-ambiguous-type-question/ C# Information, Code, Tips and News Sat, 13 Mar 2010 00:13:45 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Ethan http://www.csharp411.com/web-service-ambiguous-type-question/comment-page-1/#comment-3604 Ethan Mon, 13 Oct 2008 15:30:12 +0000 http://www.mini-tools.com/at2/csharp/wordpress/web-service-ambiguous-type-question/#comment-3604 Exactly what happened on my part. I have resolved mine by serializing changing the parameter of the method in my webservice from object to string and serialize it. it's true it's ambigous coz the service and the UI both use the datamodel entity (on my part). so from: [WebMethod] public string GetContact(ContactList contactList) to: [WebMethod] public string GetContact(string contactList) and from the calling UI, i serialiaze the object to string and inside the webmethods, deserialize it! And you're done! Exactly what happened on my part. I have resolved mine by serializing changing the parameter of the method in my webservice from object to string and serialize it. it's true it's ambigous coz the service and the UI both use the datamodel entity (on my part).

so from:

[WebMethod]
public string GetContact(ContactList contactList)

to:

[WebMethod]
public string GetContact(string contactList)

and from the calling UI, i serialiaze the object to string and inside the webmethods, deserialize it! And you're done!

]]> By: Timm http://www.csharp411.com/web-service-ambiguous-type-question/comment-page-1/#comment-81 Timm Mon, 21 Jan 2008 18:00:40 +0000 http://www.mini-tools.com/at2/csharp/wordpress/web-service-ambiguous-type-question/#comment-81 After conversing with Microsoft tech support and a couple of MVPs, it appears there is currently no way for a C# web servce client to bind to a specific DLL in the web service "bin" folder. Thus, the solution is to re-architect the project. I removed the proxy definition for DataService (that inherits from SoapHttpClientProtocol) from shared.dll, and moved it into a separate client.dll. My application client.exe references client.dll, and since client.dll is not uploaded to the web services "bin" folder, there is no ambiguity. After conversing with Microsoft tech support and a couple of MVPs, it appears there is currently no way for a C# web servce client to bind to a specific DLL in the web service "bin" folder.

Thus, the solution is to re-architect the project. I removed the proxy definition for DataService (that inherits from SoapHttpClientProtocol) from shared.dll, and moved it into a separate client.dll. My application client.exe references client.dll, and since client.dll is not uploaded to the web services "bin" folder, there is no ambiguity.

]]>