.net - Assembly creation guidelines -
Is there a rule of thumb that you can get as a number of static functions in an assembly?
How can you identify that the function requires a static V / S function, which is not required to be stable?
OK, there is no rule of thumb - which comes under the design logic. If you wanted to listen to FxCPOP, then a method is static, if it does not work on class members ...
I like the old definition of age, the method should be stable But may not be specific for an example of type.
This link contains "when to use" section:
Comments
Post a Comment