Prove me wrong: VB.NET HtmlHelper Extension Method NOT Working in MVC 4 with VS 2012 - vb.net

Question

No matter how many times I try, I cannot get my HTML Helper extension method to work. Here's the test steps I've created, if someone wants to try it out themselves:
Using Visual Studio 2012, I create a new "Visual Basic ASP.NET MVC 4 Internet Web Application" using the "Internet Application" project template.
I create a folder "~/Views/Helpers"
I create a file "DisplayForPropertyHelper.vb" and add the following code:
Namespace TestProject.Extensions
Public Module HtmlHelperExtensions
<Extension()>
Public Function DisplayForProperty(helper As HtmlHelper) As MvcHtmlString
Return MvcHtmlString.Create("TEST")
End Function
End Module
End Namespace
I open up "~/Views/Web.config" and change the following (I add the extensions namespace):
<system.web.webPages.razor>
<host factoryType="System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
<pages pageBaseType="System.Web.Mvc.WebViewPage">
<namespaces>
<add namespace="System.Web.Mvc" />
<add namespace="System.Web.Mvc.Ajax" />
<add namespace="System.Web.Mvc.Html" />
<add namespace="System.Web.Optimization"/>
<add namespace="System.Web.Routing" />
<add namespace="TestProject.Extensions"/>
</namespaces>
</pages>
</system.web.webPages.razor>
Compile the project
Choose ANY razor view file, and type #Html.Display-and you will see that the extension method does not show up.
Add to the razor view file #Imports TestProject.Extensions then save and close the file.
Reopen file, and type #Html.Display-and you will see that the extension method does not show up.
You can even try closing VS2012 and reopening the project. Won't make a difference.
I have been battling with this for weeks now. All answers I've found on here and elsewhere are NO help. Someone must have an answer.

Answer 1

Make sure that you prefixed your namespace with your application name. So for example if the application you created was called MvcApplication1 in your ~/Views/web.config you should put:
<add namespace="MvcApplication1.TestProject.Extensions"/>
and not just:
<add namespace="TestProject.Extensions"/>
Yeah, I guess, it's one of those VB.NET thingies :-) Oh and don't forget to close and open the Razor view after making changes to the ~/Views/web.config file, otherwise your changes won't be taken into account immediately (if you run the application it will work of course).

Answer 2

This is not really an answer, but I write it here in hopes to only add (a little) the overall picture.
For me, I discovered that my 'Module' class was not explicitly being modified as 'Public' (the default is Friend when you don't specify a modifier, and that was what was killing mine)
Yes, I realize the O.P.'s example Module is already declared Public already.. but, I just didn't catch it in my own code stack and figured I'd highlight that requirement. As a native C-sharper having to play VB.Netter for the past five years, I get tired of translating C# snippets manually.. and tend to rely on code converters. So, the nifty HtmlHelper I found and converted didn't quite come out right and I neglected to look for this issue in the code snippet that had been generated for me.
As noted in the prior comments, I'd also like to join the chorus and state the following:
I was doing all of the above (so I thought, as I checked the O.P.'s checklist over and over)
I also find writing HtmlHelpers nearly impossible for VB.NET MVC 4 (until today) - the requirements seem to be supported in such a fragile manner
I also despise having to use VB.NET for developing MVC sites (but, I must live with it.. it's part of the legacy code I inherited coming on board my company)
As much as I despise it (for reasons like this one) I will say everything does seem to be supported if you are determined enough to figure it out. (thanks StackOverflow!)
Prior to this discovery, I thought maybe it wasn't working because my application name had dots in it (MyCorp.Web.WorkOrders) vs. (MvcApplication1).. but, my tests conclude that the application name was not the issue. Either way you name it, it will work.
Again, as #Darin already pointed out.. you certainly must include the solution name(space) as part of the 'add namespace' declaration in views/web.config