I've nearly finished migrating a large solution to use NuGet for dependencies. Prior to this, the project simply had a Lib directory with all binary dependencies in sub-directories within it. There are, however, a few dependencies that aren't available in the official NuGet feed. Therefore, I have a few options:
- Add them to the official NuGet feed.
- Keep the existing Lib directory with any non-NuGet binaries within it.
- Create a project-local NuGet feed that contains only those packages that aren't available in the official feed.
I don't like #1 because it implies I'll be taking on responsibility for keeping the packages up-to-date. I don't like #2 because it's messy having two mechanisms for managing dependencies within the one solution.
Therefore, I'm leaning towards #3, but cannot find any documentation on conventions. I understand how to create the local feed, how to tell Visual Studio about it et cetera. What I can't find is whether there is a convention around the naming of the directory containing the local feed and anything else this approach may entail. Does anyone know what the standard practice is?