Error loading service

It looks like the DuplicateError started when I added a second operation derived from Update. That meant I had two handlers that could take an Update operation. I am guessing that confused the dsshost. Is this expected?

I tried changing my handler to derive directly from DssOperation, but the constructor I added that takes the Request data was not added to the proxy.

What do I need to do to make a custom operation constructor carry over to the proxy version?

AlanOursland at 2007-10-2 >

I don't think that is what is going on with the DuplicateEntry error. If I look at my service list, I do not see my FuturaSerialPort running. Also, the service that depends on FuturaSerialPort does not start because it cannot find the required FuturaSerialPort partner service.

If I remove the SetEffector operation then the DuplicateEntry error disappears. My theory is that there are two Handler functions that take Update operations and so the DssHost does not know which it should Handler should be called in response to an Update request. The DssHost throws a DuplicateEntry error because there are two Handler entries for Update.

I tried changing SetEffector to derive directly from DssOperation like this:

But the proxy generated for SetEffector does not have the single argument constructor I defined.

I suspect there is an attribute that will tell the proxy generator to include that constructor, but I cannot find any examples to copy.

AlanOursland at 2007-10-2 >

You have two operations, SetEffector, and ReadPort that have the same body type (ReadPortRequest) and *both* derive from Update. That is not allowed. Instead define a new body type, like SetEffectorRequest, that can for example inehrit from some common base type.

thanx

g

GeorgeChrysanthakopoulos at 2007-10-2 >