Debugging through lambda test tool works in Rider 2021, but not in 2022

[pmihalcin]

Describe the bug

I use following launch settings profile for debugging lambda handlers using lambda test tool:

"Rider Debug mock lambda test tool": {
  "commandName": "Executable",
  "commandLineArgs": "--port 5050",
  "workingDirectory": ".",
  "executablePath": "%USERPROFILE%\\.dotnet\\tools\\.store\\amazon.lambda.testtool-3.1\\0.11.3\\amazon.lambda.testtool-3.1\\0.11.3\\tools\\netcoreapp3.1\\any\\Amazon.Lambda.TestTool.BlazorTester.dll",
  "environmentVariables": {
  }
}

Expected Behavior

Debugging session started as expected

Current Behavior

Fails to start debugging session

Reproduction Steps

When I execute this profile in Rider 2021.3.4, it works as expected.
When I execute the same in Rider 2022.1.1, it fails on:

C:/Users/Lenovo/.dotnet/tools/.store/amazon.lambda.testtool-3.1/0.11.3/amazon.lambda.testtool-3.1/0.11.3/tools/netcoreapp3.1/any/Amazon.Lambda.TestTool.BlazorTester.dll --port 5050
Unhandled Exception: System.IO.FileNotFoundException: 
Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
One or more errors occurred.

It seems something changed between Rider major versions.

Can you troubleshoot this problem please?

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

SDK version is 3.1.401

Lambda Test Tool 0.11.3

Targeted .NET Platform

.NET Core 3.1

Operating System and version

Windows 10

[ashishdhingra]

@pmihalcin Unfortunately I'm unable to reproduce the issue using JetBrains Rider version 2022.1.1 and Lambda Test Tool version 0.12.2. My Exe path in Rider run configuration is set to <<user-profile-directory>>/.dotnet/tools/.store/amazon.lambda.testtool-3.1/0.12.2/amazon.lambda.testtool-3.1/0.12.2/tools/netcoreapp3.1/any/Amazon.Lambda.TestTool.BlazorTester.dll and working directory as root of Lambda project (as per instructions at https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool#configure-for-jetbrains-rider). Please try upgrading to latest version of test tool.

[fga150]

I've had the same issue as well. The Lambda Test Tool worked well with Rider 2022.1.1 until I installed the .net6 SDK (dotnet-sdk-6.0.300-win-x64). After that, running the Lambda Test Tool from Rider started to give me this error.

With Rider 2022.1.1 (tested as well with Rider 2022.1 and same error) and Lambda Test Tool 3.1 version 0.11.3 I was getting the "Could not load file or assembly 'System.Runtime, Version=4.2.2.0..." error.
With Rider 2022.1.1 (tested as well with Rider 2022.1 and same error), .net 6 and Lambda Test Tool 6.0 version 0.12.2 I was getting "Could not load file or assembly 'System.Runtime, Version=6.0.0.0' error. This is what I have in the executablePath: "%USERPROFILE%/.dotnet/tools/.store/amazon.lambda.testtool-6.0/0.12.2/amazon.lambda.testtool-6.0/0.12.2/tools/net6.0/any/Amazon.Lambda.TestTool.BlazorTester.dll"

If I ran the Lambda Test tool with the exe from Powershell, it worked, but that would not allow debugging from Rider, since it was launching it from Powershell.

Going back to Rider 2021.3.4 fixed it for me, which is admittedly not a great solution.

[oleksii-yurchenko-easypark]

The issue is actual for tool version 0.12.7 and RIder 2022.1.2 as well

[oleksii-yurchenko-easypark]

I've managed to fix the issue. In my case the problem was because I was using unproper launch config type. It must be .NET Executable in Rider

[fga150]

Could you please share your launch config?
This is what I have in launchSettings.json:

{
  "profiles": {
    "Mock Lambda Test Tool Rider": {
      "commandName": "Executable",
      "commandLineArgs": "--port 5050",
      "workingDirectory": ".",
      "executablePath": "%USERPROFILE%/.dotnet/tools/.store/amazon.lambda.testtool-6.0/0.12.2/amazon.lambda.testtool-6.0/0.12.2/tools/net6.0/any/Amazon.Lambda.TestTool.BlazorTester.dll"
    }
  }
}

And it's still not working for me :/

[oleksii-yurchenko-easypark]

{
"profiles": {
"Mock Lambda Test Tool": {
"commandName": "Executable",
"commandLineArgs": "--port 5050",
"executablePath": "%USERPROFILE%\.dotnet\tools\.store\amazon.lambda.testtool-3.1\0.12.7\amazon.lambda.testtool-3.1\0.12.7\tools\netcoreapp3.1\any\Amazon.Lambda.TestTool.BlazorTester.dll",
"workingDirectory": "C:\RiderProjects\lambda" -- it must be a folder where your lambda & configs are located
}
}
}
}
Make sure to use this profile type

[fga150]

That works now, thanks!!
I was using:

instead of:

Changing that fixed it :)

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.