Skip to content

Updated the UG Content for SP Release #1991

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: development
Choose a base branch
from
Open

Updated the UG Content for SP Release #1991

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added wpf/Guidetorunthesamples_images/TargetFrameworks-wpf.jpg
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
35 changes: 8 additions & 27 deletions wpf/Themes/Theme-Studio.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -274,40 +274,21 @@ Provide the theme name, in which the theme should be exported, and select the re

![Add Theme as Project for Theme Export](ThemeStudio_images/ThemeStudio-Themes-Folder.png)

N> When running the exported project in .NET 8.0 or .NET 9.0 environments, you may encounter reference issues due to missing or incompatible assemblies. To resolve this, manually add references to the required assemblies from the appropriate framework installation path or NuGet packages. Refer path location: C:\Program Files (x86)\Syncfusion\Essential Studio\WPF\ {product version}\precompiledassemblies\ {targetframework}\
Until version 31.2.2, while exporting themes from Theme Studio, separate projects were created for each framework. Starting with version 31.2.9, themes are exported as a single SDK-style project that supports multiple frameworks: `.NET Framework 4.6.2`, `.NET 8.0`, `.NET 9.0`, and `.NET 10`.

### Generating theme assembly
When opening the exported theme project, the `.NET Framework 4.6.2` will be selected by default.

Let us see the step-by-step procedure for ensuring theme assembly generation for exported theme projects.
If any of the supported frameworks (`.NET Framework 4.6.2`, `.NET 8.0`, `.NET 9.0`, or `.NET 10`) are not installed on your machine, you can remove the unavailable framework from the `<TargetFrameworks>` tag in the `MultiTargeting.targets` file located at: [ D:\Windows11Light\targets\MultiTargeting.targets ].This will resolve any compilation issues caused by missing frameworks.

**Step 1**
When running the exported single SDK-style theme project, you may encounter reference issues due to missing or incompatible assemblies across the targeted frameworks (4.6.2, .NET 8.0, .NET 9.0, and .NET 10). To resolve this, update the product version in the path specified in the `<SyncfusionInstallLocation>` tag of the exported .csproj theme project to match the installed product version, as shown in the image below. Reference path: C:\Program Files (x86)\Syncfusion\Essential Studio\WPF\{product version}

The following exported theme project should be attached to corresponding target frameworks used in the WPF application.
![Add Reference Path for Exported Theme Projects](ThemeStudio_images/Reference_Path.png)

<table>
<tr>
<th>
Target Framework</th><th>
Solution Project</th></tr>
<tr>
<td>
.Net 9.0</td><td>
Syncfusion.Themes.Windows11LightYellow.WPF_NET90.csproj </td>
</tr>
<tr>
<td>
.Net 8.0</td><td>
Syncfusion.Themes.Windows11LightYellow.WPF_NET80.csproj </td>
</tr>
<tr>
<td>
.Net Framework 4.6.2</td><td>
Syncfusion.Themes.Windows11LightYellow.WPF_2017.csproj </td></tr>
</table>
### Generating theme assembly

**Step 2**
Let us see the procedure for ensuring theme assembly generation for exported theme projects.

Rebuild the exported theme project in `Release` mode to generate the theme assembly.
Rebuild the exported single SDK-Style theme project in `Release` mode to generate the theme assembly.

The export theme project has default `ThemeStudio.snk` key pair. If it is not required, use the already created private key pair by referring to the export theme project inside the application properties or [Create a new key pair](https://docs.microsoft.com/en-us/dotnet/standard/assembly/create-public-private-key-pair) using Visual Studio if the private key pair was not created externally.

Expand Down
Binary file added wpf/Themes/ThemeStudio_images/Reference_Path.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified wpf/Themes/ThemeStudio_images/ThemeStudio-Themes-Folder.PNG
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
19 changes: 18 additions & 1 deletion wpf/dotnet-core-compatibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ Below table represents the supported Syncfusion<sup>&reg;</sup> Essential Studio
<th>.NET 7.0<br/></th>
<th>.NET 8.0<br/></th>
<th>.NET 9.0<br/></th>
<th>.NET 10.0<br/></th>
</tr>

<tr>
Expand All @@ -32,6 +33,7 @@ Below table represents the supported Syncfusion<sup>&reg;</sup> Essential Studio
<td>No<br/></td>
<td>No<br/></td>
<td>No<br/></td>
<td>No<br/></td>
</tr>

<tr>
Expand All @@ -41,6 +43,7 @@ From 20.4 (2022 Vol4) <br/></td>
<td>No<br/></td>
<td>No<br/></td>
<td>No<br/></td>
<td>No<br/></td>
</tr>

<tr>
Expand All @@ -50,6 +53,7 @@ From 21.1 (2023 Vol1) <br/></td>
<td>Yes<br/></td>
<td>No<br/></td>
<td>No<br/></td>
<td>No<br/></td>
</tr>

<tr>
Expand All @@ -59,6 +63,7 @@ From 23.2 (2023 Vol3 SP) <br/></td>
<td>Yes<br/></td>
<td>Yes<br/></td>
<td>No<br/></td>
<td>No<br/></td>
</tr>

<tr>
Expand All @@ -68,6 +73,7 @@ From 27.2 (2024 Vol3 SP) <br/></td>
<td>Yes<br/></td>
<td>Yes<br/></td>
<td>Yes<br/></td>
<td>No<br/></td>
</tr>

<tr>
Expand All @@ -77,6 +83,17 @@ From 29.1 (2025 Vol1) <br/></td>
<td>No<br/></td>
<td>Yes<br/></td>
<td>Yes<br/></td>
<td>No<br/></td>
</tr>

<tr>
<td>
From 31.2 (2025 Vol3 SP) <br/></td>
<td>No<br/></td>
<td>No<br/></td>
<td>Yes<br/></td>
<td>Yes<br/></td>
<td>Yes<br/></td>
</tr>

</table>
Expand All @@ -92,7 +109,7 @@ You can add the Syncfusion<sup>&reg;</sup> assembly references in one of the fol

Refer [control dependencies](https://help.syncfusion.com/wpf/control-dependencies) section to know control and its NuGet to use in the application. After that, add the required NuGet as reference and then you can use the control from ToolBox. The ToolBox will show a list of available controls once you have installed the NuGet package.

Refer [NuGet package](https://help.syncfusion.com/wpf/visual-studio-integration/nuget-packages) section to find more details about installing the NuGet package in your application.
Refer [NuGet package](https://help.syncfusion.com/extension/syncfusion-nuget-packages/nuget-packages) section to find more details about installing the NuGet package in your application.

### Adding assembly references from installed location

Expand Down
13 changes: 11 additions & 2 deletions wpf/samples.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,12 +45,21 @@ To explore any individual showcase sample from the `Syncfusion<sup>&reg;</sup> W

![Exploring Syncfusion WPF Showcase Samples](Guidetorunthesamples_images/Exploring-syncfusion-wpf-Showcase-sample.PNG)

All the sample browser projects are configured as single SDK-style projects that support multiple frameworks: `.NET Framework 4.6.2`, `.NET 8.0`, `.NET 9.0`, and `.NET 10`.

When you click the `Explore Demo Source` button, the `net10.0-windows` entry will be automatically removed from the targets file if .NET 10 is not installed on your machine, preventing any compilation errors.

To use the `.NET 10 framework`, install the required SDK and add `net10.0-windows` to the `<TargetFrameworks>` tag in the `MultiTargeting.targets` file located at the Samples Location: D:\WPF31.2.9\WPF\31.2.9\SampleBrowser\targets\MultiTargeting.targets as shown in the image below.

![WPF TargetFrameworks](Guidetorunthesamples_images/TargetFrameworks-wpf.jpg)

If you don’t have other frameworks installed and encounter compilation issues as a result, you can remove the unsupported framework from the `<TargetFrameworks>` tag in the same file and retain only the available ones to resolve the issue.

N> To run the individual control demos, please refer the instruction from [Running Individual Control Demos](https://github.com/syncfusion/wpf-demos#running-individual-control-demos).

## Online Samples

* Download and install `.NetCore` demos from [App Center](https://install.appcenter.ms/orgs/syncfusion-demos/apps/wpf-demos/distribution_groups/release).
* Download and install `.Net Framework` demos from [Microsoft Store](https://www.microsoft.com/en-us/p/syncfusion-wpf-controls-examples/9n99kdhrff6g?activetab=pivot:overviewtab).
* Download and install `.Net Framework` demos from [Microsoft Store](https://apps.microsoft.com/detail/9n99kdhrff6g?hl=en-US&gl=US).

## Download demos from online (Clone from github repository)

Expand Down