Need help structuring a class library for internal tools
Hi there, I'm working on creating an internal tool for exposing some commonly used functionality that requires external binaries.
So we have a business critical core application that consists of many modules. These modules all have their own APIs available through .dll files. Assume
When we create solutions, tools or integrations we often use some subselection of these modules, but rarely all. Currently we bake this into the solutions by moving the relevant binaries we'll be using into the repository so that it'll be available to the CI / CD pipelines.
But ideally I'd want to have this as a nuget package from our private nuget repo instead. So instead of finding the binaries we need and physically move them into our repo, I'd prefer something like
However I've never really done this before. I assume this means I'll create a class library called
So we have a business critical core application that consists of many modules. These modules all have their own APIs available through .dll files. Assume
Customers.dllFinance.dllProducts.dllIProductServiceIProductConfigurationServiceWhen we create solutions, tools or integrations we often use some subselection of these modules, but rarely all. Currently we bake this into the solutions by moving the relevant binaries we'll be using into the repository so that it'll be available to the CI / CD pipelines.
But ideally I'd want to have this as a nuget package from our private nuget repo instead. So instead of finding the binaries we need and physically move them into our repo, I'd prefer something like
nuget install OurCoreApp.Customersnuget install OurCoreApp.ProductsOurCoreAppHowever I've never really done this before. I assume this means I'll create a class library called
OurCoreApp
