Custom tag helper not working

Question

I followed a few guides on creating a custom tag helper for ASP Core.

This is my helper:

using Microsoft.AspNetCore.Mvc.ViewFeatures;
using Microsoft.Asp         


        

Answer 1

See Managing Tag Helper scope

@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
@addTagHelper *, AuthoringTagHelpers

The code above uses the wildcard syntax ("*") to specify that all Tag Helpers in the specified assembly (Microsoft.AspNetCore.Mvc.TagHelpers) will be available to every view file in the Views directory or sub-directory.

Answer 2

A way you can make the search for your TagHelpers a bit quicker is to provide the namespace that your tag helpers live in instead of the asterisk, which will look everywhere in your assembly.

@addTagHelper com.excellor.TagHelpers.*, excellor

Where excellor is the assemblyname and com.excellor.TagHelpers is the namespace the tag helpers reside in.

Note, the following entry is NOT needed as long as you are namespacing your tag helpers.

@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers

Answer 3

You need to provide only assembly name in the view imports file.

_ViewImports.cshtml:

@addTagHelper *, ToolConstrolSystem

Answer 4

So I wasted a bit of time chasing the problem where a taghelper was not working. After a while I went to bed and today with fresh eyes I gave it another try, was then that I realized that I did not add the @addTagHelper in the Razor Pages folder only in the Views folder.

So if you like I have this /Pages + /Views concepts make sure to go through all those _ViewImports.cshtml. Leaving this note here hopefully will remind someelse's tired brain, and if it helped take a break and go for a walk or a snooze.

Answer 5

And also keep in mind that at the moment (March 2020) .Net Core 3 automatically generates the namespaces with underscores in it. Nevertheless, the assembly name will be exactly the same as the folder name (even if it does contain whitespaces and other uncommon for folder name symbols). It can cause troubles with adding your custom tag helpers.

Let's assume:

1. You have a folder called SUPER-TEST
2. You cd into it and call dotnet new mvc
3. This makes your new project have a namespace "SUPER_TEST".
4. You create a tag helper in this namespace and include the assembly name into the _ViewImports like this:

***
@addTagHelper *, SUPER_TEST
***

It's not gonna work. Because in fact your assembly is now called SUPER-TEST. .Net Core runtime replaces underscores with dashes when creating the new project.

So, you have to import the tag helpers from SUPER-TEST, like this:

***
@addTagHelper *, SUPER-TEST
***

Answer 6

For those who are using the syntax correctly, but have their views and their TagHelpers in separate projects:

• Rebuild the TagHelper project
• Then rebuild the View project

It will work.