I'm running a test .Net Core Console app to try using ServiceBus messages. However after using Nuget to install Microsoft.Azure.ServiceBus v3.1.1 I get the following error
Package Microsoft.Azure.ServiceBus 3.1.1 is not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1). Package Microsoft.Azure.ServiceBus 3.1.1 supports: netstandard2.0 (.NETStandard,Version=v2.0)
I've tried installing up to v3.3.0 and get the same, I'm using the latest .Net framework and have updated my VS2017 so I don't know what the problem can be. Has anyone else had this issue?
I don't know what the problem can be
No matter the version of package Microsoft.Azure.ServiceBus is v3.1.1 or v3.3.0, both of their Dependencies is .NETStandard 2.0 while your app is .NetStandard 1.0. So, as Peter said, the version of .net core you have is too old.
You could go to download the latest .Net Core SDK and then reinstall the package you want.
Or you could download the Microsoft.Azure.ServiceBus v1.0.0. However, because the version is too old, some feature may not have. So, I suggest that you could update your TargetFramework to .net core 2.0+.
Your console app needs to have a TargetFramework .net core 2.0+ (Check in .csproj file), download latest .NET Core SDK and create a new .Net core console app to install the package again.
Related
I have two .net core applications running on Linux.
One of them is happy with .net core runtime while another one is demanding .net core SDK.
I can build both applications using dotnet publish with the following parameters:
dotnet publish Web/Web.csproj -o publish -c Release -r linux-x64 --self-contained false
Both projects target 3.1 (checked .csproj):
<TargetFramework>netcoreapp3.1</TargetFramework>
I am deploying them to the same VM server which has .net 3.1 runtime installed:
.NET Core SDKs installed:
No SDKs were found.
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.10 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.10 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
However, on start of one of those projects as systemctl service I am getting an error:
It was not possible to find any installed .NET Core SDKs
Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from:
https://aka.ms/dotnet-download
While I can successfully start the application manually using dotnet Web.dll
Does my build artifact requires SDK?
Any ideas how can I troubleshoot this behavior?
1- No, it shouln't require SDK
2- Hard to help you with the incomplete question
Have you tried to run the service with SDK installed? To check if that is the actual problem or just a misleading error.
Are you using Systemd integration package by Microsoft?
dotnet add package Microsoft.Extensions.Hosting.Systemd
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.
I have a VS2015 project that I have successfully deployed on Azure (via Github) as a web app.
However, after some offline updates, when I deploy, i get the error
The 'System.Net.Http 4.0.0' package requires NuGet client version '3.0' or above, but the current NuGet version is '2.8.60717.93'."
Is nuget 3.0 installed on the web app servers? And how can I use it?
I ended up reverting the System.Net.Http 4.0.0 package to an older version, that works with NuGet version 2.8.60717.93.
NuGet doesn't go on the the app server, it goes on the build server. Make sure your build server has the latest NuGet client. See this SO Answer.
My Mobile Service worked great till I install 'Microsoft.WindowsAzure.Storage': 4.3.0.0 through NuGet from Visual Studio.
After the installation of it, Mobile Services shows
Error
Found conflicts between different versions of the same dependent assembly 'Microsoft.WindowsAzure.Storage': 4.3.0.0. Please change your project to use version '3.1.0.1' which is the one currently supported by the hosting environment.
Does Mobile Service only support 3.1.0.1 not the latest one? Or any other configuration I can modify to make it work?
much appreciated for your response.
Oh, there's already a solution and I verified correct.
http://blogs.msdn.com/b/jpsanders/archive/2014/10/10/azure-mobile-services-net-backend-found-conflicts-between-different-versions-of-the-same-dependent-assembly.aspx
backup your project.
find a clean packages.config
copy content from it and replace to my existing problematic packages.config
open the package manager console and type: Install-Package WindowsAzure.Storage -Version 3.1.0.1
Clean the Build. Then Build
Publish again to Azure Mobile Services.
done.
Bottomline: if you want to use Mobile Services, PLEASE DO NOT USE NuGet to install latest WindowsAzure.Storage cause Azure Mobile Services currently doesn't support the latest Storage client which is very weird.
I had the same problem when working on an Azure Mobile Service project (.NET Backend). However, I could not downgrade to Azure.Storage 3.1.0.1 because it requires Ms.Data.OData; 5.6.0 (exact version). Even having the assemblyBinding which redirects all versions to MS.Data.OData to 5.6.2, still did not work.
At the end, I had to uninstall almost all Nuget packages, including Azure.MobileServices.Tables, .BackEnd, and .Enitity. This removed almost all Nuget packages. After that, I was able to install WindowsAzure.Storage 3.1.0.1
Install-Package WindowsAzure.Storage -Version 3.1.0.1
Then reinstalling all the packages that I removed earlier (Azure.MobileServices.Tables, .Backend, etc). This worked for me. Hope it helps somebody else too