Trying to install this specific NuGet package in an offline VS2017 environment.
However, despite downloading the .nupkg file and saving it in the specified offline NuGet package directory under "NuGet Package Manager Settings", the package does not appear in the list in the NuGet package manager in VS2017.
Do I need to unzip the file first? Have tried that but receive the error that the .nupkg file does not contain a .nuspec file (despite clearly containing one in File Explorer).
Could someone with VS2017 try to install this specific NuGet package in an offline VS2017 environment and provide a clearly worded, unambiguous step-by-step guide on how to install the package?
Could someone with VS2017 try to install this specific NuGet package in an offline VS2017 environment and provide a clearly worded, unambiguous step-by-step guide on how to install the package?
To accomplish install nuget package in an offline VS2017 environment, please following below steps:
Manually download that nuget package, save it to your local location, for example, D:\Test\NuGet. You will get a file ending in .nupakg: nupengl.core.0.1.0.1.nupkg.
Open a command prompt with administrator from start menu, switch the path to where nuget.exe exists, for example, C:\Users\Admin. Then add the download package to the ffline NuGet package directory: C:\Program Files (x86)\Microsoft SDKs\NuGetPackages by below command:
nuget add "D:\Test\NuGet\nupengl.core.0.1.0.1.nupkg" -source "C:\Program Files (x86)\Microsoft SDKs\NuGetPackages"
After that, you will find the nuget package be added to the the offline NuGet package directory with a hierarchical layout:
Then you can use this nuget package when your Visual Studio 2017 without an internet connection:
Related
After installing vs 2022 and uninstalling it (because it doesn't support ODT - oracle developer tools).
Going back to the previous version (2017 or 2019) causes the NuGet package manager fails to install packages properly (all packages).
I've tried to install (for example) Newtonsoft.Json but it failed with the following error:
Error Install Log
I have tried to reinstall to NuGet package manager.
I have tried to reinstall VS (both 2017 and 2019).
Any help\ suggestions will be appreciated.
Thanks, Asaf
There are some Flatpak apps that have optional dependencies that are not bundled with the app. E.g the plotting package Veusz is available as a Flatpak and it can optionally use the Python package h5py to open HDF5 files. But h5py is not bundled with the Flatpak version. I saw a flatpak command flatpak enter that the documentation says allows us to
Enter the flatpak sandbox.
So I started the Veusz flatpak app and used flatpak ps to get its PID. Then I tried sudo flatpak enter PID pip3 install h5py but it installed h5py in my host operating system!
TLDR; Is it possible to install custom packages (not just Python packages) in a Flatpak application's sandbox? If yes, how shall I do it?
In general, you need to add an extension point and create a new package.
For example, add an extension point for the directory you need to add files (here lib/GL):
[Extension org.gnome.Platform.GL]
version=1.4
directory=lib/GL
and make a new flatpak package with the files to add (here org.gnome.Platform.GL).
In this case though, there may be some sort of issue. Looking at the metadata file for the Veusz flatpak here, they seem to be including hdf5 and h5py already. If you're missing this functionality you probably want to raise an issue in the repo.
I have a created a simple AWS Dotnet core API in visual studio and now I need to install Amazon.Lambda.Tools 3.1.1 NuGet package But, whenever I try to install this NuGet package I get this error
The error:
Package 'Amazon.Lambda.Tools 3.1.1' has a package type 'DotnetTool' that is not supported (Project name)
I am running VS 2017(15.9.3) on Windows 10 and Dotnet core 2.1.500
Any ideas!!
I was able to solve it by adding
Amazon.Lambda.Tools to csproj and then deleting Microsoft.AspNetCore.All from csproj
I have a problem with Visual Studio 2017. When I install any package, nuget manager not installs dependencies. For example, Microsoft.EntityFrameworkCore.Sqlite has 2 dependencies and I must install it manually.
Is it normal behavior? As I remember in the past nuget manager did dependencies installation automatically.
VS2017 NuGet: Dependencies not install automatically
Your package should be managed as packagereference. You could edit your project file .csproj to check it.
Unlike packages.config, PackageReference lists only those NuGet packages you directly installed in the project. As a result, the NuGet Package Manager UI and the project file aren't cluttered with down-level dependencies.
Besides, the dependencies info included in the project.assets.json in the obj folder. You do not need to install the dependencies manually.
You can check the document Migrate from packages.config to PackageReference for some details.
Hope this helps.
We are using Visual Studio Team Services for build and deployment of several sites. Some .NET and some are not. All working fine when using the hosted agent. Due to performance issues and long queue times for the hosted agent we need to use our own build agent.
Here comes the problem:
When running the VSTS builds we get an error when running bower:
******************************************************************************
Starting: bower install
******************************************************************************
C:\Program Files (x86)\nodejs\npm.cmd install -g bower
C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\npm\bower -> C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\npm\node_modules\bower\bin\bower
bower#1.7.9 C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\npm\node_modules\bower
Not found bower: null
******************************************************************************
Finishing: bower install
******************************************************************************
The problem is that bower is actually in that location:
And here are the actual bower build step:
How can we fix this Not found bower: null error?
There are known issues with tools installed into profile folders it has to do with permissions. It's easier to install the tool from an administrative console with the -g parameter. And ensure that the central NPM version is added to the service or system's %path% environment variable.
Or pass in a specific location by adding additional parameters to the call to npm: npm install --prefix "$(Agent.WorkFolder)" Bower Then specify the same location in the Advanced section of the Bower task.
Bower CLI location: $(Agent.WorkFolder)\node_modules\
(You'd need to check the exact location the package is installed to, I'm slightly guessing at the moment ;)).