LambdaTestTool: The tool doesn't work if I change the working directory to my build path. #1976
-
|
For my dotnet application, I have a custom base path and custom output path. So, when I change the working directory for the tool to my build path as there is no bin folder for my application. It doesn't read the DLLs. But surprisingly, when I copy the files from the custom build path to the bin folder (manually created), it works. Do we have a bug here? Default configuration works when bin exists: Custom path to the build: The custom path doesn't load the config and handlers in the tool. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @Neelabhra08 We are actually working on a new version of this tooling that you can find here https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool-v2. Admittedly the documentation is light right now as we are still in preview and our first focus is integrating the new tooling with .NET Aspire. We do have documentation coming from the .NET Aspire side via our tracker issue you can find here: aws/integrations-on-dotnet-aspire-for-aws#17. I would really appreciate if you could try your use case through .NET Aspire integration and see how it works for you. |
Beta Was this translation helpful? Give feedback.
-
|
@normj Thanks for the answer. I will check it out. |
Beta Was this translation helpful? Give feedback.
Hi @Neelabhra08
We are actually working on a new version of this tooling that you can find here https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool-v2. Admittedly the documentation is light right now as we are still in preview and our first focus is integrating the new tooling with .NET Aspire.
We do have documentation coming from the .NET Aspire side via our tracker issue you can find here: aws/integrations-on-dotnet-aspire-for-aws#17. I would really appreciate if you could try your use case through .NET Aspire integration and see how it works for you.