Skip to content

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

Closed
tonysneed opened this issue Mar 26, 2019 · 10 comments
Closed

Amazon.Lambda.TestTool for Custom .NET Core Runtimes #427

tonysneed opened this issue Mar 26, 2019 · 10 comments
Labels
feature-request A feature should be added or improved. l Effort estimation: large module/lambda-test-tool p2 This is a standard priority issue queued

Comments

@tonysneed
Copy link

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)?

@normj normj added the feature-request A feature should be added or improved. label Mar 26, 2019
@normj
Copy link
Member

normj commented Mar 26, 2019

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.

@tonysneed
Copy link
Author

I'll spread the word!

I can also help with the effort if we discuss the strategy for how this could be implemented.

@gdevolder
Copy link

Any update on this? Would really appreciate a version upgrade!!

@miladsleiman
Copy link

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.

@CDargis
Copy link

CDargis commented Sep 4, 2019

+1

3 similar comments
@DieterDR
Copy link

+1

@shivawahi
Copy link

+1

@rv-amadden
Copy link

+1

@normj
Copy link
Member

normj commented Feb 1, 2025

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

@normj normj closed this as completed Feb 1, 2025
Copy link
Contributor

github-actions bot commented Feb 1, 2025

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved. l Effort estimation: large module/lambda-test-tool p2 This is a standard priority issue queued
Projects
None yet
Development

No branches or pull requests