Wrong XAML files are shipped with the Net Core themes archive. Instead of Docuemnts.xaml and RichTextBoxUI.xaml the RichTextBox.xaml file should be added. 

Steps to reproduce: 

1. Download Telerik_UI_for_WPF_Source_[Version].zip

2. Modify the Release70 configuration to Debug70 in the following script - Build_WPF70_Xamlless.bat

3. Execute the bat file to reproduce the error:

Telerik_UI_for_WPF_Source_[Version]\Core\Controls\Input\Touch\TouchManagerV3\TouchManager.TouchMode.cs(242,9): error CS1519: Invalid token '{' in class, record, struct, or interface member declaration [D:\temp\tic\Telerik_UI_for_WPF_Source_2023_3_1114\Core\Controls\Controls_NetCore_5cmyf5ge_wpftmp.csproj::TargetFramework=net7.0-windows]

As I workaround I would suggest editing the NetCoreConfigurations.targets with the following property groups: 

<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug70|AnyCPU' ">
    <TargetFrameworks>net7.0-windows</TargetFrameworks>
    <PlatformTarget>AnyCPU</PlatformTarget>
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <OutputPath>bin\$(Configuration)\</OutputPath>
    <DefineConstants>DEBUG;WPF;NETCORE;CODE_ANALYSIS;WPF45;WPF40</DefineConstants>
    <TreatWarningsAsErrors>false</TreatWarningsAsErrors>
    <WarningsAsErrors />
    <SourceAnalysisTreatErrorsAsWarnings>true</SourceAnalysisTreatErrorsAsWarnings>
    <StyleCopEnabled>false</StyleCopEnabled>
    <TargetFrameworkVersionString>70</TargetFrameworkVersionString>
  </PropertyGroup>

  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug70.NoXaml|AnyCPU' ">
    <TargetFrameworks>net7.0-windows</TargetFrameworks>
    <PlatformTarget>AnyCPU</PlatformTarget>
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <OutputPath>bin\$(Configuration)\</OutputPath>
    <DefineConstants>DEBUG;WPF;NETCORE;CODE_ANALYSIS;WPF45;WPF40;NOXAML</DefineConstants>
    <TreatWarningsAsErrors>false</TreatWarningsAsErrors>
    <WarningsAsErrors />
    <SourceAnalysisTreatErrorsAsWarnings>true</SourceAnalysisTreatErrorsAsWarnings>
    <StyleCopEnabled>false</StyleCopEnabled>
    <NoXaml>true</NoXaml>
    <GenerateImplicitStyles>true</GenerateImplicitStyles>
    <TargetFrameworkVersionString>70</TargetFrameworkVersionString>
  </PropertyGroup> 

The file can be found here: Telerik_UI_for_WPF_Source_[Version]\Build\Imports\NetCoreConfigurations.targets.

- collision with classes CallbackBehaviour and ConcurrencyMode, collision with DuplexChannelFactory

- Collision with SecurityPolicyVersion and may others types in System.ServiceModel.Security Namespace | Microsoft Learn

- [Breaking change]: WCF Client 6.0 release will no longer support net standard 2.0 · Issue #33515 · dotnet/docs · GitHub

- - large amount of 40 unnecessary dependencies. These are potential errors in Nuget dependecy resolution.

9,4 MB unnecessary additional files per application.

-Only necessary dependencies should be added.

Telerik UI for WPF demo application can not be launched when there is no internet connection or access to Google Analytics is restricted by DNS. 

In EventViewer you can observe the following error:

Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.Http.HttpRequestException: The requested name is valid, but no data of the requested type was found. (www.google-analytics.com:443)

Hello,

During project implementation a wrong link connection was found.

Precondition:

When we have two models of ContainerNodeViewModelBase OuterModel and InnerModel.

InnerModel has set to true "RadDiagramShapeBase.UseGlidingConnector".

Steps to reproduce:

1. Put InnerModel inside OuterModel.

2. Connect the top middle connector to middle connector of InnerModel

3. When you move InnerModel in upper part of OuterModel the link is connected to bottom of InnerModel instead of to top.

To make reproduce easier i attach video, and i modified your sample application (PasteOnMousePosition) to reproduce this issue.

I attached both things.

Video desc:
1st use case with no gliding connector -- looks ok

2nd use-case movement outside of container and the link looks ok, but the link connection inside looks bad.

Currently this link is just a line, but when it would be an arrow then its looks even worse.

In our app many checkboxes are crop when user scale to 125 %, it happens in win11 but it has been reported in win10.

I found out that this is also happening in the colour theme generator from Telerik with the checkbox in the ribbon (screenshot below).

Is this a known issue or something that we can fix some how? so far we have taken the template for the checkboxes and change the margin of the element "grid" from 1 to 0 to work around it. 

Thanks in advance

Julio

If the total Items count exceed the MaxVisiblePips value,scroll by mousewheel,when scroll to the start or end item,the next scroll item should be the end or start,

the scrollview can not scroll to the selected item. Please see Annexes 1 and 2

When  the MaxVisiblePips value is four,click the right item ,The scroll view cannot be rolled to the center, Please see Annexes 3

ArgumentNullException is thrown in the GetNameCore method of the RadGlyphAutomationPeer class. This happens when the Glyph property of RadGlyph is not set and the automation peer for the corresponding element kicks-in.

To work this around, disable the automation peers.

AutomationManager.AutomationMode = AutomationMode.Disabled;

There seems to be a bug concerning tabs headers of TabControl when used with Office2016 theme.

The color of the header changes from white (active tab) to light blue when a control on this tab is hovered. White background is shown only when mouse hovers only over TabControl Tab panel directly. See gif attached.

The following exception is thrown when changing the theme of an element with the StyleManager runtime:
Cyclic reference found while evaluating the ThemeStyle property on element 'Telerik.Windows.Controls.Gauge.Needle'.

This only occurs in some themes, such as Fluent, Crystal, and Office2016.

Selecting a pinned row or column results in wrongly selected indexes. 

Steps to reproduce:

Case #1: 

1. Pin a row

2. Select the pinned row 

result: a wrong row is selected

Case #2: 

1. Pin one column 

2. Select a cell from the pinned column 

Result: The visual selection is for the first unpinned cell. The selected indexes are wrong too. The Column index is always 0