During the Turning a .NET library into a VL library workshop I encountered a problem following the suggested workflow for installing NuGets for use with VL. This was caused by me having specified a repositoryPath in the User nuget.config. The result was that when running nuget install on the commandline after Quadmenu > Manage Nugets > Commandline the package was installed to the repository specified in my nuget.config and therefore not available in Gamma.
Solutions if you have NuGet configured to use a custom package repository which then will be used as default when running nuget:
-OutputDirectoryoption when invoking nuget, for example:
Quadmenu > Manage Nugets > Commandline and then in the commandline run:
nuget install SomeCoolNugetPackage -OutputDirectory .(see NuGet cli-reference):
- Put the following nuget.config in the gamma nuget folder (path revelead by:Quadmenu > Manage Nugets > Show Installed)
<?xml version="1.0" encoding="utf-8"?> <configuration> <config> <add key="repositoryPath" value="." /> </config> </configuration>
Maybe this information could be edited and go into the gray book?
Possibly gamma could ship with a nuget.config in the package repo dir used by gamma but not sure if that’s a good idea or not.