-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnet-lambda-test tool 6.0 doesn't support aws toolkit with Amazon Q #1935
Comments
@wabwin Good afternoon. Unfortunately, I'm unable to reproduce the issue.
Below is the
Below are the logs emitted in Output window:
Please try re-installing Amazon Lambda Test tool and see if error goes away. (related issue for reference: #1080) Also, on a side note, do you have default browser installed on your system (you may check this in you Windows System Settings), since Amazon Lambda test tool would attempt to launch default we browser? Thanks, |
Describe the bug
When I installed aws toolkit with Amazon Q in my visual studio 2022, and tried to create an aws lambda project and after I debug this function and click "Mock lambda test tool" , the pop up window will open and suddenly debug model will terminate. The breakpoint can not be hit.
Please check if this is an issue for dotnet-lambda-test tool 6.0 with that aws toolkit version. Because now in visual studio 2022, now there is only this version "aws toolkit with Amazon Q" can be installed in "Extension manager".
Regression Issue
Expected Behavior
It would be helpful if you can check this point and resolve it.
Current Behavior
When use dotnet lambda test tool 6.0 and press F5 to debug, it throws output below
'dotnet-lambda-test-tool-6.0.exe' (CoreCLR: DefaultDomain): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.36\System.Private.CoreLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'dotnet-lambda-test-tool-6.0.exe' (CoreCLR: clrhost): Loaded 'C:\Users*.dotnet\tools.store\amazon.lambda.testtool-6.0\0.16.0\amazon.lambda.testtool-6.0\0.16.0\tools\net6.0\any\Amazon.Lambda.TestTool.BlazorTester.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'dotnet-lambda-test-tool-6.0.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.36\System.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'dotnet-lambda-test-tool-6.0.exe' (CoreCLR: clrhost): Loaded 'C:\Users*.dotnet\tools.store\amazon.lambda.testtool-6.0\0.16.0\amazon.lambda.testtool-6.0\0.16.0\tools\net6.0\any\Amazon.Lambda.TestTool.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'dotnet-lambda-test-tool-6.0.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.36\System.Console.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The program '[69912] dotnet-lambda-test-tool-6.0.exe' has exited with code 3221226505 (0xc0000409).
Reproduction Steps
If you have any other concerns, please let me know about it.
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
No other additional sdks
Targeted .NET Platform
.NET 6
Operating System and version
Windows 11
The text was updated successfully, but these errors were encountered: