-
Notifications
You must be signed in to change notification settings - Fork 174
Cannot add NuGet packages #584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Try replacing
with
|
Thanks for the tip, sadly it doesn't make a difference... |
you have an error
can you set omnisharp log level to trace and capture the output again? |
Thanks for the hint. I think I found two possible bugs....
|
I have added the official package source and it works. Not sure if above are still bugs to look at or if we can close this.
|
This is by design. dotnet-script will respect nuget.config to give you the ability to point to custom nuget feeds. Since NuGet 3.4 the nuget behavior is such that it will look in the project's directory or "or any folder up to the drive root" to locate the config file https://docs.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior |
I am trying to use a NuGet package with dotnet-script. I have initialized a new script project as explained and added this into the main.csx file and restarted omnisharp. The using directive is always underlined with "Type or namespace could not be found". I even do not see that any NuGet packages were downloaded.
Here is the log
The text was updated successfully, but these errors were encountered: