I have a "new" windows xp sp3 machine with VS2010 SP 1 and Nuget 1.8
Every time a try to add a Nuget Package a receive the following error:
The specified cryptographic algorithm is not supported on this platform.
Does anyone know what does that means?
There's a known issue with NuGet 1.8 : NuGet issue#2240. The Nuget team will soon (crossing fingers) release a hot fix.
In the meanwhile, I'd suggest installing NuGet 1.7.
EDIT: NuGet released the hotfix (1.8.30524.9000)
Related
I have been doing some testing between VS2015 and VS2017. I created a .NetFrameworkApp and a .NetCoreApp website in both systems. I then installed a couple of packages in all four websites; in particular EntitytFramework. It installed in both VS2015 websites and the VS2017 .NetFrameworkApp website without problem but it wouldn't install in the VS2017 .NETCoreApp website. I got the following error messages.
net45 (.NETFramework,Version=v4.5)
One or more packages are incompatible with .NETCoreApp,Version=v1.1.
Package restore failed. Rolling back package changes for 'RLSBCWebSite_NC'.
Time Elapsed: 00:00:01.4470850
Error Package restore failed. Rolling back package changes for 'RLSBCWebSite_NC'. 0
Anyone any idea why that should be. I am assuming it should install otherwise how would you use CodeFirst etc.
The "EntityFramework" package is not supported with .NET Core App, use the:
Microsoft.EntityFrameworkCore.SqlServer
package instead
With NuGet 3.3.0 we get the following error when restoring AutoMapper 5.1.1. Other packages restore successfully:
[11:49:53] [restore] Unable to find version '5.1.1' of package 'AutoMapper'.
[11:49:53] [restore] Process exited with code 1
There was an issue we had where we were unable to restore this package in Visual Studio 2013 on our dev machines unless we updated the NuGet package manager.
If we build the project in Visual Studio 2013 on the TeamCity server, the package restores successfully, leading us to believe that it's the NuGet version on the build agents that needs updating.
We tried to upload the NuGet.CommandLine.3.4.3.nupkg via the TeamCity | Tools menu, however TeamCity complains that it's not a valid NuGet package because it doesn't contain tools\NuGet.exe, even though it does!
We did manage to successfully upload Nuget.CommandLine.3.6.0-beta1.1839.nupkg, however that gives us a different error when the build step attempts to run.
So we're stuck. Has anyone out there had this issue and managed to resolve it?
Uploading NuGet.CommandLine.3.5.0-beta-final.nupkg to TeamCity (Administration => Tools => NuGet.exe => Add Version) and setting the NuGet build step to version 3.5.0-beta-final successfully resolved our issue.
I got the package from: https://dotnet.myget.org/feed/nuget-build/package/nuget/NuGet.CommandLine/3.5.0-beta-final
This is not the first time it has happened, so I assume it's a bug where in the pipeline of NuGet Client / Visual Studio / NuGet server. A package has just been updated on NuGet.org. The latest version is 3.0.0.14. When I went to upgrade my package it couldn't find it and it said I had the latest version. After using Fiddler to see what was going over the wire, it's clear the NuGet Server is not serving the latest information. This call returns version 3.0.0.13 as the latest version.
https://api.nuget.org/v3/registration1/tweetmoasharp/index.json
Is that a bug on NuGet Server? Do they have a deliberate caching? Is it something the package publisher did that he didn't mark as a stable version?
So I installed a local NuGet server using the NuGet.Server package and VS2012. Everything seems to work fine, I have a package that I created based on a web application. The server knows about the package (i.e. I can list it using "nuget list"), but when I try to install it on the target machine, I get an InvalidDataException with a message the the Archive file cannot be size 0.
I am using Win7 x86 and the command-line nuget.exe utility from within PowerShell. Nuget.exe is in \windows.
Also, I can install packages from the public nuget.org server on this target machine.
In an interesting twist, I am able to install the very same internal package from the very same internal server when I run the same command from within the Package Manager Console in VS2012. I have verified that the nuget.exe versions are the same.
Any help on this?
Thanks,
Matthew
Turns out there was an issue with the local Nuget cache. Once I cleared it out, the package installed correctly.
All articles say that SignalR can be installed from
Microsoft.AspNet.SignalR
nuget package.
But this package is not available through nuget interface in VisualStudio but only if you install from the console.
Install-Package Microsoft.AspNet.SignalR
Why?
Also it's not available here http://nuget.org/packages?q=signalr
Can you somebody explain what the right way to install SignalR?
SignalR is still pre release so you need to install it from the command line with the -pre option. From what I've heard it should be available in the next RTM update.
It is found here in the gallery: http://nuget.org/packages/microsoft.aspnet.signalr
Use Install-Package Microsoft.AspNet.SignalR -Pre to install from the console.
you can use the Manage Nuget packages UI in VS to install pre-release packages as well
http://docs.nuget.org/docs/release-notes/nuget-2.2 has instructions on how to do it as well