ASP.NET MVC Conventions

Question

ASP.NET MVC is heavily based on conventions, a “configuration convention,” as they say. Thus, this means that what is given is the name and where they are created in the project structure.

As a newbie to ASP.NET MVC, I appreciate the strength and simplicity of this approach, but it seems to me a little confusing to keep track of which conventions are in the game. For example, when using the controller method UpdateModel, which uses HTML form fields that have the same names as the model class properties. This is an obvious thing, and most of the time this is probably what most people will do instinctively, but I see that it will be very confusing if someone renames something in one place and forgot to rename it to another. The connection is somewhat fragile.

So, I thought it would be useful to have a list of all ASP.NET MVC conventions here in one place, as brief statements on best practice. such things as:

"HTML form fields must have the same name as" Model Properties. "

Does anyone have anything like this? Will you help me create a list here?

Answer 1

Use the virtual path from the deployment server and enter it into the project configuration in Visual Studio. Thus, the visual studio development server will use the same path structure as the deployment server. This will save you countless hours of deployment work.

Answer 2

Controllers should always end with a controller .

Answer 3

, , , ( "-" ). , [ControllerName] [ActionName].

Answer 4

Note that a configuration agreement is not required, but how everything works out of the box. If you find that the agreement is confusing or does not help, you can change it (for example, how the controllers are selected, how the views are visible, etc.) or configure.