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.
Move the Scan extension under the Microsoft.Extensions.DependencyInjection namespace
See original GitHub issueThis will avoid include the using Scrutor and is the way Microsoft and third party components extends the framework.
some examples:
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Microsoft.Extensions.DependencyInjection Namespace
Provides classes that support the implementation of the dependency injection software design pattern.
Read more >Microsoft.Extensions.DependencyInjection
Provides extension methods for Microsoft.Extensions.DependencyInjection.IServiceCollection implemenations.
Read more >Why should I put my own classes in a Microsoft.* ...
We recommended that apps follow the naming convention of creating extension methods in the Microsoft.Extensions.DependencyInjection namespace.
Read more >DO NOT use the Microsoft.Extensions. ...
We recommend that apps follow the naming convention of creating extension methods in the Microsoft.Extensions.DependencyInjection namespace.
Read more >Using Scrutor to automatically register your services with ...
In this post I describe how to use the open source library Scrutor to add assembly scanning capabilities to the ASP.NET Core DI...
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
Sure, I guess we could do that. This is a binary level breaking change, though, so I think we’ll have to spare this for when we’re going for a new major release 😄
After some try, I think if we want to move the extension under
Microsoft.Extensions.DependencyInjectionnamespace, it is easier to give a small breaking change without trying giving backward compatibility.I will PR soon, then you will decide, BTW I think is the good direction.