Home/ Questions/Q 444539
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T21:16:51+00:00

I am increasingly finding situations where my ASP.NET MVC view requires some logic to

  • 0

I am increasingly finding situations where my ASP.NET MVC view requires some logic to perform layout. These routines have no place being in either my model or my controller. I have 3 options:

  1. Write lots of <% %> inline in the view.
  2. Write less <% %> in a number of partial views.
  3. Write an HtmlHelper Extension method.

It is the last option that confuses me. Is it OK to do this if the logic is specific to only that one view? The extension would be ‘visible’ to the Html object of every other view, and it will never be needed.

Any suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I personally prefer option 3 (“Write an HtmlHelper Extension method”) because those bodies of code lend themselves to be easily unit testable.

    I really do wish extension methods could be placed on internal or nested classes because you are right, you will begin to pollute your namespaces with tons of extension methods which are only used in one View.

    I’d recommend sequestering these HtmlHelper extension methods in static classes in a custom namespace per View that you manually reference in the View so as to limit the number of extension methods available throughout your project.

    • 0