Dot Net Core 3.1 Link Tag Helpers not Clickable

Q: Dot Net Core 3.1 Link Tag Helpers not Clickable

Problem: When developing in Asp.Net Core 3.1 and the links (Asp.Net Core Tag Helpers not working) stop working for example: Link Anchor Tag declared with asp-controller="ControllerName" asp-action="ActionName" stops working see solution below: Solution: (Step 1) Open the Dev Tools, navigate to the "Elements" Tab and find a section where the unclickable link is located in the Dom. (Step 2) When you find the link that can't be clicked, double click on it, while in the Dev Tools [Note] Clicking on a link from the Dev Tools might not work using other Web Browser, this was tested using Chrome Web Browser Version 80.0.3987.132 (Official Build) (64-bit), make sure you are using Chrome the latest version. (Step 3) The navigation happens and the error is thrown, for example, if there are any migrations pending to take place before the Action/Function is navigatable (if this is even a word).

Question

Accepted Answer

Problem: When developing in Asp.Net Core 3.1 and the links (Asp.Net Core Tag Helpers not working) stop working for example:

Link Anchor Tag declared with asp-controller="ControllerName" asp-action="ActionName" stops working see solution below:

Solution:

(Step 1) Open the Dev Tools, navigate to the "Elements" Tab and find a section where the unclickable link is located in the Dom.
(Step 2) When you find the link that can't be clicked, double click on it, while in the Dev Tools

[Note] Clicking on a link from the Dev Tools might not work using other Web Browser, this was tested using Chrome Web Browser Version 80.0.3987.132 (Official Build) (64-bit), make sure you are using Chrome the latest version.

(Step 3) The navigation happens and the error is thrown, for example, if there are any migrations pending to take place before the Action/Function is navigatable (if this is even a word).

Dot Net Core 3.1 Link Tag Helpers not Clickable

702 said:

How to get a path to a file in an ASP Dot Net (ASP

How to get a path to a file in an ASP Dot Net (ASP.Net Core 2.2 ) Core 2.2 Application

MailKit not Sending Emails in Production Enviromen

MailKit not Sending Emails in Production Enviroment with Dot Net Core 2.2

ASP.Net Core 2.2 Razor View Routing for Partial Vi

ASP.Net Core 2.2 Razor View Routing for Partial View not working

Asp.Net Core 3.1 MVC 5 Error ViewBag does not Exis

Asp.Net Core 3.1 MVC 5 Error ViewBag does not Exist in the Current Context

Solved: Error] System.ArgumentException: Illegal c

Solved: Error] System.ArgumentException: Illegal characters in path MS Test when testing with Dot Net Core 2.2

Upgrading to .Net Core 3.1 Error Visual Studio 201

Upgrading to .Net Core 3.1 Error Visual Studio 2019: dotnet core 3.1 rzc generate exited with code 2147450730

Asp.Net MVC Development Notes

Asp.Net MVC Development Notes

Docker on Raspberry Pi Error .Net Core 3.1 Error:

Docker on Raspberry Pi Error .Net Core 3.1 Error: standard_init_linux.go:211: exec user process caused "exec format error"

The framework 'Microsoft.AspNetCore.App' version'3

The framework 'Microsoft.AspNetCore.App' version'3.1.0' was not found

SignalR Error in Dot Net Core 3.1 (.Net Core 3.1)

SignalR Error in Dot Net Core 3.1 (.Net Core 3.1) : "Failed to invoke 'SendMessage' due to an error on the server".

Solved!! Dot Net Core 3.1 Error: Inspecting the st

Solved!! Dot Net Core 3.1 Error: Inspecting the state of an object in the debuggee of type System.Reflection.MethodBase is not supported in this context

[Resolved] Dot Net Core Error "Project file is inc

[Resolved] Dot Net Core Error "Project file is incomplete. Expected imports are missing"

HTTP Dot Net Core 2.2 Error 500.30 - ANCM In-Proce

HTTP Dot Net Core 2.2 Error 500.30 - ANCM In-Process Start Failure

We're unable to complete your request invalid_requ

We're unable to complete your request invalid_request: The provided value for the input parameter 'redirect_uri' is not valid. The expected value is a URI which matches a redirect URI registered for this client application.