Fix #2208: Add handler configuration documentation#2221
Fix #2208: Add handler configuration documentation#2221
Conversation
- Add Handler Configuration section to AspNetCoreServer.Hosting README - Document executable vs class library handler modes - Explain Main(string[] args) pitfall causing JsonSerializerException - Provide clear code examples for correct handler setup - Address community confusion about Lambda handler configuration
|
That works for me. The AWS docs themselves could use some love there too but I don't think those are on GitHub. So here |
|
|
||
| When deploying your Lambda function, the handler configuration depends on your project structure. | ||
|
|
||
| ### Executable Mode (Recommended) |
There was a problem hiding this comment.
This is the README for Amazon.Lambda.AspNetCoreServer.Hosting which always has the Lambda function deployed as an executable. The doc update should be explaining how for this library the executable programming model is always used and the function handler must be set to the assembly name.
You can remove the Common Configuration Issue section because once they know to deploy as an executable that is a non-issue.
There was a problem hiding this comment.
I updated it. Let me know if you have further feedback.
Issue #, if available:
Fixes #2208
Description of changes:
This PR addresses the documentation gap identified in issue #2208 by adding a comprehensive "Handler Configuration" section to the AspNetCoreServer.Hosting README.
Changes Made:
Main(string[] args)with incorrect handler configuration causes JsonSerializerExceptionCommunity Impact:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.