The class name should usually point to a class function. "Common" is usually better as part of the name of the library (for example, "Common.Logging" or "Ninject.Web.Common") to indicate that the files in this library are shared for a specific purpose and are likely to be used by a number of other libraries .
You will need to provide additional information about the purpose of the class you are creating, if you need better ideas for calling the class. But overall it's good to think about the "consumer" experience. For example, what makes sense?
var common = new Common(); common.LogInfo("something happened");
... or:
var log = new LogService(); log.LogInfo("something happened");
source share