Url.Action does not build expected link using Route Attribute in 2.2

[WouterHD]

Describe the bug

After updating to Microsoft.AspNetCore.(Mvc) packages from version 2.1.2 to 2.2.0 some of the urls produced with HtmlHelper ActionLink no longer build the correct link using Route attribute

To Reproduce

Steps to reproduce the behavior:

1. Create an AspNetCore.Mvc project with the following code

Controller

public IActionResult Index()
{
    return View();
}

[Route("{firstInt:int}/{secondInt:int?}")]
public IActionResult Test(int firstInteger, int? secondInteger)
{
    return View("Index");
}

View

@Html.ActionLink("CorrectLink", "Test", "Home", new { firstInt = 1, secondInt = 2, boolean = true })

@Html.ActionLink("WrongLink", "Test", "Home", new { firstInt = 1, secondInt = (int?)null, boolean = true })

Package versions with the expected behaviour

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="2.1.2" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="2.1.2" />
  </ItemGroup>

Package versions with the incorrect behaviour

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="2.2.0" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="2.2.0" />
  </ItemGroup>

Expected behavior

A clear and concise description of what you expected to happen.

Links should go to [host]/1/2?boolean=True and [host]/1?boolean=True respectively, but instead go to [host]/1/2?boolean=True and [host]/Home/Test?firstInt=1&boolean=True

[mkArtakMSFT]

Thanks for contacting us, @WouterHD.
@JamesNK can you please confirm this is the expected outcome? Thanks!

[JamesNK]

@Html.ActionLink("WrongLink", "Test", "Home", new { firstInt = 1, secondInt = (int?)null, boolean = true })

[Route("{firstInt:int}/{secondInt:int?}")]
public IActionResult Test(int firstInteger, int? secondInteger)
{
    return View("Index");
}

I've done some testing. Results:

2.1: /1?boolean=True
2.2 (no EP routing): /Home/Test?firstInt=1&boolean=True
2.2 (EP routing): <blank>
3.0: /Home/Test?firstInt=1&boolean=True

@rynowak Results are odd in that there is a break in behavior between traditional routing in 2.1 and 2.2. Do you know why this traditional routing behavior it changed?

Thank you for contacting us. Due to no activity on this issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.