Hello everyone,

Here are the highlights of the new online resources we published this week from 10 Nov 2025 to 17 Nov 2025:

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/find
Summary: Learn how to use RadPdfViewer’s Find feature in WPF to search text in PDF documents, navigate next/previous matches, and highlight results. The article explains the built-in Find UI, commands and API for initiating searches, configuring options like match case and whole word, and handling events to react to search state changes, with code examples for integrating the search UI and driving it from code-behind or MVVM.

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/save-as
Summary: Use RadPdfViewer for WPF’s Save As to export the currently loaded PDF to a new file, preserving edits such as annotations and form fields. Invoke it from the UI or programmatically with RadPdfViewerCommands.SaveAs targeting your RadPdfViewer instance. The command is available regardless of whether the document was opened from a file path or a stream.

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/printing
Summary: Learn how to print PDFs from RadPdfViewer in a WPF application using the built-in Print command or programmatically from code-behind. The article shows how to invoke the WPF PrintDialog and configure print settings (for example, scaling and other output options) to control the printed result.

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/bookmarks
Summary: Learn how to enable and use the Bookmarks pane in RadPdfViewer for WPF to display a PDF’s hierarchical outline and navigate to bookmark destinations. The article shows how to toggle the pane in the built-in UI and how to access and traverse bookmarks programmatically so you can implement custom navigation or integrate bookmarks into your own controls.

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/scrolling
Summary: This article explains how to configure and control scrolling in RadPdfViewer for WPF, including vertical/horizontal scrollbars, continuous document scrolling, and how zoom and fit modes affect the viewport. It details user interactions (mouse wheel, touch, keyboard) and shows how to scroll programmatically to a page or offset and handle scroll changes through the viewer’s API.

Article: https://www.telerik.com/products/wpf/documentation/ai-assistant/mcp-server-as-a-nuget
Summary: This guide shows you how to install and self-host an MCP (Model Context Protocol) server via a NuGet package in a WPF app and connect it to RadAIAssistant. You will configure the server and register tools/resources so an LLM can invoke application capabilities through MCP.

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/ai-summarization
Summary: Learn how to enable AI summarization in the WPF RadPdfViewer so you can summarize the entire PDF or the current selection via built-in summarize commands. You configure an LLM provider, connect it to the viewer, invoke the commands, and optionally customize prompt text and output (length/format), with guidance on async execution, context/token limits, and error handling.

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/digital-signature
Summary: This article shows how to view and validate PDF digital signatures in RadPdfViewer for WPF, including displaying signature widgets, inspecting signer/certificate details, and reporting validity (trusted, expired, revoked, or document modified). It explains how to configure validation by providing trusted root certificates and enabling revocation checks (OCSP/CRL), handle user interactions with signatures, and notes that creating signature fields or signing PDFs is done with PdfProcessing.

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/interactive-forms
Summary: RadPdfViewer for WPF supports interactive PDF AcroForm forms, allowing you to display and fill fields such as text boxes, check boxes, radio buttons, list/combo boxes, and push buttons directly in the viewer. You can read and write field values, control focus and keyboard navigation, and handle standard form actions (submit/reset) through the API; XFA forms are not supported.

Article: https://www.telerik.com/products/wpf/documentation/controls/radpdfviewer/export-fixedpage-to-image
Summary: Learn how to export a WPF RadPdfViewer page (FixedPage) to an image (PNG/JPEG) by retrieving the FixedPage for a given PDF page, converting it to a bitmap, and saving it to a file or stream with control over size and DPI/scale. The article explains handling page virtualization and layout so you can export pages that aren’t currently visible and generate consistent thumbnails and previews from C# code.

Feel free to check them out and share your thoughts!

The Telerik Team

---------------------------------------------------------------------------------------------------------------------------------------------------------

Hello everyone,

Here are the highlights of the new online resources we published this week from 29 Oct 2025 to 05 Nov 2025:

Article: https://www.telerik.com/products/wpf/documentation/netcore/overview
Summary: This article shows you how to use Telerik UI for WPF in .NET Core/.NET SDK-style WPF projects, outlining supported target frameworks and the Windows-only scope. You add the Telerik packages from your private NuGet feed, reference the controls and XAML namespaces, merge theme resource dictionaries, and account for Visual Studio design-time support and differences from .NET Framework.

Article: https://www.telerik.com/products/wpf/documentation/security/overview
Summary: This article outlines the Telerik UI for WPF security model: assemblies are strong-named and Authenticode-signed, and the controls are designed for full-trust desktop applications rather than partial-trust environments (e.g., XBAP or partial-trust ClickOnce). It provides guidance to reduce risk—avoid loading untrusted XAML or documents, gate clipboard/drag-and-drop/printing/file access, keep dependencies updated, and align your app with .NET/WPF security practices.

Feel free to check them out and share your thoughts!

The Telerik Team

As of 2024 Q4 (November), we will deprecate the .NET 7 distribution. This decision is rooted in our dedication to align with Microsoft’s recommended framework versions so that our products leverage the latest advancements in technology, security, and performance.  

We are aligning our product with Microsoft’s lowest-supported framework versions for .NET Framework and .NET, respectively. Please refer to the following blog post: Product Update for Enhanced Performance and Security

For more information about how to upgrade your project when a new version of the Telerik UI for WPF suite is released, you can check here: Project Migration to .NET 4.6.2 and .NET 6

As of 2024 Q2, we will deprecate .NET Framework 4.0, .NET Framework 4.5, and .NET Core 3.1 distributions. This decision is rooted in our dedication to align with Microsoft’s recommended framework versions so that our products leverage the latest advancements in technology, security, and performance.

We are aligning our product with Microsoft’s lowest-supported framework versions for .NET Framework and .NET, respectively. Please refer to the following blog post:

Product Update for Enhanced Performance and Security (telerik.com)

For more information about how to upgrade your project's .NET Framework version, you can check the following MSDN article:

Migration Guide to .NET Framework 4.8, 4.7, and 4.6.2 - .NET Framework | Microsoft Learn

We are using WPF with Prism, MEF, and Telerik controls (PdfViewer and GridView, version 2017.2.503.45). Our application loads multiple tab views dynamically using the MVVM pattern. Each view contains multiple Telerik controls, and their data is bound from the ViewModel.

The issue we are facing is that when a tab is closed, the Telerik controls still hold references to the associated ViewModel, preventing the memory from being released.

We have tried the following approaches while closing the tab:

RadPdfViewer.DataContext = null;

RadPdfViewer = null;

RadGridView.DataContext = null;

RadGridView = null;

We also tried disposing of the Telerik controls, but the memory is still retained by them.

We have also defined the PdfViewer in XAML, but no PDF file was ever loaded into it from the UI. However, even in this case, the XAML view is not being disposed when the tab is closed, and the PdfViewer still holds a reference to the view.

Could you please help us identify how to properly release memory and ensure the controls? 

Can RadGlyph work with Font Awesome's Duotone font? For example, we want to render: https://fontawesome.com/icons/house?f=duotone&s=solid

I've tried various things, including:

                <Grid>
                    <!-- Secondary (back) layer -->
                    <telerik:RadGlyph
                        Font="fads"
                        FontSize="40"
                        Glyph="&#x10F015;"
                        Foreground="Red" />
                    <!-- Primary (front) layer -->
                    <telerik:RadGlyph
                        Font="fads"
                        FontSize="40"
                        Glyph="&#xF015;"
                        Foreground="Blue" />
                </Grid>

This just renders an all blue house.

Reversing the elements:

            <telerik:RadTabItem.Content>
                <Grid>
                    <!-- Primary (front) layer -->
                    <telerik:RadGlyph
                        Font="fads"
                        FontSize="40"
                        Glyph="&#xF015;"
                        Foreground="Blue" />
                    <!-- Secondary (back) layer -->
                    <telerik:RadGlyph
                        Font="fads"
                        FontSize="40"
                        Glyph="&#x10F015;"
                        Foreground="Red" />
                </Grid>

I'm using the same technique I use to register regular Font Awesome fonts and have verified the codepoints exist:

        var solidDuotoneFontFilePath = Path.Combine(directory, "Resources/Fonts", "Font Awesome 7 Duotone-Solid-900.otf");
        var solidDuotoneFontUri = new Uri(solidDuotoneFontFilePath, UriKind.Absolute);
        var solidDuotoneFontFamily = new FontFamily(solidDuotoneFontUri, "./#Font Awesome 7 Duotone Solid");
        RadGlyph.RegisterFont(solidDuotoneFontFamily, "fads");

        bool HasChar(FontFamily fam, int codePoint)
        {
            var tf = new Typeface(fam, FontStyles.Normal, FontWeights.Normal, FontStretches.Normal);
            if (!tf.TryGetGlyphTypeface(out var gtf)) return false;
            return gtf.CharacterToGlyphMap.ContainsKey(codePoint);
        }

        Debug.WriteLine($"Primary F015 present: {HasChar(solidDuotoneFontFamily, 0xF015)}");
        Debug.WriteLine($"Secondary 10F015 present: {HasChar(solidDuotoneFontFamily, 0x10F015)}");

I am using the Material Theme, here's my app.xaml code

<Application x:Class="Desktop_Application.App"
             xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
    <Application.Resources>
        
        <ResourceDictionary>
            <!-- Global default font size -->
            <Style TargetType="{x:Type Control}">
                <Setter Property="FontSize" Value="8"/>
            </Style>
            
            <ResourceDictionary.MergedDictionaries>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/System.Windows.xaml"/>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/Telerik.Windows.Controls.Chart.xaml"/>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/Telerik.Windows.Controls.Data.xaml"/>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/Telerik.Windows.Controls.FixedDocumentViewers.xaml"/>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/Telerik.Windows.Controls.GridView.xaml"/>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/Telerik.Windows.Controls.ImageEditor.xaml"/>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/Telerik.Windows.Controls.Input.xaml"/>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/Telerik.Windows.Controls.Navigation.xaml"/>
                <ResourceDictionary Source="/Telerik.Windows.Themes.Material;component/Themes/Telerik.Windows.Controls.xaml"/>
            </ResourceDictionary.MergedDictionaries>
        </ResourceDictionary>
    </Application.Resources>
</Application>

I'm using central package management, where my Directory.Build.props has folliwing entries:

<ItemGroup>
    <PackageVersion Include="Telerik.UI.for.Wpf.NetCore.Xaml" Version="2024.1.423" />
    <PackageVersion Include="Telerik.Windows.Controls.Data.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Controls.DataVisualization.for.Wpf.Xaml" Version="2024.3.924" />
    <PackageVersion Include="Telerik.Windows.Controls.Diagrams.Extensions.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Controls.Diagrams.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Controls.Diagrams.Ribbon.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Controls.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Controls.GridView.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Controls.Input.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Controls.Navigation.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Controls.RibbonView.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Data.for.Wpf.Xaml" Version="2025.2.707" />
    <PackageVersion Include="Telerik.Windows.Diagrams.Core.for.Wpf.Xaml" Version="2025.2.707" />
</ItemGroup>

As you can maybe see, 

Telerik.UI.for.Wpf.NetCore.Xaml has 2024.1.423
Telerik.Windows.Controls.DataVisualization.for.Wpf has 2024.3.924

when using the manage nuget packages dialog from within visual studio it does not report that any updates are necessary, but the build tells me that (of course) there is a version mismatch,

The dialog even tells me that there is a newer version:

What could be the problem that it doesn't get updated or is not found to require an update?