-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Core March 16, 2020 Update - 3.1.200 SDK #4404
Comments
Trying to run
I pinned my config back to mcr.microsoft.com/dotnet/core/sdk:3.1.102 as a workaround. |
@jrabbitb I removed all the specflow packages, and reinstalled the lastest:
similar to the accepted answer here: https://stackoverflow.com/questions/39316353/techtalk-specflow-error-could-not-load-assembly-file-or-assembly |
Seeing this same issue, but not locally (windows) only in our CI build system (Gitlab - Linux runners) |
The SpecFlow issue doesn't seem related to Docker but rather to the underlying product. I see a new issue had been created to track this at SpecFlowOSS/SpecFlow#1912. |
Upgrading from .NET Core SDK 3.1.101 to 3.1.200, one of our ASP .NET Core projects now fails to build with the following:
The line of code where the error comes from: var bodyReader = this.Request.BodyReader; The csproj is straighforward: <Project Sdk="Microsoft.NET.Sdk.Web">
<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<OutputType>Exe</OutputType>
<RootNamespace>SampleServer</RootNamespace>
<Platform Condition=" '$(Platform)' == '' ">x64</Platform>
<Platforms>x64</Platforms>
</PropertyGroup>
</Project> Adding Nuget package This may be related to dotnet/aspnetcore#19548, which was closed as a dupe of dotnet/aspnetcore#19133. |
Similar to @davidni, after the upgrade from .NET SDK Core 3.1.101 to 3.1.200, project fails to build with the error:
|
Similar to the guys above. One of my projects which uses msbumb package (https://github.com/BalassaMarton/MSBump) fails to build with 3.1.200:
It only fails when using command line tools. It works perfectly when building from Visual Studio 2019. Setting this as environment variable fix the issue as a workaround: |
@gp2-gp2 I'll add MSBump to the list of failing tasks: dotnet/msbuild#5202 |
@gp2-gp2 Must I set this environment variable in project or for Operation System? |
Hi @dborovsky at Operation System level, at least that's what works for me both in Windows and Ubuntu. |
having similar issue with .net 3.1.300 (windows) |
@smartpcr with what NuGet package or build task? |
I am also experiencing the same with MSBump when targeting a docker-compose project.
The project builds fine when i unload docker-compose from the project and re-build. |
If anyone is interested, there is an updated and maintained project forked from msbump. Everything works off the bat, even docker |
Closing in favor of #2555 |
Release Notes
Please report any issues you find with 3.1.200, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:
Status of availability of 3.1.200 SDK on Linux feeds:
The text was updated successfully, but these errors were encountered: