![]() This approach allows the various dependent solutions throughout our codebase to use the package within the same repository instance. There's a shared library within the codebase that's published/deployed as a. My use case for this functionality is that I have multiple instances of a single code repository on my machine. Here's an example nfig to get you started: (You'll see the source(s) listed in the Package Manager, and you'll find the packages on the "Browse" tab when you're managing packages for a project.) nupkg files from those source folders will be available. ![]() When you next open the solution in Visual Studio 2017, any. Configure the file with the package source(s) you want. You need to create a nfig file in the same directory as your. This will add a package source that only applies to a specific solution, and you can use relative paths. Local NuGet packages using a relative path But that means your dependency's location isn't committed (to version-control) with the rest of your codebase. What most people do is go into the NuGet Package Manager and add the local folder as a source (menu Tools → Options → NuGet Package Manager → Package Sources). You first have to tell Visual Studio about the location of your package, and then you can add it to a project. (That's likely because the PackageReference element doesn't support file paths it only allows you to specify the package's Id.) You can no longer just use Install-Package to point to a local file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |