- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 126
Support ASP.NET Core 3.0 #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Will try it soon. Thanks for head up. |
The docs for the reference: @HamedFathi, I don't see a problem if you don't return |
@dadhi .NET Core 3.0.100-preview3-010431
Related link: |
Instead of creating the Container in your Startup, you may just move it to the host ( In addition, |
This is strange, could you share this sample application with me? |
Sure, You can find it here |
I tried to build the sample in vs2019 and .NET Core 3 preview 3, and after some quirks got the same error. Not sure the reason, but it shoud not relate to DryIoc itself. DryIoc is strongly signed now, is it a problem? or is it a binding redirects? Not sure. But won't spend much time on it until RC. If you have ideas, please help. |
I think a possible workaroud would be the use of source code package for DryIoc.MS.DI, which is not existent. Maybe it is time to make it , hmmm... |
I have published DryIoc.Microsoft.DependencyInjection.src source package and will try it. |
You can not define a return type for
ConfigureServices
in ASP.NET Core 3.0. I got an error on this.Can you show me how to use you amazing IoC with ASP.NET Core 3.0 preview 3?
The text was updated successfully, but these errors were encountered: