Home/ Questions/Q 7085309
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T07:24:32+00:00

In .NET, Microsoft has guidelines for naming classes, members, etc. when developing class libraries.

  • 0

In .NET, Microsoft has guidelines for naming classes, members, etc. when developing class libraries. Other languages may also have best practices how to name classes, how/if to use some notations.

Now SOAP is a protocol that can be used to possibly communicate across language boundaries. Are there best practices how to name functions, variable names, etc.? Or should I use whatever my language (if at all) uses? Or when I’m generating a SOAP interface via tools (e.g. WCF service contracts), should I use whatever the tool produces?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There seems to be no official W3C naming convention for service method names.

    Some commonly used guidelines:

    • Method names should clearly indicate what they do from the client’s point of view

    • Use different method names instead of overloading

    • In general, PascalCasing seems to be favored (no underscores). For .Net, follow the .Net naming conventions for normal methods.

    You may also find this blog post from Oracle useful.

    • 0