WCF proxy problems

Hi everybody:

I develop an application that uses .NET Remoting in order to communicate the
client with our server applications.

Now, we are moving to Windows Communication Framework and we have several
problem on our migration.

This is my current data model:

IDataManager:
- Data GetDataByID(int id);
- Data GetDataByParentID(int id);
- string GetDataName();
- MyCustomEnum GetDataInformation();

Data:
- int ID;
- string Name;
- int ParentID;
- MyCustomEnum DataInfo.

I defined my data structure on a DLL called: MyApplication.Common.dll

MyServer and MyClient implement the IDataManager (ServerDataManager and
ClientDataManager respectively). The ServerDataManager implements the server
functionality and the ClientDataManager uses a remote object that access to
the ServerDataManager implementation:

ClientDataManager:

string GetDataName();
{
return remoteObject.GetDataName();
}

I wanted to implement a similar model using Windows Communication Foundation
but I have a lot of problems about it:

1. My data providers will include more and more methods anytime, because my
communication model upgrade will be done module by module, so, generating
the proxies anytime is a very bothering task

2. I have several proxies in order to provide different information, but all
my proxies implement the same enumerations and classes that I already
implement in my Common.dll; so, when I compile my project, a lot of "Already
defined" errors are thrown.

There is a way to remove the need of generating the proxies anytime my
IDataManager interfaces are modified?

There is a way to avoid the need of define my enumerations and classes on
the proxies?

Best regards,



Ernesto

Hi

If you use the Service Model Metadata Utility Tool (Svcutil.exe) , to create
the Proxy, make this adding the {/excludeType:<type list>} option.

In another case, i recommends create a own Proxy to call the service.

Regards,

--
Ronald Ricardo Ramirez Moran
Solutions Architect
DlanorOk Solutions

Blog:
http://blogs.wdevs.com/DlanorOk
http://spaces.msn.com/DlanorOk {spanish}


"Ernesto Bascón Pantoja" wrote:

> Hi everybody:
>
> I develop an application that uses .NET Remoting in order to communicate the
> client with our server applications.
>
> Now, we are moving to Windows Communication Framework and we have several
> problem on our migration.
>
> This is my current data model:
>
> IDataManager:
> - Data GetDataByID(int id);
> - Data GetDataByParentID(int id);
> - string GetDataName();
> - MyCustomEnum GetDataInformation();
>
> Data:
> - int ID;
> - string Name;
> - int ParentID;
> - MyCustomEnum DataInfo.
>
> I defined my data structure on a DLL called: MyApplication.Common.dll
>
> MyServer and MyClient implement the IDataManager (ServerDataManager and
> ClientDataManager respectively). The ServerDataManager implements the server
> functionality and the ClientDataManager uses a remote object that access to
> the ServerDataManager implementation:
>
> ClientDataManager:
>
> string GetDataName();
> {
> return remoteObject.GetDataName();
> }
>
> I wanted to implement a similar model using Windows Communication Foundation
> but I have a lot of problems about it:
>
> 1. My data providers will include more and more methods anytime, because my
> communication model upgrade will be done module by module, so, generating
> the proxies anytime is a very bothering task
>
> 2. I have several proxies in order to provide different information, but all
> my proxies implement the same enumerations and classes that I already
> implement in my Common.dll; so, when I compile my project, a lot of "Already
> defined" errors are thrown.
>
> There is a way to remove the need of generating the proxies anytime my
> IDataManager interfaces are modified?
>
> There is a way to avoid the need of define my enumerations and classes on
> the proxies?
>
> Best regards,
>
>
>
> Ernesto
>
>
>
>