new KB - Resolving Ambiguous references

Author: dessyordanova

knowledge-base/dpl-resolve-ambiguous-references.md

@@ -4,7 +4,7 @@ description: This article describes how to resolve ambiguous references due to c
 type: how-to
 page_title: How to Resolve Ambiguous References
 slug: dpl-resolve
-tags: radspreadprocessing, document processing, wpf, ambiguous reference, extern alias
+tags: spreadprocessing, document, processing, wpf, ambiguous, reference, extern, alias
 res_type: kb
 ticketid: 1684241
 ---
@@ -17,16 +17,23 @@ ticketid: 1684241
 
 ## Description
 
-When developing a WPF application that utilizes RadSpreadProcessing for Document Processing to set a font in a spreadsheet, and the solution includes a cross-platform project referencing `Telerik.Documents.Core`, an ambiguous reference error may occur. The issue arises due to identical namespaces in both assemblies when both platform-specific projects and cross-platform projects are part of the solution. This knowledge base article also answers the following questions:
-- How to resolve ambiguous reference errors in a WPF project using RadSpreadProcessing?
-- How to use RadSpreadProcessing in a WPF application with cross-platform project references?
-- How to set a spreadsheet font in WPF using RadSpreadProcessing without ambiguous references?
+When developing a WPF application that utilizes [RadSpreadProcessing]({%slug radspreadprocessing-overview%}) to set a font in a spreadsheet, and the solution includes a cross-platform project referencing `Telerik.Documents.Core`, an ambiguous reference error may occur. 
+
+![Ambiguous Error](images/ambiguous_error.png) 
+
+The issue arises due to identical namespaces in both assemblies when both platform-specific projects and cross-platform projects are part of the solution.
 
 ## Solution
 
-To resolve the ambiguous reference error in a WPF application using RadSpreadProcessing alongside a cross-platform project, use the `extern alias` directive. This approach allows differentiating between assemblies that have the same namespace but are intended for different platforms. Follow the steps below to apply this solution:
+The Telerik Document Processing libraries are available in .NET Framework, .NET 8/.NET 9 (or newer) for Windows and .NET Standard compatible versions. All versions are available as NuGet packages. The assemblies/packages for .NET Standard do not contain the word *Windows* in their name. Learn [What Versions of Document Processing Libraries are Distributed with the Telerik Products]({%slug distribute-telerik-document-processing-libraries-net-versions%}).
+
+In a WPF project, you need to use the assemblies containing the word *Windows* and avoid mixing .NET Framework and .NET Standard compatible versions.
+
+However, to resolve the ambiguous reference error in a WPF application using RadSpreadProcessing alongside a cross-platform project, use the [extern alias](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/extern-alias) directive. This approach allows differentiating between assemblies that have the same namespace but are intended for different platforms. Follow the steps below to apply this solution:
+
+1. **Assign an alias to the conflicting assembly in the WPF project**. Right-click on the referenced assembly in the Solution Explorer and select `Properties`. In the `Aliases` field, enter a unique alias (e.g., `NetFramework`).
 
-1. **Assign an alias to the conflicting assembly in the WPF project**. Right-click on the referenced assembly (`Telerik.Documents.Core` in the cross-platform project) in the Solution Explorer and select `Properties`. In the `Aliases` field, enter a unique alias (e.g., `NetFramework`).
+![NET Framework Aliases](images/framework_aliases.png)  
 
 2. **Use the `extern alias` directive in your WPF project code**. At the top of your C# file where you are facing the ambiguous reference, declare the alias defined in step 1. This explicitly specifies which assembly to use for the conflicting types.
 
@@ -55,7 +62,6 @@ By following these steps, you can successfully resolve the ambiguous reference e
 
 ## See Also
 
-- [Telerik Document Processing Introduction](https://docs.telerik.com/devtools/document-processing/introduction)
-- [What Versions of Document Processing Libraries are Distributed with the Telerik Products](https://docs.telerik.com/devtools/document-processing/knowledge-base/distribute-telerik-document-processing-libraries-net-versions)
-- [Resolve Compile-Time Error Between RadPdfProcessing and Telerik Reporting](https://docs.telerik.com/devtools/document-processing/knowledge-base/resolve-compile-time-error-radpdfprocessing-telerik-reporting)
+- [What Versions of Document Processing Libraries are Distributed with the Telerik Products]({%slug distribute-telerik-document-processing-libraries-net-versions%})
+- [Resolve Compile-Time Error Between RadPdfProcessing and Telerik Reporting]({%slug resolve-compile-time-error-radpdfprocessing-telerik-reporting%})
 - [C# Extern Alias - Microsoft Documentation](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/extern-alias)