At the time I wrote the blog post, we did not yet have separate NuGet packages for the new .NET Standard 2.0 Document Processing libraries, so I needed to use the DLLs that were shipped with UI for Xamarin.
Azure functions (v3) are compiled for .NET Core (see the C# Azure Functions reference). Those assemblies you're currently using are only for .NET Framework projects because it comes from the UI for ASP.NET MVC product (which is for ASP.NET MVC5).
Now that you know the "why", let's move on to the "how" and get you up and running.
You need to instead switch to .NET Standard 2.0 versions. You can get these from a few places:
- NuGet Packages (recommended)
- .NET Core Product Installation folders
- UI for ASP.NET Core - C:\Program Files (x86)\Progress\Telerik UI for ASP.NET Core [version]\dpl
- UI for Xamarin - C:\Program Files (x86)\Progress\Telerik UI for Xamarin [version]\Binaries\Portable
I have updated my demo code on GitHub to use the NuGet server instead, you can use that for a quick reference. Please visit LanceMcCarthy/DocProcessingFunctions.
Updating the Project
Let me take you through each step to fix your current project.
1. Remove Incorrect References
The first thing you'll want to do is delete the all the current .NET Framework DLL assembly references you have for Document Processing.
Tip - You should not even have a visible node for "Assemblies" anymore. Typically, .NET Core projects use NuGet packages instead of assembly references.
Step 2. NuGet Package Manager
Open the NuGet Package Manager, switch to the Telerik NuGet server and filter the packages by "Telerik.Documents"
Advanced Tip - You can also use an offline packages folder instead of the Telerik NuGet server (as long as you copied all the .nupkg files into it).
3. Install the Required Document Processing Libraries packages
Since you're using SpreadProcessing libraries, you can find the required packages in RadSpreadProcessing Getting Started documentation. As this is .NET Core project, you need to use .NET Standard version, which is listed under the .NET STANDARD-COMPATIBLE section.
Be sure not to miss any additional functionality. Because you're also using the PDF export, you'll need to look down a little further under the next
Here's a screenshot to help guide you:
The NuGet package name is the same as the assembly name, but without the .dll file extension. The end result should look like this:
Important Note: I have .Trial in the name because this project is for GitHub public repo. You would be using the ones without the .Trial suffix instead.
If I was able to answer your question, you can let me know by using the thread's "Answered" button so that other folks can more easily find it for their
If you have any further trouble or questions about the usage of the libraries in NET Core, please open a Support Ticket here (you have a priority support license with 24hr support) so that Martin and his team can assist further.
Thank you for choosing Telerik for your project, have a great day and stay safe!
Lance | Team Lead - US DevTools Support
Progress is here for your business, like always. Read more
about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.