You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.
On page 103, Listing 4-3 is titled "Adding All Tag Helpers in the Microsoft.AspNet.Mvc.TagHelpers Namespace"
The fact it's a Namespace is not why that works... it's because it's an Assembly. Please refer to the "Managing Tag Helper scope" on the TagHelpers Overview page for the two ways (Assembly wildcard and FQN) you can make Tag Helpers available to the view.
It would be much less misleading if 'Namespace' were changed to 'Assembly' and it would then also align with the official Microsoft documentation.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On page 103, Listing 4-3 is titled "Adding All Tag Helpers in the Microsoft.AspNet.Mvc.TagHelpers Namespace"
The fact it's a Namespace is not why that works... it's because it's an Assembly. Please refer to the "Managing Tag Helper scope" on the TagHelpers Overview page for the two ways (Assembly wildcard and FQN) you can make Tag Helpers available to the view.
It would be much less misleading if 'Namespace' were changed to 'Assembly' and it would then also align with the official Microsoft documentation.
The text was updated successfully, but these errors were encountered: