search

dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
https://asp.net
MIT License
35.39k stars 10k forks source link

Tag Helper is generating the empty link #33075

Open Sourabh721992 opened 3 years ago

Sourabh721992 commented 3 years ago

I am trying creating link using tag helper but that is creating the empty link. I have included Tag helper reference as well. PFA the code file: TagHelper.txt

ManickaP commented 3 years ago

Hi @Sourabh721992 could you please specify in more detail what you're doing and what you're trying to achieve? Could you share a minimal reproduction (source code) of the problem so we can help.

Sourabh721992 commented 3 years ago

Hi,

I am using a tag anchor link to go from view, Index.cshtml to view, Details.cshtml. Both views are linked to HomeController in the solution. But what is happening is tag helper is creating empty link for me. I am attaching all the files.

Index.txt Details.txt _ViewImports.txt HomeController.txt

ManickaP commented 3 years ago

Are you following any example or documentation? https://docs.microsoft.com/en-us/aspnet/core/mvc/views/tag-helpers/intro?view=aspnetcore-5.0 might help you, there are also some samples here: https://github.com/dpaquette/TagHelperSamples

Unfortunately, this is beyond my knowledge. @Pilchie is this something you can help with?

Sourabh721992 commented 3 years ago

Yes I have followed the documentation but I am not sure why the link is href is not getting generated.

Pilchie commented 3 years ago

Transferred to dotnet/aspnetcore. @pranavkm or @javiercn - any ideas on this one?

ghost commented 3 years ago

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

ghost commented 3 years ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.