Url.Action doesn't include action name when there are more parameters

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

Hi, this is simple one.
I have default route defined like this:

app. UseEndpoints(endpoints =>
{
	endpoints. MapDefaultControllerRoute();
	endpoints. MapControllers();
});

Now, I call:
Url.Action("GroupCategoryView", new { id = "(sheetGroupId)", categoryId = "(categoryId)"})

I was expecting address like:
/Document/GroupCategoryView/(sheetGroupId)?categoryId=(categoryId)
(Document is my controller name), but instead it gives:

/(sheetGroupId)?categoryId=(categoryId)

---

Original Comments

Feedback Bot on 7/23/2020, 03:23 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Feedback Bot on 7/23/2020, 10:58 PM:

Thank you for sharing your feedback! Our teams prioritize action on product issues with broad customer impact. See details at: https://docs.microsoft.com/en-us/visualstudio/ide/report-a-problem?view=vs-2019#faq. In case you need answers to common questions or need assisted support, be sure to use https://visualstudio.microsoft.com/vs/support/. We’ll keep you posted on any updates to this feedback.

ajachocki on 7/24/2020, 01:55 AM:

After I removed HttpGet attribute from controller method it started working. So maybe this was my mistake. And one should not use those attributes on not api controllers.

---

Original Solutions

(no solutions)

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. 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]

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.

[ghost]

Thanks for contacting us.
We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. 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.

[MackinnonBuck]

After I removed HttpGet attribute from controller method it started working. So maybe this was my mistake. And one should not use those attributes on not api controllers.

It sounds like there's more going on here than what's provided in the original comment. We would probably need a repro project to continue investigating this further.

[ghost]

Hi @vsfeedback. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.