diff --git a/wpf/Guidetorunthesamples_images/TargetFrameworks-wpf.jpg b/wpf/Guidetorunthesamples_images/TargetFrameworks-wpf.jpg deleted file mode 100644 index fbfb404bfe..0000000000 Binary files a/wpf/Guidetorunthesamples_images/TargetFrameworks-wpf.jpg and /dev/null differ diff --git a/wpf/Themes/Theme-Studio.md b/wpf/Themes/Theme-Studio.md index 7177c182a9..78c30c0b53 100644 --- a/wpf/Themes/Theme-Studio.md +++ b/wpf/Themes/Theme-Studio.md @@ -274,21 +274,40 @@ 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) -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`. +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\ {target framework}\ -When opening the exported theme project, the `.NET Framework 4.6.2` will be selected by default. +### Generating theme assembly -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 `` tag in the `MultiTargeting.targets` file located at: [ D:\Windows11Light\targets\MultiTargeting.targets ].This will resolve any compilation issues caused by missing frameworks. +Let us see the step-by-step procedure for ensuring theme assembly generation for exported theme projects. -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 `` 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} +**Step 1** -![Add Reference Path for Exported Theme Projects](ThemeStudio_images/Reference_Path.png) +The following exported theme project should be attached to corresponding target frameworks used in the WPF application. -### Generating theme assembly + + + + + + + + + + + +
+Target Framework +Solution Project
+.Net 9.0 +Syncfusion.Themes.Windows11LightYellow.WPF_NET90.csproj
+.Net 8.0 +Syncfusion.Themes.Windows11LightYellow.WPF_NET80.csproj
+.Net Framework 4.6.2 +Syncfusion.Themes.Windows11LightYellow.WPF_2017.csproj
-Let us see the procedure for ensuring theme assembly generation for exported theme projects. +**Step 2** -Rebuild the exported single SDK-Style theme project in `Release` mode to generate the theme assembly. +Rebuild the exported 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. diff --git a/wpf/Themes/ThemeStudio_images/Reference_Path.png b/wpf/Themes/ThemeStudio_images/Reference_Path.png deleted file mode 100644 index 9d7b97a5ac..0000000000 Binary files a/wpf/Themes/ThemeStudio_images/Reference_Path.png and /dev/null differ diff --git a/wpf/Themes/ThemeStudio_images/ThemeStudio-Themes-Folder.PNG b/wpf/Themes/ThemeStudio_images/ThemeStudio-Themes-Folder.PNG index 4d6e0464e1..66131996de 100644 Binary files a/wpf/Themes/ThemeStudio_images/ThemeStudio-Themes-Folder.PNG and b/wpf/Themes/ThemeStudio_images/ThemeStudio-Themes-Folder.PNG differ diff --git a/wpf/samples.md b/wpf/samples.md index aff49a7dfe..50e279b378 100644 --- a/wpf/samples.md +++ b/wpf/samples.md @@ -45,16 +45,6 @@ To explore any individual showcase sample from the `Syncfusion® 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 `` 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 `` 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