Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
AWS Lambda uses netstandard 1.3 can we downgrade Windsor from netstandard 1.6?
See original GitHub issueThe package Amazon.Lambda.Core uses netstandard1.3 from NuGet and it also has runtime dependencies on:
Can we downgrade the current implementation to netstandard 1.3 and System.X 4.1?
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
How to downgrade .NetStandard 1.6 to .NetStandard 1.3
Based on the limited information provided, I would say you need to change the frameworks portion of your project.json and run dotnet restore....
Read more >Downgrade ASP.NET Core app from .NET 6.0 to . ...
NET 5.0. As a result, I now have to downgrade my project from .NET 6.0 to a previous version. However, I am facing...
Read more >NuGet Warning NU1605
Detected package downgrade: 'PackageB' from 4.0.0 to 3.5.0. Reference the package directly from the project to select a different version.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FYI I’m going to cut the release tomorrow.
@jonorossi it looks like the test done by @fir3pho3nixx is a good evidence that v4 will run on Lambda without any issue. I’ll try to work on another test during the afternoon (right now it’s 11:40 here in Sweden)
Anyway, thanks a lot for the attention to this specific use case 😃