Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How should one structure their frequently used non-important functions (conversions, etc) in C# since everything must be contained in an object? Usually I take all these functions and put them in a static Utility class. Is this a good practice? How do most developers do it?
This tends to be what most developers end up doing, myself included.
The only pitfall is when you start having a massive set utilities that shouldn’t really all belong together (conversion, database access, logging you name it…).
Try to structure these as different assemblies, so projects that do not need a set of utilities will not have to import a large set of extraneous code.