Timeline for How to register DI Services in .net core class library?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15 at 7:49 | answer | added | Davide Messori | timeline score: 1 | |
| May 15 at 7:41 | comment | added | Steven | It would be good to get familiar with the topics of Composition Root and DI-Friendly libraries. Big question though is: are you creating a reusable library or simply a class library that is used solely within a single solution? | |
| May 15 at 7:26 | history | edited | David Osborne | CC BY-SA 4.0 |
Grammar and structure.
|
| May 15 at 6:52 | comment | added | Damien_The_Unbeliever | Consider that Microsoft themselves supply many optional libraries and almost all of them expose extensions that you're expected to call from the main application's service registration code. They don't attempt to "automagically" register with the DI system. Why do you think your class library is different? | |
| S May 15 at 6:43 | review | First questions | |||
| May 29 at 6:46 | |||||
| S May 15 at 6:43 | history | asked | shah Taymur | CC BY-SA 4.0 | created from wizard |