Okay, I've just deleted my first post since I was having issues with editting a post with codeblocks. Trying once more.
I'm new to WCF and I am trying to write a webservice that must follow a specific XML format. Because of this, I found that I had to drop DataContractSerializer since I must be able to use attributes. I now have the <XMLSerializerFormat>
attribute on my servicecontract for this purpose and I have laid out the schema I need by using a Class with Public Properties and the <Serializable()> attribute where appropriate. I have one service endpoint that has several different schemas
that it may accept. I have a base class with derived classes for this purpose. This also works well from what I can see as the test client and webservice are talking to each other just fine. However, the client that will be using the service
is non-WCF and must have the elements named specifically in order to handle them. The problem arises when the service is serializing the derived classes. The structure of each class works perfectly, however, the name of the element is not the name
of the element I have assigned it. It is most likely because of the way that I pass the information back and forth to the service and the fact that I do not know what the object actually is when it is passed into or out o
View Complete Post