I am using font-awesome 4.7 sass in asp net core project and want to update to version 5.12.1.
unpgk in VS 2019 offers only 4.7
FontAwesome 5 has been released under a new official package name: #fortawesome/fontawesome-free
You just have to change the package name declaration and refactor all your existing classes from fa to fas.
See also this answer post on StackOverflow.
Related
When I try to add the Orc.Controls package v4.2.8 from Nuget I get the error "You are trying to install this package into a project that targets '.NETFramework,Version=v4.7', but the package does not contain any assembly references or content files that are compatible with that framework." The documentation page https://opensource.wildgums.com/ says that .NET 4.7 is supported. Am I doing something wrong, or does the pacakge just not support .NET 4.7?
According to nuget, 4.1.1 was the last version to support .Net Framework 4.7, you can install that version with: Install-Package Orc.Controls -Version 4.1.1
The current version is >= .NET Core 3.1.
I had to make a .NET project in Linux using monodevelop. When I tried monodevelop in Ubuntu I got an error message when I used nuget at certain packages saying my version is 2.8 and I needed 2.12 or earlier.I updated nuget package successfully in terminal but monodevelop uses 2.8 no matter what I do. The nuget package I can't use because of this is Tweetinvi.
In order to solve this I have to either add tweetinvi without using nuget or manage to use nuget 2.12 running from outside monodevelop, which I could not find out how to do.
https://github.com/linvi/tweetinvi
MonoDevelop does not use the NuGet version supplied by Mono that is available from the command line. So updating the command line version of NuGet will not resolve any problems with MonoDevelop.
More recent versions of MonoDevelop use later versions of NuGet.
The last MonoDevelop version 5 release was version 5.10 which supports NuGet 2.8.7.
Support for MonoDevelop 2.12 was added in MonoDevelop 6.0.2. NuGet v3 support was added in MonoDevelop 6.1. Currently MonoDevelop 6 is only available as a FlatPak package unless you build it from source.
If you cannot build MonoDevelop from source you may be able to upgrade NuGet by copying the NuGet.Core.dll from the mono/nuget-binary GitHub repository and copying it into the NuGet addin directory addins/MonoDevelop.PackageManagement, but take a backup copy of the original NuGet.Core.dll before you do that so you can rollback the change if it does not work.
I am the developer of the library and the installation of the library without nuget is not supported on mono because I do not have enough time to look into it.
Tweetinvi supports mono > 4.5 with nuget.
Running into a situation where I deployed an application to production a few months ago and now I need to do some work on it, on an entirely new machine. The first I do is pull source and nuget restore won't restore because it can't find the particular version of the package it was developed under. When I check nuget.org for this package version it is not there. So how do I upgrade my solution to the latest binaries?
Visual Studio 2013 trying to update ServiceStack '4.0.39' to latest, which is '4.0.40' at the time of this post.
Thank you,
Stephen
The best solution I've come up with for this is to manually edit the Packages.config file(s) and set the version number to whatever you want. Restore should then work. It's not a perfect solution but it has dug me out of some holes.
(I know this is an old answer, but it just came up in some Googling)
One issue with the accepted answer (of just updating the version # in packages.config) is that this is just triggering a "package restore"--and will skip any "installation steps" the package might have (things that were done automatically when you first added the package, such as adding assembly references, modifying config files, etc.).
An alternative way would be to edit the packages.config and REMOVE the package in question from there---then start up VS and add the new version. This will trigger the package's usual install routine to do it's thing.
I recommend you to use the NuGet Package Manager Console of Visual Studio:
TOOLS > NuGet Package Manager > Package Manager Console
Command to update a NuGet package to the latest version:
Update-Package ServiceStack
Command to update a NuGet package to a specific version:
Update-Package ServiceStack -version 4.0.40
I updated Xamarin Mvvmcross 3.2.2 project to 3.5 for Unified API support.
Mvvmcross.HotTuna 3.5 package is added in project.
So there are Mvvmcross.HotTuna.CrossCore and Mvvmcross.HotTuna.MvvmCrossLibraries packages can be seen under Package folder.
But cannot find binding assemble, so "using Cirrious.MvvmCross.Binding;" is not resolved.
And MvxTouchSetup is also not resolved
The project worked well with Mvvmcross3.2.2.
Now what other nuget packages should be added in the project?
No package is added newly.
The 3.5 libraries package has been updated to include the new MvvmCross.Touch.dll for lib\Xamarin.iOS10\ - see https://github.com/MvvmCross/MvvmCross/blob/3.5/nuspec/MvvmCross.HotTuna.MvvmCrossLibraries.3.0.1.nuspec#L72
The 3.5 crosscore package has bee update to include the new MvvmCross.Binding.Touch.dll for lib\Xamarin.iOS10\ - see https://github.com/MvvmCross/MvvmCross/blob/3.5/nuspec/MvvmCross.HotTuna.CrossCore.3.0.1.nuspec#L91
If the update isn't working for you:
read the advice on http://kerry.lothrop.de/unified-api-for-xamarin-ios/ about how to update the unified
check you have updated your own project to Xamarin iOS unified
check you have up-to-date nuget installed
clean, rebuild, swear and retry until it all works
I have updated xamarin ios from classic api to unified api.
When i trying to add Mvvmcross nuget package it shows following error
Could not install package 'MvvmCross.PortableSupport 3.2.2'. You are trying to install
this package into a project that targets 'Xamarin.iOS,Version=v1.0', 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.
The MvvmCross.PortableSupport 3.2.2 NuGet package contains an empty Portable Class Library folder and can be installed into a Xamarin.iOS project if you have the Portable Class Libraries installed for Xamarin and if you have the latest version of NuGet installed.
So you may not have the PCLs installed for Xamarin or, if you are using Visual Studio, then your NuGet version may be too old and need to be updated.
To get the Portable Class Libraries:
If you are on the Mac you should install the Mono Development Kit (MDK).
If you are on Windows then things are can be more complicated. The simplest way is to install Visual Studio 2013 (full or Express) Update 2 or higher. The more complicated way is to install the Portable Library Tools and the Portable Library Reference Assemblies 4.6. The Portable Library Reference assemblies installs a PortableReferenceAssemblies.zip file which contains three directories (4.0, 4.5 and 4.6). These three directories need to be extracted and copied into the PCLs directory:
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETPortable
Finally on Windows you would then need to reinstall Xamarin. The easiest way to do this is to find Xamarin in the Control panel's Programs and Features and select the option to Repair it.