I'm writing client and webservice code. The problem is that in the client, i get ambiguous references when i use a common data type.
How do i make computed Permissions one and only, unique across all my webservices
Thanks.
Error 102 'ComputedPermissions' is an ambiguous reference between 'MyCompany.XXX.API.AdminServiceWSE.ComputedPermissions' and 'MyCompany.XXXt.API.SearchServiceWSE.ComputedPermissions' D:\src\MyCompany\XXX\Main\Source\Production\XXXt\API\VaultDocument.cs 47 17 VaultAPI
making a data type unique across web services
Steve Camsell
It sounds like you just need to namespace qualify your types in code:
Replace ComputedPermissions in your code with
MyCompany.XXX.API.AdminServiceWSE.ComputedPermissions or
MyCompany.XXXt.API.SearchServiceWSE.ComputedPermissions as appropriate
Is that the problem you are running into
Daniel Roth
Ralf Hedler
Hi
Here is what i understoodd. this is the problem occurring when u r using Web service in client pplication.
As in ur web service u have 2 different NameSpaces but the class names are same in it.When u r trying to consume it in ur client, then ur getting an ambiguous references like u have system.windows.forms.Timer and system.Threading. Timer.
If ur application is using :
using system. Windows.Forms;
using System.Threading;
now if u will try to create the object of Timer ten u will get ambiguous reference problem.
If i am correct then i m afraid to say that there is nothing u can do abt. it. Only solution is to use a different class name in any of ur package.
aprivate
Daniel,
Issue is not of using fully qualified names in ur client, issues is how can u solve ur component's client 's problem of geting ambiguous reference.
Can u tell me any another way of using it apart from specifying Fully qualified names