Thanks for contacting support.
The product teams are working on creating APIs based on .NET core but I am afraid they are not yet available. We do understand the necessary of this requirement but I am afraid the teams have been busy supporting other previously requested high priority requirements and fixing some critical issues. Nevertheless, as shared earlier, we can share some updates by Q1-2018.
Please be patient and spare us little time.
Is there a beta release cycle that users can apply for before RTM?
Once the .NET core is supported, then we would be able to share the Hotfix versions of the Aspose APIs. Normally, we release a new version of each Aspose API in a month, and share a Hotfix version if the full version is taking time to come out. It is a complex task because we need to remove some dependencies to add support of .NET Core. We will let you know once a significant progress has been made in this regard.
@F_Z_14, @lars.olsson, @craigfis, @rsamveda.ramsoft, @MaitreDede, @Shrike, @gwert, @michaelhelfenstein, @sandcastle,
The issues you have found earlier (filed as WORDSNET-13612) have been fixed in this Aspose.Words for .NET 17.12 update and this Aspose.Words for Java 17.12 update.
Please also check the following articles:
@gwert, @Shrike, @michaelhelfenstein, @sandcastle
Thanks for your patience.
We are pleased to inform you that new feature, which request was logged under the ticket ID PDFNET-40993, has been provided in latest version Aspose.Pdf for .NET 17.12. Please download latest version of the API and in case of any further assistance, please feel free to let us know.
What feature?
Also I cant see the mentioned bug number on the release page.
Thanks for contacting support.
We have added support for .NET Standard 2.0 in new release Aspose.Pdf for .NET 17.12. For an overview of Improvements and Changes in the latest version of the API, please check the Release Notes page in our API documentation.
@awais.hafeez @asad.ali - This is great news to see words and pdf now supporting .net standard 2 - when can we expect to see cells and email support?
We have added support for .NET Standard 2.0 in our latest release Aspose.Email for .NET 17.12 that we have just published. For further information, please check the Release Notes section of our documentation.
For Aspose.Cells, please spare us some more time for evaluation. Once, we will have some news for you, we will update you in this topic.
Hi,
Aspose.Total for .NET will be include .NET Core. Or is it new product and i need buy new license?
This is to update you that .NET Core will be part of .NET APIs. There is no need to buy separate license.
Aspose.Pdf doesn’t seem to work with DotnetCore on linux (Docker), I’m getting a a ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length when using pdfDocument.Save(pOutput, SaveFormat.Html);
ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length
string.Substring(int startIndex, int length)
.()
.(FontSource )
.()
.()
.(string , bool , bool )
.()
. ()
. ( , , )
. ( , )
.( , List< > )
.( , List< > )
. ( , List< > )
. ( , , )
.(Document , ref , UnifiedSaveOptions , ref int )
.(Document , string , Stream , HtmlSaveOptions )
Aspose.Pdf.Document.Save(string outputFileName, SaveOptions options)
Kindly send us the complete details of the scenario, including source PDF, code and environment details. We will investigate and share our findings with you.
I would also like to subscribe to be notified when Aspose.Pdf and Aspose.Words are updated for ASP.NET Core 2.0
This is to update you that Aspose.PDF and Aspose.Words supports ASP.NET Core 2.0. Furthermore Aspose.Words started supporting ASP.NET Core 2.0 since version 17.12. However there are a few limitation. Please visit the link below for details.
Asp.net MVC core Controller:
// POST api/values
[HttpPost]
[Route("api/values/pdftest")]
public async Task<ActionResult> PdfTest(IFormFile file)
{
var uploads = Path.Combine(_hostingEnvironment.WebRootPath, "uploads");
if (file.Length > 0)
{
if (!System.IO.Directory.Exists(uploads))
{
System.IO.Directory.CreateDirectory(uploads);
}
var filePath = Path.Combine(uploads, file.FileName);
using (var fileStream = new FileStream(filePath, FileMode.Create))
{
await file.CopyToAsync(fileStream);
}
AsposePdfTester tes = new AsposePdfTester();
tes.ConvertPdfToHtml(filePath,"test.html");
}
return Json(new { result = "" });
}
Class:
using System;
using System.Collections.Generic;
using System.Text;
using Aspose.Pdf;
namespace PdfTester
{
public class AsposePdfTester
{
public AsposePdfTester()
{
Aspose.Pdf.License lic = new License();
lic.SetLicense("Aspose.Total.lic");
}
public void ConvertPdfToHtml(string pfile, string pOutput)
{
var pdfDocument =
new Document(pfile);
// Save the file into HTML format
pdfDocument.Save(pOutput, SaveFormat.Html);
}
}
}
DockerFile:
FROM microsoft/aspnetcore:2.0
ARG source
WORKDIR /app
EXPOSE 80
COPY ${source:-obj/Docker/publish} .
ENTRYPOINT [“dotnet”, “PdfTester.Service.dll”]
I’m using Asp.net MVC Core and Dotnet Core 2.0 and deploying using docker for linux
We are preparing an environment to deploy the MVC application with Docker. We will investigate and share our findings with you soon.
Any news about this?
We have prepared an instance of Windows 10 Enterprise with docker, and facing ‘MobyLinuxVM’ failed to initialize error. We will get back to you soon once it is resolved.
We have logged this problem under the ticket ID PDFNET-44157 in our issue tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates.