When I deploy my .net core 2.1.0 project, I get the following error:
-----> Installing dotnet-framework 2.0.3
**ERROR** DEPENDENCY MISSING IN MANIFEST:
Version 2.0.3 of dependency dotnet-framework is not supported by this buildpack.
The versions of dotnet-framework supported in this buildpack are:
- 1.0.5
- 1.0.10
- 1.0.11
- 1.1.2
- 1.1.7
- 1.1.8
- 2.0.0
- 2.0.7
- 2.1.0
All solutions in my project is targeting the .net core framework 2.1.0, so I don't understand why this is.
I have dependencies in my project, and some of the them, like NETStandard.Library and Microsoft.NETCore.DotNetAppHost, are version 2.0.3, but does that really matter? (Also I don't think a version higher than 2.0.3 exist of NetStandard.Library.)
The project runs fine on my local machine, and ran fine on the host before we upgraded the buildpack and target .net framework, as well as various dependencies through NuGet.
Here is the full log:
https://1drv.ms/t/s!Ar81AKlFywcPhapTJdjZEnrcGrZS4A
You can try to pin the RuntimeFrameworkVersion to a specific one:
<RuntimeFrameworkVersion>2.0.7</RuntimeFrameworkVersion>
Related
According to this Microsoft blog post section, Package references in F# scripts
, I should be able to use the following syntax in an fsx script:
#r "nuget: FSharp.Data"
Unfortunately, the compiler gives me the following error:
The package management feature requires language version 5.0 use /langversion:preview F# Compiler(3302)
I believe I have dotnet.core 5.0 installed correctly:
dotnet --info
.NET SDK (reflecting any global.json):
Version: 5.0.100
Commit: 5044b93829
Runtime Environment:
OS Name: Mac OS X
OS Version: 11.0
OS Platform: Darwin
RID: osx.11.0-x64
Base Path: /usr/local/share/dotnet/sdk/5.0.100/
Host (useful for support):
Version: 5.0.0
Commit: cf258a14b7
.NET SDKs installed:
5.0.100-rc.1.20452.10 [/usr/local/share/dotnet/sdk]
5.0.100 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 5.0.0-rc.1.20451.17 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 5.0.0-rc.1.20451.14 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-downloa
How can I get this working correctly? Currently, the fsx script inside a dotnet core solution if that makes any difference. I'm using vscode with the ionide plugin to write F#.
Ionide doesn't yet support F#5.
As Isaac Abraham pointed out in his answer, the Ionide vscode package, at the time of this post, doesn't support F# 5.0 quite yet. However, the Ionide package helpfully does give the user the ability to enable a preview of F# 5.0 language features.
I fixed this compiler error by opening up the User's settings.json file and adding the following lines:
"FSharp.fsiExtraParameters": [
"--langversion:preview"
]
I have .NET Core SDK 3.1.200 installed on my local machine.
I create a Asp.Net Core app (using Visual Studio) targeting netcoreapp3.1. I test it and it works fine.
But when I commit it to CI the build fails to get the nuget package:
##[error]The nuget command failed with exit code(1) and error(NU1102: Unable to find package Microsoft.NETCore.App with version (>= 3.1.0)
- Found 81 version(s) in MyGet [ Nearest version: 3.0.0-preview8-28405-07 ]
- Found 73 version(s) in NuGet [ Nearest version: 2.2.8 ]
.NET Core 3.1 was released in December 2019 so why is the package not on nuget?
What am I missing?
Update
The CI is Azure Devops Pilelines and the agents are Windows machines that have Visual Studio 2017 installed. .Net core sdk 3.1 is not installed on the agents
Method 1:
Add the following task in your yaml
steps:
- task: UseDotNet#2
displayName: 'Use .Net Core sdk 3.1.x'
inputs:
version: 3.1.x
Method 2:
If using template editor, add Use .Net Core task and provide the version over there
Note: Make sure this should be the first task of the pipeline configured
I have created project in asp.net MVC with 4.5 framework in 2015 VS. I am trying to add Microsoft.Owin.Host.SystemWeb this package from nuget package manager but getting error like
Could not install package 'Microsoft.Owin 4.0.0'. You are trying to
install this package into a project that targets
'.NETFramework,Version=v4.5', but the package does not contain any
assembly references or content files that are compatible with that
framework.
Even if I changed framework still getting error and
Microsoft.Owin.Host.SystemWeb latest Version of this package is 4.0.
f you are installing last versions of SignalR you will not be able as it has some dependencies that require .Net4.5, but you can still install an old version of SignalR which uses .Net4.0, like
1.1.3 Install-Package Microsoft.AspNet.SignalR -Version 1.1.3
This is not the case any more, and the 2.x releases require .NET 4.5.
https://github.com/SignalR/SignalR/issues/1723
I've installed SignalR.Core and it says the following...
Package 'Microsoft.AspNet.SignalR.Core 2.2.2' was restored using
'.NETFramework,Version=v4.6.1' instead of the project target framework
'.NETCoreApp,Version=v2.0'. This package may not be fully compatible
with your project.
Why would a "Core" version of SignalR be incompatible with .net Core?
That's not the Core version of SignalR, that's the core package of the "classic" version.
SignalR was rewritten from scrach for .NET Core. The first alpha version was released on September 2017 as Microsoft.AspNetCore.SignalR. The latest version is 1.0.0 Alpha 2, released on October.
As the blog post explains, this is a significant redesign. You'll have to experiment with the new SignalR to see how the changes affect your application
You should probably track the Github repository and check this video that explains why SignalR was redesigned
I was having the same problem, I solved installing Microsoft.EntityFrameworkCore before Microsoft.AspNetCore.Identity
PM> Install-Package Microsoft.EntityFrameworkCore -Version 2.2.2
PM> Install-Package Microsoft.AspNetCore.Identity -Version 2.2.0
You can omit -Version to get latest stable version of the Package.
I faced below error when I ran below commands;
meteor update --patch
ran command meteor
ERROR
D:\test>meteor update --patch
Changes to your project's package version selections from updating the
release:
accounts-base upgraded from 1.2.17 to 1.3.0
babel-compiler upgraded from 6.18.2 to 6.19.1
boilerplate-generator upgraded from 1.0.11 to 1.1.0
dynamic-import added, version 0.1.0
ecmascript upgraded from 0.7.3 to 0.8.0
ecmascript-runtime upgraded from 0.3.15 to 0.4.1
ecmascript-runtime-client added, version 0.4.1
ecmascript-runtime-server added, version 0.4.1
localstorage upgraded from 1.0.12 to 1.1.0
meteor-base upgraded from 1.0.4 to 1.1.0
minifier-js upgraded from 2.0.0 to 2.1.0
minimongo upgraded from 1.0.23 to 1.2.0
modules upgraded from 0.8.2 to 0.9.0
modules-runtime upgraded from 0.7.10 to 0.8.0
mongo upgraded from 1.1.17 to 1.1.18
promise upgraded from 0.8.8 to 0.8.9
reactive-dict upgraded from 1.1.8 to 1.1.9
standard-minifier-js upgraded from 2.0.0 to 2.1.0
webapp upgraded from 1.3.15 to 1.3.16
test: updated to Meteor 1.4.4.3.
D:\test>meteor
[[[[[ ~\D\test ]]]]]
=> Started proxy.
=> Meteor 1.5 is available. Update this project with 'meteor update'.
=> Started MongoDB.
=> Errors prevented startup:
While selecting package versions:
error: Potentially incompatible change required to top-level
dependency: meteor-base 1.0.4, was 1.1.0.
Constraints on package "meteor-base":
* meteor-base#1.0.4 <- top level
* meteor-base#1.0.4 <- top level
Potentially incompatible change required to top-level dependency:
dynamic-import 0.1.0-beta.20, was 0.1.0.
Constraints on package "dynamic-import":
To allow potentially incompatible changes to top-level dependencies,
you must pass --allow-incompatible-update on the command line.
=> Your application has errors. Waiting for file change.
if you update to meteor 1.5 with meteor update Everything will work as expected with 0 conflict.
Dont touch any files!
Worked for me, first update that actually does not break anything.
I have noticed that the update included package "dynamic-import".
Just taking it out solved the issue. Then run with:
meteor --allow-incompatible-update
Maybe it is just a coincidence I have made this patch just a bit after the new Meteor 1.5 is launched. I wonder if this package should not be in this release.