.net-standard-1.6

This is one of the weird issue I have seen and here are the steps to reproduce 1> Create new Web API project in VS 2017 with Target Framework 4.6.2 Create new ASP.NET Web Application -> Select Empty -> Check Web API -> Click OK 2> Add Controller that returns a Stream public class ReportController : ApiController { [HttpGet] public HttpResponseMessage Download() { var filePath = "C:\\Report.xlsx"; var fs = new FileStream(filePath, FileMode.Open, FileAccess.Read); var result = new HttpResponseMessage(HttpStatusCode.OK) { Content = new StreamContent(fs) }; result.Content.Headers.ContentType = new

I`m trying to publish a self-contained app, made in .net-core, following the steps in https://docs.microsoft.com/en-us/dotnet/articles/core/deploying/index . The repository with the code is in https://github.com/fontanaricardo/httpecho I execute the commands: $dotnet build -r debian.8-x64 $dotnet publish -c Release -r debian.8-x64 $docker build -t httpecho . Starting the container: $ docker run -p 5000:5000 httpecho Error: assembly specified in the dependencies manifest was not found -- package: 'Microsoft.AspNetCore.Hosting.Abstracti ons', version: '1.1.0', path: 'lib/netstandard1.3/Microsoft

I'm porting a .NET 4.6.1 console app to .NET Core. I have NETStandard.Library 1.6 installed, and it's not letting me pass a file path string into a StreamReader constructor. Viewing the definition confirms that it's not available: Where's it gone? This is correct. .Net Core 1.0/.Net Standard 1.x refactored the base libraries, so that basic stream types like StreamReader are in the System.IO package and FileStream is in the System.IO.FileSystem package . Since the constructor you're looking for would require StreamReader to depend on FileStream , it was removed. Note that a large part of this

I've been using iTextSharp with regular dotnet applications for a while now. We're interested in using it with dotnet core. But it seems that the library is still not supported on the new dotnet core platform: Package iTextSharp 5.5.10 is not compatible with netstandard1.6 Do you plan to support dotnet core in a future release? blagae For the record: I am an employee at iText Software. Currently, .NET Core and the related UWP standard are not supported by any iText projects. We have done investigations into both these new technologies and have found that there are significant issues with