Why don't you just remove the <Webmethod()> attribute from the the
functions/subs that you don't want to be seen yet?
as soon as they are implemented you can just put the method-attribute back
in place.
HTH
Friso Wiskerke
>I have a webservice with several stubbed out methods and severl
> implemented methods. We are releasing to prod with a beta version
[quoted text clipped - 12 lines]
>
> Thank you
Dustyg - 24 Jan 2006 18:47 GMT
As I stated, we don't want to remove the [WebMethod] attribute because
we don't want to have to push the code every time we release a new
method. Changing a value in a config file would better suite our
needs.
Thank you
- Dustin
Friso Wiskerke - 25 Jan 2006 08:51 GMT
Maybe the [Conditional] attribute can help you out?
> As I stated, we don't want to remove the [WebMethod] attribute because
> we don't want to have to push the code every time we release a new
[quoted text clipped - 4 lines]
>
> - Dustin
Dustyg - 25 Jan 2006 14:35 GMT
The [Conditional] attribute relies on the definition of a compilation
symbol, meaning the defined symbol is compiled and cannot be changed
without re-compiling. It also only ignores calls to the method rather
than removing them from compilation like a directive in C++ would so it
would still show up in the wsdl.