handling class declarations generated by proxy

[TS]

Hi, i have some common classes that i pass from my client app through the
web services to my server side app. I have their assembly referenced in both
places. The proxy automatically creates its own class definitions for all
objects used as params to the web service. A MS professional helped set up
the project and what he said to do was to comment out these proxy created
classes becuase otherwise you get a conflict of duplicating names. So what i
have to do is every time i update my web reference, i have to go in to the
reference.cs class and comment them out.

What is the industry standard way of doing this because this doesn't seem
very good?

thank you

 

[Tom Porterfield]

Hi, i have some common classes that i pass from my client app through the
web services to my server side app. I have their assembly referenced in both
places. The proxy automatically creates its own class definitions for all
objects used as params to the web service. A MS professional helped set up
the project and what he said to do was to comment out these proxy created
classes becuase otherwise you get a conflict of duplicating names. So what i
have to do is every time i update my web reference, i have to go in to the
reference.cs class and comment them out.

What is the industry standard way of doing this because this doesn't seem
very good?

thank you

Instead of using a webreference in your project, use the command line tool
wsdl.exe to generate your proxy. Any time you need to update, run wsdl.exe
to generate the proxy in a temp directory. Copy and paste the updated
methods, making sure to exclude copying the class declarations, into a copy
of the proxy that you keep in your project.