On VisualStudio 2017 there is a checkbox to automate the NuGet package generation on build when compiling .net core libraries.
But I have to generate the symbols package manually. Is there a way to automate it?
Thanks!!
Related
Visual Studio lists AutoMapper 11.0.1 in the Nuget packages Updates list when all projects target .NET Framework 4.8, which is incompatible with 11.0.1. Is this normal, or is there an error in my solution configuration, a bug in Visual Studio or something else? When I attempt to install it I get this error - Could not install package 'AutoMapper 11.0.1'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.8', 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.
I am trying to create a nuget package from a class library project in Visual studio 2015, In Project properties ---> package tab is not available/ visible.
IN the package tab we define the nuget package details.
Is it because of the visual studio 2015 issue or should I look for it somewhere else ?
VS2015 IDE does not support that.
The Package tab(Generate Nuget package on build) is the feature of new sdk style lib project.(Net Core and Net Standard).
And the new sdk projects are released since VS2017 while VS2015 does not support it -- You can not create any Net Core or Net Standard projects and only the Net Framework lib projects which does not contain the feature.
So you should use VS2017 or later VS and then create a Net Core or Net Standard lib project and then you can find it.
A NuGet package is published with many, many assemblies. Not all assemblies in a NuGet package need to be referenced in the *.csproj in Visual Studio. How does Visual Studio determine which assembly to reference? Is the logic for this in nuget.exe or is it in some NuGet API?
How does Visual Studio determine which assembly to reference? Is the logic for this in nuget.exe or is it in some NuGet API?
This determine should be a combination of nuget.exe and NuGet API in Visual Studio. Visual Studio use NuGet.exe to download the package, then use the NuGet API in Visual Studio to install the corresponding assemblies to the project.
First, NuGet supports putting multiple versions of the same library in a single package when using the convention-based working directory. So we will use different case-sensitive framework names to specifically target multiple frameworks with subfolders under lib:
lib\{framework name}[{version}]
Then we will use NuGet API in Visual Studio to install the package to project, it tries to match the framework name of the assembly with the target framework of the project.
Besides, NuGet Package Manager for Visual Studio is an instance of the combination of nuget.exe and nuget API, so Visual studio knows which assemblies in a NuGet package to reference.
You can refer to the NuGet document Supporting multiple .NET framework versions for more detail info.
I am trying to install JSNLog through Package Manager Console in Visual Studio 2010 as per the instructions given in http://www.jsnlog.com/Documentation/DownloadInstall but I am getting installation error...as below.
I am wondering that has something changed with the command ?? and also how can we restore the missing NuGet packages from the project solution -- I updated the NuGet version
Environment I have is
Visual Studio 2010 Professional and NuGet from https://www.nuget.org/api/v2/
Main Purpose of using JSNLog is to implement client side Logging in my project...
Any thoughts pelase...
PostSharp 3 is available only as a visual studio extension. Visual Studio Express don't support extension. Is there a way to use PostSharp 3 with Express version of Visual Studio?
Previously we use PostSharp 2.1 as an external tools with free PostSharp express license, but currently this license is not available.
Here is an answer from PostSharp tech support:
PostSharp 2.1 Starter editions are not available any more. However, PostSharp 3 does not work in VS Express.
Now it is possible, using Nuget package. Actually, you should add reference to Postsharp Nuget to all projects that are failed for compile.
In my case, I have a postsharp reference in some referenced project and Console app project and WebApplication projects required to have reference to package too.
To provide license just go to package folder and run Postsharp.HQ.v.3.0.exe