Is it possible to use Lambda Layers with references to .dll files?

[SSkupien]

Hi, I would like to create a Layer with custom libraries (.dll). Is it possible?
From my research, I found out that layers for .NET lambda works with NuGet references.

Details:
I want to deploy many Lambda functions that all of them would use the same model/methods that I have implemented in my .dll library. I would like to create a layer with that .dll so I won't need to have this library in every lambda .zip.
I know that I can create NuGet from my library and that way create a layer and have it working but this way each time I would like to upgrade version of my library it will require an update for all of lambda's even when having backward compatibility in .dll. All because of the specific version reference in lambda for NuGet.
If it will be possible to have reference to .dll in the layer then I would be able to update .dll library and then update Lambda's one by one when I would like to.

[normj]

Using .NET's runtime package store feature, which is created from NuGet packages, is certainly the easiest way to include additional dlls to a .NET process. If you create a layer with just dlls then it would be up to you to explicitly load those assemblies into your process. I would not recommend doing that because that ends up ignoring the deps.json file and child dependencies of your library might not be found.

To create a layer from NuGet package you don't necessary have to publish the packages with different version numbers. You can create the packages in a separate folder and then just add that folder to your list of NuGet sources when creating the layer.

Keep in mind Lambda layers themselves are versioned. So if you make a bug fix in your library and create an update the layer for it you still have to update all of your existing Lambda functions to use the new layer version.

[github-actions]

This issue has not recieved a response in 2 weeks. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

[sohail-sf]

But I have written a blog regarding publishing custom DLL's on lambda layer if it is very essential for some one
https://medium.com/@sohail-dev/publish-custom-dlls-to-aws-lambda-layer-e4ac37a59b85