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.
In an ASP.NET MVC application, what do you do when you have unique classes that aren’t controllers, helpers or view-models?
For example, say you have a class of utilities that are useful for processing map/location data.
These utilities may be used by more than one controller.
Would you create a top-level folder/namespace for them and call it ‘Maps’ or something?
Maybe a new top-level folder and namespace called Utilities, and add your utility classes here:
ProjectName.Utilities.MapUtility
If you have a lot of utility type classes, consider moving them into their own separate project.