Best pratices ... advice -- client proxy from wsdl

[Trebek]

Hello group:

I am seeking advice regarding the modification of the client proxy generated
by wsdl from a .NET webservice. I have several production services with
many different types of clients referencing them that have been working well
for the last two years. Whenever we release a feature update on one of the
services that would alter the client proxy, we re-reference the changed
service to rebuild the proxies and re-deploy. This is fine for our purposes
since it is scheduled downtime (usually at night -- off hours). The problem
comes in when we change a service using WSE. This requires that we change
the client proxy to be derived from Microsoft.Web.Services....etc. Is there
any way to specify this by *default*? It's not a big deal, but since
several people are working on these releases, ocassionally someone will push
a version live when they forgot to change this. Testing picks it up
immediately, but I'd like to eliminate the problem before this occurs. In
other cases, I could simply create a class derived from the wsdl-generated
proxy, change/override what I need in the sub class and use that in the
client, but since multiple inheritance is not supported in C#, how can I
handle this situation?

Any advice?

Thanks all,

Alex

 

[Dino Chiesa [Microsoft]]

sed ?

 

[Trebek]

Yeah, I did a VS add-in project that does something similiar to SED (uses
Regex to replace class def, add overrides, etc..) but was just hoping there
was some solution I was missing

Alex