Lambda Test Tool v2 add .NET 10 build target #2279
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull request overview
Adds a .NET 10 target to Lambda Test Tool v2 (and its associated test projects) to improve the local Lambda debugging/test experience in VS Code/Aspire scenarios, alongside updating several AWS Lambda/AWSSDK package dependencies.
Changes:
- Multi-target Lambda Test Tool v2 and its tests for
net8.0;net10.0. - Update AWS Lambda and AWSSDK package references to newer versions.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| Tools/LambdaTestTool-v2/src/Amazon.Lambda.TestTool/Amazon.Lambda.TestTool.csproj | Multi-target tool for net8/net10 and update AWS/AWSSDK dependencies. |
| Tools/LambdaTestTool-v2/tests/Amazon.Lambda.TestTool.UnitTests/Amazon.Lambda.TestTool.UnitTests.csproj | Multi-target unit tests for net8/net10 and bump AWS-related package versions. |
| Tools/LambdaTestTool-v2/tests/Amazon.Lambda.TestTool.IntegrationTests/Amazon.Lambda.TestTool.IntegrationTests.csproj | Multi-target integration tests for net8/net10 and bump AWS-related package versions. |
| Tools/LambdaTestTool-v2/tests/Amazon.Lambda.TestTool.Tests.Common/Amazon.Lambda.TestTool.Tests.Common.csproj | Multi-target shared test utilities for net8/net10 and bump APIGatewayEvents package version. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Tools/LambdaTestTool-v2/src/Amazon.Lambda.TestTool/Amazon.Lambda.TestTool.csproj
Show resolved
Hide resolved
normj
force-pushed
the
normj/testtool-v2-10
branch
from
91af692 to
78466e5
Compare
normj
force-pushed
the
normj/testtool-v2-10
branch
from
78466e5 to
a0812f4
Compare
GarrettBeatty
approved these changes
Feb 9, 2026
muhammad-othman
approved these changes
Feb 10, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
Tracking down issues with getting the Lambda experience working better in VS Code. I'm getting some issues with the test tool not finding the
blazor.web.jsfile when run through Aspire + VS Code but the issues go away when I build the test tool for .NET 10.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.