|
Query |
Details |
|
I don't see "Syncfusion.EJ2.PdfViewer.AspNet.Core.Windows.dll" in the published build folder. Is "Syncfusion.EJ2.PdfViewer.AspNet.Core.Windows" just the nuget package name and it includes "Syncfusion.EJ2.PdfViewer.dll" for Windows i.e. there is no "Syncfusion.EJ2.PdfViewer.AspNet.Core.Windows.dll?" |
Yes the “Syncfusion.EJ2.PdfViewer.AspNet.Core.Windows”is NuGet name and it includes "Syncfusion.EJ2.PdfViewer.dll" |
|
So, is the Windows and Linux-specific code in two versions of Syncfusion.EJ2.PdfViewer.dll? Can I just publish everything on Windows and then swap that one file for the Linux deployment? |
No, we need to use the Syncfusion.EJ2.PdfViewer.AspNet.Core.Linux package in your project then build it in Linux environment and then publish the same |
|
I assumed I could build/publish on Windows and deploy to Linux (as described in #2). Do I need a separate Linux "build server?" |
No, we cannot use the build/ publish on Widows in Linux platform. We need to build the project in Linux environment and then publish the same |
FWIW, for my struggling developer congeners, here's how I solved it in a .NET Core Blazor project:
Downloaded the pdfium files from here: https://blazor.syncfusion.com/documentation/pdfviewer/how-to/unexpected-token. Added a folder "Assets" to the root of my Blazor web project and added this to my .csproj:
Also, since I build with Azure Devops on a Ubuntu linux machine (and deploy to an Azure linux stack), I have this in the .csproj:
Hi Gerard,
I'm having a similar problem with this thread. I would like to support PDF Viewer for Windows as well as Linux. So I added 2 dlls - Syncfusion.Blazor.PdfViewerServer.Windows and Syncfusion.Blazor.PdfViewerServer.Linux.
Unfortunately when running my Blazor solution on my machine (Windows) the viewer doesn't work - I suspect it's because of adding the Linux package.
Unfortunately I can't see your code, so could you re-share your solution?
We cannot use both the windows package and the Linux package at the same.
Kindly install the respective package according to your environment.
Kindly revert to us if you still have any issues after installing the respective package alone.
Kindly find the forum for reference :