I would like to create a Visual Studio Nuget package for work. I also want to develop a Visual Studio extension to allow right-click deploy functionality for me and my co-workers. My question is: can I accomplish both of my requirements using the Nuget package alone, or do I have to develop a Nuget package and extension separately? If I have to do them separately, how can I roll the extension into the Nuget package so it can all be delivered together?
Related
In my class library, Manage Nuget Packages shows the latest stable version of Newtonsoft as 12.0.3. In another application that references the class library, Manage Nuget Packages shows the latest stable version of Newtonsoft as 9.0.1
What would explain that difference, and how is it fixed in Visual Studio 2019? When I try to compile the application, it fails with the error that the class library's version of Newtonsoft is newer.
EDIT: I think I've found the reason: in the top right corner of the window the package source for the application was not nuget.org but Visual Studio Offline Sources.
Why is the latest stable version of Newtonsoft showing in Nuget
Package Manager as 12.0.3 in one project and as 9.0.1 in another?
When you install a nuget package, you should select the right nuget package source.
As it shows that, Visual Studio Offline Sources is your local nuget caches. It is required that you download the corresponding nuget version and then exist in this data source. So it depends on you and not all versions of the package are fully displayed.
nuget.org is the ultimate destination for developers releasing nuget packages. You can find every version of the package here. So you should check this link.
Check and enable that link.
Then, open Nuget Package Manager UI and choose nuget.org and you can find it.
How to build a VSTS extension in Visual Studio 2017. The post build event configured in package.json doesn't work from Visual Studio.
Only the Command npm run build triggers the build and postbuild events. I want vsix file to be created on building the VisualStudio 2017 project.
We cannot build directly to generate the vsix file in VS. Just as you said we can only trigger the postbuild events to call the command tfx extension create --manifest-globs vss-extension.json to package it.
To create TFS/VSTS extensions, you can refer to this article for detials :Create your first extension with Visual Studio
To package as the vsix file, please see Packaging and publishing - Package
If you mean create Visual Studio VSIX Package, then you can reference below articles:
Creating Your First Visual Studio VSIX Package
Visual Studio Extensibility: Creating Visual Studio VSIX package
extension
Added the new Package using Package Manager console or manage nuget packages in Project it's not added project it's Throw below Error.
I was Check some Links Not give proper reason. why this problem in coming in vs2017
Anyone Know Share the knowledge.
Thanks in Advance
Visual Studio 2017: Package Restore failed, Rolling back Package changes for 'Projectname'
You could not install the package exceldatareader.dataset to the UWP project. That because this package only have the .NET Framework assemblies, which is not compatible with UWP project. You can download that package from nuget.org, then open it, you will find this package only have the assemblies for .NET 2.0 and .NET 4.5:
So this package is not compatible with UWP project, you can find the error message in the output window when you install it to the UWP project:
Hope this helps.
I'm working with RESTful webservice, getting error while adding package "System.Net.Http";
"The 'System.Net.Http 4.0.0' package requires NuGet client version '3.0' or above, but the current NuGet version is '2.8.5.0'. "
So, to resolve above error i'm trying to install "NuGet client" from "Add Package" option in xamarin studio, but this time I'm facing another issue that is;
"Could not install package 'NuGet.Client 3.2.0'. You are trying to install this package into a project that targets 'portable-net45+win+wp80+MonoAndroid10+xamarinios10+MonoTouch10', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author."
please help to resolve this issue.
Xamarin Studio currently does not support NuGet 3. It is currently only supported in Visual Studio 2015.
It is not possible to upgrade Xamarin Studio so it supports NuGet 3 at this time. Installing the NuGet.Client NuGet package does not upgrade NuGet in Xamarin Studio.
I would instead look at using the Microsoft.Net.Http NuGet package which you can install into a portable class library project (PCL) and supports all Xamarin Android and Xamarin iOS projects.
I was able to grab a copy of System.Net.Http.dll from another project and manually add it as a reference to my Xamarin project. I put it in the packages folder and then browsed to it from the edit references dialog.
For people facing problem trying to add System.Net.Http...
I was able to solve the problem by using Microsoft.Net.Http instead of System.Net.Http. In Xamarin studio, Right click on your project > Add > Add NuGet Packages.. > search for "Microsoft Http Client Libraries" and click Add Package.
There is a build server without Visual Studio, there are only build tools (MSBuild.exe, Nuget Manager,...). The Nuget Packet Manager need to upgraded to new version, but I cannot find any installer or way how to upgrade it without Visual Studio Gallery.
How shoudl I upgrade the Nuget Manager on build server?
The latest version of the nuget.exe command-line tool is always available from http://nuget.org/nuget.exe.
More details