I have a solution with 3 library projects in it. I use dependency injection to create a loose connection between these projects, which:
- Services that are relevant features
- Domain
- Repository
So, ultimately, my NuGet package will only expose functions in the "Services", but the functions of the service use repository methods and domain objects. Therefore, everything should be included in my package.
Here where I am confused:
- How can I make sure that my NuGet package will contain all the necessary fragments in it, that is, domain objects and repository methods. Domain objects are expanded, but the repository methods are consumed only by service functions, so in the end they are not visible to users. However, my service functions need them, so they should be included in the package.
- I am also confused by linking three projects that are usually run at the top level. In other words, installing the NuGet package will not be sufficient, as dependencies will need to be resolved. For example, if I add my NuGet package to a new ASP.NET project, I will have to resolve these dependencies in my Startup.cs, which seems a bit inconvenient. Not sure how to handle this part.
- . , Azure, NewtonSoft.Json. , , NuGet .
NuGet?