I can create a layer like this:
dotnet lambda publish-layer efk-KarlTest-ProcessFileLayer -sb efk-karltest -sp layers/ --layer-type runtime-package-store --package-manifest manifest.xml --framework net8.0
With this manifest:
But I get an assembly not found error for ‘Aspose.PDF’ when running the lambda. Have you tested this scenario? We would like to use a layer, because the dll size is enormous, and slows down our dev work.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): PDFNET-58780
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
I figured out the issue, finally. It was a bug on my end. What was happening, is for .NET Lambda functions with a layer, the CLI sets this special environment variable on the lambda:
DOTNET_SHARED_STORE=/opt/dotnetcore/store/
My scripts were removing that variable when I was setting my own env vars (DB Connection strings, etc.)
Now that I set that env var, all assemblies in the layer can be loaded. So you can close this ticket.