ansaurus

Question

asp.net mvc 2 view extensions, new project

Answer 1

A:

If you want to use helper methods and avoid importing the namespace of your helper extension class in each of your views, you can register the namespace in your web.config and it will be accessible to all views.

Like this:

<add namespace="MyMvcNamespace.SomeLibrary"/>

Then you might want to put your HTML Helper extensions in a class library (called "SomeLibrary" in the "MyMvcNamespace" namespace), and add a reference to that in each MVC web application you want to utilize it in.

RPM1984 2010-06-05 04:26:58

That part of it I was able to figure out. The problem is my SomeLibrary project compiles, but when I try to call that extension method the parameter identified as "this HtmlHelper htmlHelper" is causing throwing an error because it is never set. I suspect I'm probably missing a reference or a using statement somewhere, I just don't know where.

bteller 2010-06-08 19:14:37

Have a look at this page: http://www.asp.net/mvc/tutorials/creating-custom-html-helpers-csThere are 2 known methods of creating custom html helpers - using extension method or regular static methods.Maybe the extension method needs to be in the same root namespace of the MVC web application (i know it shouldnt have to be though). Try putting the extension method in a standalone class in the same project as your web application. If that still doesnt work, try changing them from extension methods to regular static methods.As you say though, its probably something obvious (import, etc).

RPM1984 2010-06-09 00:20:32

Answer 2

A:

Okay, I'm feeling kinda silly about this, but it was something painfully obvious.

I had added references to System.Web.Extensions and System.Web.MVC. Apparently though it is really important to remember to add a reference for System.Web. Once I did that, good to go.

So, there you have it!

bteller 2010-06-19 00:43:49

ansaurus

tags:

views:

answers:

asp.net mvc 2 view extensions, new project

related questions