Skip to content

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

Closed

Description

@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

Activity

  1. added
    bugThis issue is a bug.
    needs-triageThis issue or PR still needs to be triaged.
    on May 17, 2022
  2. changed the title [-](short issue description)[/-] [+]Debugging through lambda test tool works in Rider 2021, but not in 2022[/+] on May 17, 2022
  3. ashishdhingra commented on May 17, 2022

    @ashishdhingra
    Contributor

    @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.

  4. locked and limited conversation to collaborators on May 17, 2022
  5. converted this issue into a discussion #1180 on May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions