Where do you put classes that are neither controllers, nor models, nor helpers, nor ViewModels?

In an ASP.NET MVC application, what do you do when you have unique classes that are not controllers, helpers, or views?

For example, let's say you have a class of utilities that are useful for processing map / location data.

These utilities can be used by more than one controller.

Would you create a top-level folder / namespace for them and name it "Maps" or something else?

+5
source share
2 answers

, , Utilities, : ProjectName.Utilities.MapUtility

, , .

+4

, util.

project.name.space.util project.name.space.domain.util

.

, apache , java .net.

+2

All Articles