-
Notifications
You must be signed in to change notification settings - Fork 489
Amazon.Lambda.TestTool for Custom .NET Core Runtimes #427
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
Comments
I would like to, it's just a matter of finding time and demand for it. So if this is a feature people want I encourage people to +1 the issue. |
I'll spread the word! I can also help with the effort if we discuss the strategy for how this could be implemented. |
Any update on this? Would really appreciate a version upgrade!! |
yeah, it would be great if this can work in 2.2 as it's not allowing me to use some libraries I have that are 2.2 only. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
We are working on a new version of the test tool that does support this scenario. We just released the first early preview and admittedly our documentation is light and focused on Aspire integration. In that case the test tool runs out of process and Visual Studio is debugging your Lambda project. In this case the test tool is agnostic to what version of .NET you are using which should cover this use case. Closing this as it will be handled with the new tooling. Checkout this tracker for the progress of the new tooling. aws/integrations-on-dotnet-aspire-for-aws#17 |
Comments on closed issues are hard for our team to see. |
Are there plans for a version of the Amazon.Lambda.TestTool that will be compatible with a custom runtime for versions of .NET Core (2.2, etc)?
The text was updated successfully, but these errors were encountered: