When trying to install one of the following nuget packages an error occurs:
The same issue manifests with the NoXaml version of the same packages.
The error message is:
Severity Code Description Project File Line Suppression State Details Error Failed to add reference. The package 'Telerik.Windows.Controls.EntityFramework60.for.Wpf.Xaml' tried to add a framework reference to 'EntityFramework' which was not found in the GAC. This is possibly a bug in the package. Please contact the package owners for assistance. Reference unavailable.
A XamlParseException is raised when the theme's resource dictionaries are not merged in App.xaml. The missing resource is the RepeatButtonStyle resource.
To work this around, merge the resource dictionaries for the theme in the Resources collection of the App.xaml file.
After upgrading to .net 9 I get the following error when starting the published program (running it in RIDER in debug-mode doesn't create the issue).
System.TypeInitializationException: The type initializer for 'Telerik.Windows.Input.Touch.TouchManager' threw an exception.
---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Windows.Forms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Das System kann die angegebene Datei nicht finden.
the mentioned assembly System.Windows.Forms is not used by me at all.
Hi,
it would be convenient to add an extra small font size to te existing enumerations. For instance in Windows 11 theme, could it be possible to add a XS size:
Windows11Palette.Palette.FontSizeXS = 10;
Windows11Palette.Palette.FontSizeS = 12;
Windows11Palette.Palette.FontSize = 14;
Windows11Palette.Palette.FontSizeM = 18;
Windows11Palette.Palette.FontSizeL = 20;
Windows11Palette.Palette.FontSizeXL = 28;
Having a range in the bigger font sizes is very useful. It owuld be equally helpful to have a range on the smaller font.
Thank you for considering it :)
Hello,
HtmlDataProvider will throw an exception on export or when used by a RadRichTextBox, when using a html containing the length value "NaN", which doesn't seem to be a standard approved value, but nevetheless it is a special case because other invaild values are simply ignored while this one triggers two exceptions - one of which is hard to catch and crashes the whole application.
Code to reproduce: Console App / .Net Framework 4.8 / Package Telerik.Windows.Documents.FormatProviders.Html.for.Wpf 2022.3.912
using System;
using Telerik.Windows.Documents.FormatProviders.Html;
using Telerik.Windows.Documents.Model;
namespaceHtmlProviderCrash
{
internalclassProgram
{
static void Main(string[] args)
{
var htmlContent = "<img src=\"https://static.cleverpush.com/notification/icon/92fYF7FtKbthsezwS.png?element=Le7adDwC\" " +
"alt=\"\" style=\"display: inline-table;max-width: 100%;width: 300px;\" width=\"300\" height=\"NaN\" class=\"cp-element-image light-img\">";
HtmlFormatProvider htmlProvider = new HtmlFormatProvider();
RadDocument document = htmlProvider.Import(htmlContent);
try
{
var export = htmlProvider.Export(document);
}
catch (Exception ex)
{
var ka = ex.ToString();
}
while (Console.ReadKey().KeyChar != 'x') { }
}
}
}
Message "MeasureOverride returned NaN: Telerik.Windows.Documents.Layout.ImageLayoutBox" string at Telerik.Windows.Documents.Layout.LayoutElement.Measure(SizeF availableSize) at Telerik.Windows.Documents.Layout.ParagraphLayoutBox.MeasureCurrentGroupSize(ParagraphLayoutBoxMeasureContext context, SizeF measureSize, Func`1 GetCurrentXDefaultValue, LinkedList`1 currentGroupInlines) at Telerik.Windows.Documents.Layout.ParagraphLayoutBox.MeasureOverride(SizeF availableSize) at Telerik.Windows.Documents.Layout.LayoutElement.MeasureCore(SizeF availableSize) at Telerik.Windows.Documents.Layout.LayoutElement.Measure(SizeF availableSize) at Telerik.Windows.Documents.Layout.SectionLayoutBox.MeasureOverrideInternal(SizeF availableSize) at Telerik.Windows.Documents.Layout.SectionLayoutBox.MeasureOverride(SizeF availableSize) at Telerik.Windows.Documents.Layout.LayoutElement.MeasureCore(SizeF availableSize) at Telerik.Windows.Documents.Layout.LayoutElement.Measure(SizeF availableSize) at Telerik.Windows.Documents.Layout.DocumentLayoutBox.MeasureOverrideInternal(SizeF availableSize) at Telerik.Windows.Documents.Layout.DocumentLayoutBox.MeasureOverride(SizeF availableSize) at Telerik.Windows.Documents.Layout.LayoutElement.MeasureCore(SizeF availableSize) at Telerik.Windows.Documents.Layout.LayoutElement.Measure(SizeF availableSize) at Telerik.Windows.Documents.Model.RadDocument.Measure(SizeF measureSize) at Telerik.Windows.Documents.Model.RadDocument.MeasureAndArrangeInDefaultSize() at Telerik.Windows.Documents.Model.RadDocument.EnsureDocumentMeasuredAndArranged() at Telerik.Windows.Documents.FormatProviders.Html.Export.HtmlDocumentExporter.Export(RadDocument document, Stream output) at Telerik.Windows.Documents.FormatProviders.Html.HtmlFormatProvider.Export(RadDocument document, Stream output) at Telerik.Windows.Documents.FormatProviders.Html.HtmlFormatProvider.Export(RadDocument document) at HtmlProviderCrash.Program.Main(String[] args)
Message "The image data generated an overflow during processing"
at System.Windows.Media.Imaging.TransformedBitmap.FinalizeCreation() in System.Windows.Media.Imaging\TransformedBitmap.cs:line 216
at System.Windows.Media.Imaging.TransformedBitmap.EndInit() in System.Windows.Media.Imaging\TransformedBitmap.cs:line 112
at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation() in System.Windows.Media.Imaging\BitmapImage.cs:line 505
at System.Windows.Media.Imaging.BitmapImage.EndInit() in System.Windows.Media.Imaging\BitmapImage.cs:line 319
at Telerik.Windows.Documents.Model.ImageDocumentElementHelper.CreateImageSourceCore(BitmapCreateOptions createOptions, Byte[] bytes, Size renderingSize, String& extension, Byte[]& resultBytes)
at Telerik.Windows.Documents.Model.ImageDocumentElementHelper.CreateImageSource(Byte[] bytes, Size imageSize, Size scaleFactor, String& extension, Byte[]& resultBytes)
at Telerik.Windows.Documents.Model.ImageDocumentElementHelper.InitializeRawImageData(IImageDocumentElement imageElement, Byte[] bytes, Size scaleFactor, String& extension)
at Telerik.Windows.Documents.Model.ImageDocumentElementHelper.InitInternal(IImageDocumentElement imageElement, Byte[] bytes, Size size, String extension, Boolean isUserInitiated)
at Telerik.Windows.Documents.Model.ImageInline.InitImageElementFromUriStream(Stream stream)
at Telerik.Windows.Documents.Model.ImageInline.<SetStreamFromUriSource>b__0(Object s, StreamReadyEventArgs a)
at Telerik.Windows.Documents.Utils.ResourceStreamLocator.OnStreamReady()
at Telerik.Windows.Documents.Utils.ResourceStreamLocator.<GetStreamAsync>b__0(Object sender, OpenReadCompletedEventArgs e)
at System.Net.WebClient.OnOpenReadCompleted(OpenReadCompletedEventArgs e)
at System.Net.WebClient.OpenReadOperationCompleted(Object arg)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Hello together,
I am experiencing a bug with the following use case:
When upgrading Telerik.Documents.Fixed from version 2024.3.806 to version 2024.4.1106 the exported PDF file is missing different parts of the originally imported PDF file or even results in a complete "messy" file. Input and output files are view with Adobe Acrobat, Google Chrome, Edge...all showing the same result.
Even omitting step 2 (i.e. I only import and directly export the PDF file) results in the same bug after.
I do not use any special import or export setting to reproduce the error. But even with applying different import/export settings I could not change the buggy outcome.
var bytes = File.ReadAllBytes(@"C:\temp\in.pdf");
var formatProvider = new PdfFormatProvider();
var document = formatProvider.Import(bytes, TimeSpan.FromSeconds(20));
var outBytes = formatProvider.Export(document, TimeSpan.FromSeconds(20));
File.WriteAllBytes(@"C:\temp\out.pdf", outBytes);
See the attached file for example, import it and export it (via code snippet above).
With version 2024.3.806 everything works fine - and as I am not seeing any relevant breaking changes or other release information regarding this issue, I am a little bit lost with what I could do to solve the issue..
Thanks for your support!
A compilation error occurs in a class library project which doesn't use any Telerik code, but it is referenced in another project which installs the Telerik.Licensing NuGet package. The error reproduces only if the class library project contains .xaml files.
The error message from the class library project is the following:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.WinFx.targets(268,9): error MC1000: Unknown build error, 'Cannot resolve dependency to assembly 'Telerik.Licensing.Runtime, Version=1.4.6.0, Culture=neutral, PublicKeyToken=keyhere' because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded on demand through the ReflectionOnlyAssemblyResolve event.'
To workaround this, you can add assembly references to the Telerik dlls in the main project (including Telerik.Licensing.Runtime), instead of using NuGet packages.
Alternatively, you can install the Telerik.Licensing NuGet package also in the class library.
<ItemGroup>
<PackageReference Include="Telerik.Licensing" Version="1.4.*" />
</ItemGroup>
Note that with this approach you will see a message in the output that no license is installed, even if you have one. However, for now (versions from 1.4.6 to 1.4.12, which is the latest at the moment of writting this post), the error won't apply any compile or runtime restrictions on the UI or the functionality.
The build performance with new license validation (2025) is very poor. 2025 version takes about 5 sec. extra time to build. For small projects it takes 10x longer.
Test environment:
Build times depending on the Version of Telerik Nuget:
<PackageReference Include="Telerik.Windows.Controls.Navigation.for.Wpf" Version="2025.1.211" />
11:25:47:071 Build started at 11:25...
11:25:47:189 1>------ Build started: Project: TelerikBuildTest, Configuration: Debug Any CPU ------
11:25:51:748 1>[Telerik and Kendo UI Licensing]
11:25:51:748 1> Telerik and Kendo UI License Key found at: C:\Users\...\AppData\Roaming\Telerik\telerik-license.txt (UserDirectory)
11:25:51:748 1> License issued at 2025-03-16 to e**********@....
11:25:51:748 1>[Telerik and Kendo UI Licensing]
11:25:51:748 1> Valid Telerik UI for WPF license found.
11:25:52:743 1>[Telerik and Kendo UI Licensing]
11:25:52:743 1> Telerik and Kendo UI License Key found at: C:\Users\...\AppData\Roaming\Telerik\telerik-license.txt (UserDirectory)
11:25:52:743 1> License issued at 2025-03-16 to e**********@...
11:25:52:743 1>[Telerik and Kendo UI Licensing]
11:25:52:743 1> Valid Telerik UI for WPF license found.
11:25:52:815 1>TelerikBuildTest -> C:\Users\....\source\repos\TelerikBuildTest\TelerikBuildTest\bin\Debug\net8.0-windows\TelerikBuildTest.dll
11:25:52:828 ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
11:25:52:828 ========== Build completed at 11:25 and took 05,892 seconds ==========
<PackageReference Include="Telerik.Windows.Controls.Navigation.for.Wpf" Version="2024.4.1213" />
11:26:33:405 Build started at 11:26...
11:26:33:581 1>------ Build started: Project: TelerikBuildTest, Configuration: Debug Any CPU ------
11:26:33:953 1>TelerikBuildTest -> C:\Users\...\source\repos\TelerikBuildTest\TelerikBuildTest\bin\Debug\net8.0-windows\TelerikBuildTest.dll
11:26:33:960 ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
11:26:33:960 ========== Build completed at 11:26 and took 00,633 seconds ==========