Merge pull request #2047 from Syncfusion-Content/hotfix/hotfix-v25.1.35

DOCINFRA-2341_merged_using_automation

Author: SyncfusionBuild

File-Formats-toc.html

@@ -945,6 +945,12 @@
 					<li><a href="/file-formats/pdf-to-image/Converting-PDF-pages-into-Images-in-WPF">WPF</a></li>
 				</ul>
 			</li>
+			<li>
+			    How to
+				<ul>
+					<li><a href="/file-formats/pdf-to-image/How-to/Run-NET80-Linux-application-in-azure-app-service">Run NET8.0 Linux application on Azure app service</a></li>
+				</ul>
+			</li>
 		</ul>
 	</li>
     <li>

File-Formats/PDF-to-image/How-to/Azure_Linux_Net80_Images/Azure_Linux_Step1.png

@@ -0,0 +1,34 @@
+---
+title: Run NET80 Linux application in azure app service| Syncfusion
+description: Learn about the steps to run the .NET80 linux application in Azure app service with the PdfToImageConverter control.
+platform: file-formats
+control: PDF to image
+documentation: UG
+---
+
+# Run .NET80 PdfToImageConverter Linux application in Azure app service 
+
+To run a .NET 8.0 Linux application with PdfToImageConverter on an Azure App Service, you need the libdl.so file to access the pdfium assembly. However, in Azure App Service, the file is named libdl.so.2 instead of libdl.so. Therefore, to ensure compatibility and functionality, you must manually move and rename libdl.so.2 to libdl.so in the Azure App Service environment for the .NET 8.0 applications. This adjustment allows your .NET 8.0 application to function properly with PdfToImage conversion capabilities.
+
+N> While running the .NET 8.0 PdfToImageConverter Linux application on a Azure app service, you will get the `TypeInitializationException: Type initializer for "Syncfusion.PdfToImageConverter.PdfiumNative" threw an exception`.
+
+## Steps to run the .NET80 PdfToImageConverter Linux application in Azure app service
+
+Step 1: Open the SSH command window which will be present under your Azure app service in [Azure portal](https://portal.azure.com/).
+![Open SSH command Window](Azure_Linux_Net80_Images/Azure_Linux_Step1.png)
+
+Step 2: Now, navigate back to the home location and then navigate to the usr/lib/x86_64-linux-gnu location in the SSH.
+![Navigation to the libdl assembly location](Azure_Linux_Net80_Images/Azure_Linux_Step2.png)
+
+Step 3: List the assemblies present in this location using the `ls` command. You can find the libdl.so.2 assembly in that location instead of libdl.so assembly file.
+![Locate the libdl assembly](Azure_Linux_Net80_Images/Azure_Linux_Step3.png)
+
+Step 4: Copy the libdl.so.2 file from this location to the `home\site\wwwroot` folder and rename it to libdl.so using the command `cp libdl.so.2 /home/site/wwwroot/libdl.so`.
+![Copy and rename the libdl assembly](Azure_Linux_Net80_Images/Azure_Linux_Step4.png)
+
+Step 5: Then navigate back to the `home\site\wwwroot` folder and ensure whether the copied assembly present in the desired location.
+![Ensuring the copied assembly](Azure_Linux_Net80_Images/Azure_Linux_Step5.png)
+
+Step 6: Finally, refresh the service page URL and then the application will be work as expected.
+
+N> If still the service is not working properly, stop and start the service again in the Azure portal. The `TypeInitializationException` will no longer be thrown.