5.0 SDK requires an explicit reference to System.IO.Pipelines for a 3.1 classlibrary targeted ASP.NET Core
See original GitHub issueI’m getting errors like this when building with the .NET 5.0.100-rc.1.20452.10 SDK:
/Users/ryan/github.com/dapr/dotnet-sdk/src/Dapr.AspNetCore/DaprEndpointRouteBuilderExtensions.cs(47,72): error
CS0012: The type 'PipeWriter' is defined in an assembly that is not referenced. You must add a reference to assembly
'System.IO.Pipelines, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. [/Users/ryan/github.com
/dapr/dotnet-sdk/src/Dapr.AspNetCore/Dapr.AspNetCore.csproj]
when building a project that:
- targets
netcoreapp3.1
- is a class library
- references
Microsoft.AspNetCore.App
- uses
PipeWriter
in code - does not explicitly reference the
System.IO.Pipelines
package
Example project: https://github.com/dapr/dotnet-sdk/blob/master/src/Dapr.AspNetCore/Dapr.AspNetCore.csproj
This is regression from the 3.1.301 SDK - which builds these projects successfully on the CI: https://github.com/dapr/dotnet-sdk/runs/1221898037?check_suite_focus=true
I can work around the problem by adding an explicit reference to the System.IO.Pipelines
package (and I will do) - but it seems like this old bug came back.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Build error: You must add a reference to System.Runtime
I'm preparing a brand new ASP.NET MVC 5.1 solution. I'm adding in a bunch of NuGet packages and setting it up with Zurb...
Read more >Migrate from ASP.NET Core 3.1 to 5.0
In this article. Prerequisites; Update .NET Core SDK version in global.json; Update the target framework; Delete bin and obj folders ...
Read more >Migrate from ASP.NET Core 2.2 to 3.0
Sdk.Web SDK implicitly reference the Microsoft.AspNetCore.App framework. No additional references are required for these projects: XML
Read more >Could not load file or assembly after 4.2.0.7 update
Reference assemblies should not be loaded for execution. ... NET Core 3.1, and we are getting System.IO.FileNotFoundException.
Read more >System.IO.Pipelines 7.0.0
Single producer single consumer byte buffer management. Commonly Used Types: System.IO.Pipelines.Pipe System.IO.Pipelines.PipeWriter System.IO.Pipelines.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@wli3 we should also ensure this is covered in tactics so folks are both aware and remember to do this as I don’t want to have to remember to remind people.
Closing as the change to the installer repo has been merged.