Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When I add a service reference to my Visual Studio 2010 C# project, a new class for one of the types defined in the WSDL will be generated. A de-facto equivalent definition of that type already exists in our solution in a different assembly.
When adding the SoapTypeAttribute to the existing class and replacing the references to the generated class in the generated code, everything runs perfectly and as expected.
How would I tell Visual Studio to use the existing class in the generated code?
This is not possible… you have to use the Classdefinition of the webservice.
You could try to define an Interface from your Webservice and derive your Class from that interface as a workaround.