Hi Rory,
I think Bruce's explanation is reasonable. However, for ASP.NET webservice,
webmethod does should be defined as instance method rather than static. I
think the Coderush might just treat webservice class as as a normal
class(doesn't have sense of webservice). Anyway, I think you you can
report this behavior since in webservice context, that message does be a
bit misleading.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Date: Thu, 12 Jun 2008 13:59:30 +0000 (UTC)
>Message-ID: < >
>From: Rory Becker <>
>Subject: Static/Shared Webmethod
>
>I have been testing a beta feature in Coderush (CodeIssues) which has
prompted
>me with the suggestion that one of my WebMethods in a Webservice, could be
>Shared/Static and is not.
>
>I have never though about this before but I guess I had assumed that there
>is very little point in declaring such a method static or not as the web
>is stateless ( isn't it?)
>
>Is Coderush correct to suggest this or should I be filing a bug?
>
>--
>Rory
>
>