Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I have not found a way of doing what I asked for in the question. However, from looking at Microsoft.Extensions.[...] packages, it seems .NET follows a different approach: For ease of developme...
Answer
#1: Initial revision
by
raphaelschmitz
·
2023-11-12T09:51:22Z (about 1 year ago)
I have not found a way of doing what I asked for in the question. However, from looking at `Microsoft.Extensions.[...]` packages, it seems .NET follows a different approach: - For ease of development, things are put into different projects/NuGet packages - For ease of consumption, things _are_ put under the same namespace, even though they might be in different project. For example, `IConfigurationBuilder` from the NuGet package `Microsoft.Extensions.Configuration.Abstractions` is available in the namespace `Microsoft.Extensions.Configuration`.