ASP.NET Core route multiple optional parameters

Question

In MVC 4 I had this custom route:

url+ "test/{id1}/{id2}/{id3}/{id4}/{id5}/{id6}/{id7}/{id8}/{id9}/{id10}/{id11}/{id12}",
                                                  new
                                                  {
                                                      controller = nameof(Test),
                                                      action = "Index",
                                                      id1 = UrlParameter.Optional,
                                                      id2 = UrlParameter.Optional,
                                                      id3 = UrlParameter.Optional,
                                                      id4 = UrlParameter.Optional,
                                                      id5 = UrlParameter.Optional,
                                                      id6 = UrlParameter.Optional,
                                                      id7 = UrlParameter.Optional,
                                                      id8 = UrlParameter.Optional,
                                                      id9 = UrlParameter.Optional,
                                                      id10 = UrlParameter.Optional,
                                                      id11 = UrlParameter.Optional,
                                                      id12 = UrlParameter.Optional
                                                  }

This was going to a single method in TestController. However, I can't seem to get this working in Core.

If I have

"Test Controller", "/test/{action}/{id1?}/{id2?}/{id3?}/{id4?}/{id5?}/{id6?}/", new { Controller = "Test", Action = "Index" }

In controller:

[HttpGet]    
public IActionResult Index(string id1, string id2, string id3, string id4, string id5, string id6)
    {
        return Ok("hello world");
    }

Then it only works if I specify the ids as query parameters. I need the slashes in the URLs.

Route attributes work, but the URL is dynamic and I don't think that's working well together.

How would I need to build the route here to get this to work?

Serge · Accepted Answer · 2021-08-31 21:13:04Z

1

it is better to use attribute routing

[HttpGet("~/test/index/{id1?}/{id2?}/{id3?}/{id4?}/{id5?}/{id6?}")]
public IActionResult Index(string id1, string id2, string id3, string id4, string id5, string id6)
    {
        return Ok("hello world");
    }

answered Aug 31, 2021 at 21:13

Serge

44.4k4 gold badges26 silver badges53 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

The Cookies Dog Over a year ago

As mentioned, this is no good as as my URL must be dynamically registered.

Serge Over a year ago

@TheCookiesDog I am sorry, but could you please explain what dynamically registered means?

The Cookies Dog Over a year ago

The URL is not fixed. Attribute routing seems to always go fixed to /test/... but I need it based off another passed in URL.

Collectives™ on Stack Overflow

ASP.NET Core route multiple optional parameters

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related