From c1f06ae288fc8e8c45e5fb7bdcb161ecaaad0f6d Mon Sep 17 00:00:00 2001 From: Kesavaraman Date: Wed, 22 Jan 2025 16:59:45 +0530 Subject: [PATCH 1/7] trademark added --- .../ASPNET-Extension/Check-for-Updates.md | 20 +-- Extension/ASPNET-Extension/Overview.md | 40 ++--- .../ASPNET-Extension/Project-Conversion.md | 50 +++--- .../ASPNET-Extension/Project-Migration.md | 40 ++--- Extension/ASPNET-Extension/Sample-Creator.md | 58 +++---- .../Syncfusion-Project-Templates.md | 66 ++++---- .../ASPNET-Extension/Toolbox-Configuration.md | 40 ++--- Extension/ASPNET-Extension/Troubleshooting.md | 154 +++++++++--------- .../Command-Line-installation.md | 8 +- .../Download-ASPNET-MVC-Extension.md | 20 +-- Extension/ASPNET-MVC-Extension/Overview.md | 30 ++-- .../Project-Conversion.md | 102 ++++++------ .../ASPNET-MVC-Extension/Project-Migration.md | 50 +++--- .../ASPNET-MVC-Extension/Sample-Creator.md | 56 +++---- .../Step-by-Step-Installation.md | 44 ++--- .../Syncfusion-Project-Templates.md | 82 +++++----- .../Visual-Studio-Code/create-project.md | 32 ++-- .../download-and-installation.md | 26 +-- .../Visual-Studio-Code/overview.md | 8 +- .../Visual-Studio/Overview.md | 26 +-- .../Visual-Studio/Project-Conversion.md | 32 ++-- .../Visual-Studio/Project-Migration.md | 34 ++-- .../Visual-Studio/Sample-Creator.md | 36 ++-- .../Visual-Studio/Scaffolding.md | 36 ++-- .../Visual-Studio/Syncfusion-Notifications.md | 28 ++-- .../Syncfusion-Project-Templates.md | 44 ++--- .../Visual-Studio/check-for-updates.md | 14 +- .../download-and-installation.md | 22 +-- Extension/ASPNETCore-Extension/Overview.md | 36 ++-- .../Project-Conversion.md | 62 +++---- .../ASPNETCore-Extension/Project-Migration.md | 42 ++--- .../ASPNETCore-Extension/Sample-Creator.md | 50 +++--- .../Syncfusion-Project-Templates.md | 50 +++--- .../Overview.md | 28 ++-- .../Project-Conversion.md | 36 ++-- .../Project-Migration.md | 36 ++-- .../Sample-Creator.md | 38 ++--- .../Scaffolding.md | 36 ++-- .../Syncfusion-Notifications.md | 26 +-- .../Syncfusion-Project-Templates.md | 44 ++--- .../check-for-updates.md | 14 +- .../download-and-installation.md | 20 +-- .../Visual-Studio-Code/code-snippet.md | 44 ++--- .../Visual-Studio-Code/convert-project.md | 34 ++-- .../Visual-Studio-Code/create-project.md | 54 +++--- .../download-and-installation.md | 26 +-- .../Visual-Studio-Code/overview.md | 16 +- .../Visual-Studio-Code/upgrade-project.md | 22 +-- .../Visual-Studio/Syncfusion-Notifications.md | 28 ++-- .../Visual-Studio/code-generator.md | 38 ++--- .../Visual-Studio/convert-project.md | 40 ++--- .../download-and-installation.md | 22 +-- .../Visual-Studio/overview.md | 16 +- .../Visual-Studio/scaffolding.md | 50 +++--- .../Visual-Studio/template-studio.md | 82 +++++----- .../Visual-Studio/upgrade-project.md | 26 +-- .../Visual-Studio-Code/FAQ.md | 12 ++ .../configuration-options.md | 2 +- .../Visual-Studio-Code/getting-started.md | 10 +- .../Visual-Studio-Code/overview.md | 8 +- ...t-message-in-Syncfusion-Xamarin-Toolbox.md | 26 +-- ...sion-NuGet-packages-in-your-application.md | 10 +- ...the-new-project-window-of-Visual-Studio.md | 48 +++--- ...-two-icons-in-the-window-to-select-from.md | 12 +- ...control-after-installing-nuget-packages.md | 4 +- ...control-after-installing-NuGet-Packages.md | 2 +- ...al-Studio-How-can-to-get-them-installed.md | 32 ++-- ...w-to-select-from-How-to-get-rid-of-this.md | 8 +- .../Visual-Studio-Code/code-snippet.md | 34 ++-- .../Visual-Studio-Code/create-project.md | 16 +- .../download-and-installation.md | 26 +-- .../Visual-Studio-Code/overview.md | 12 +- .../Visual-Studio-Code/code-snippet.md | 32 ++-- .../Visual-Studio-Code/create-project.md | 24 +-- .../download-and-installation.md | 24 +-- .../Visual-Studio-Code/overview.md | 10 +- .../Visual-Studio/Syncfusion-Notifications.md | 28 ++-- .../Visual-Studio/Toolbox-Control.md | 44 ++--- .../download-and-installation.md | 20 +-- .../Visual-Studio/overview.md | 12 +- .../Visual-Studio/template-studio.md | 24 +-- .../NuGet-Packages.md | 60 +++---- .../NuGet-Uninstallation-process.md | 14 +- .../Register-the-Syncfusion-License-key.md | 36 ++-- .../Syncfusion-NuGet-Manager.md | 60 +++---- ...erences-via-Syncfusion-Reference-Manger.md | 46 +++--- ...ion-assemblies-in-Visual-Studio-project.md | 16 +- .../Migrate-the-Syncfusion-assemblies.md | 24 +-- .../Syncfusion-Reference-Manager/Overview.md | 10 +- .../Syncfusion-Troubleshooter/Overview.md | 24 +-- .../Syncfusion-Troubleshooter.md | 112 ++++++------- .../Syncfusion-Updates/Essential-Studio.md | 20 +-- Extension/UWP-Extension/Overview.md | 30 ++-- Extension/UWP-Extension/Project-Templates.md | 50 +++--- .../UWP-Extension/Syncfusion-Notifications.md | 28 ++-- Extension/WPF-Extension/Add-Item.md | 44 ++--- Extension/WPF-Extension/Add-References.md | 60 +++---- Extension/WPF-Extension/Check-for-Updates.md | 20 +-- Extension/WPF-Extension/Create-Project.md | 56 +++---- .../Download-and-Installation.md | 22 +-- Extension/WPF-Extension/Overview.md | 36 ++-- .../WPF-Extension/Syncfusion-Notifications.md | 28 ++-- Extension/WPF-Extension/Template-Studio.md | 64 ++++---- .../WPF-Extension/Toolbox-Configuration.md | 66 ++++---- Extension/WPF-Extension/Troubleshooting.md | 96 +++++------ .../WindowsForms-Extension/Add-References.md | 52 +++--- .../Check-for-Updates.md | 18 +- Extension/WindowsForms-Extension/Overview.md | 38 ++--- ...fusion-Item-Templates-for-Windows-Forms.md | 44 ++--- .../Syncfusion-Notifications.md | 26 +-- ...ion-Project-Templates-for-Windows-Forms.md | 58 +++---- .../WindowsForms-Extension/Template-Studio.md | 64 ++++---- .../Toolbox-Configuration.md | 38 ++--- .../WindowsForms-Extension/Troubleshooting.md | 94 +++++------ .../download-and-installation.md | 20 +-- .../Xamarin-Extension/Check-for-Updates.md | 20 +-- Extension/Xamarin-Extension/Create-Project.md | 72 ++++---- .../Download-and-Installation.md | 22 +-- .../Xamarin-Extension/Essential-UI-Kit.md | 20 +-- Extension/Xamarin-Extension/Overview.md | 24 +-- .../Syncfusion-Notifications.md | 28 ++-- Extension/Xamarin-Extension/Toolbox.md | 40 ++--- 122 files changed, 2207 insertions(+), 2187 deletions(-) diff --git a/Extension/ASPNET-Extension/Check-for-Updates.md b/Extension/ASPNET-Extension/Check-for-Updates.md index 6e491db9..e6c063cf 100644 --- a/Extension/ASPNET-Extension/Check-for-Updates.md +++ b/Extension/ASPNET-Extension/Check-for-Updates.md @@ -1,28 +1,28 @@ --- layout: post -title: Check for Updates | ASP.NET | Syncfusion -description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. +title: Check for Updates | ASP.NET | Syncfusion +description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. platform: extension control: Visual Studio Extensions documentation: ug --- -# Check for Updates in Syncfusion® ASP.NET Web Forms +# Check for Updates in Syncfusion® ASP.NET Web Forms - Syncfusion® provides Extensions to update the most recent version of the Essential Studio® release. Installing the most recent version ensures that you always have the most up-to-date features, fixes, and improvements. +Syncfusion® provides Extensions to update the most recent version of the Essential Studio® release. Installing the most recent version ensures that you always have the most up-to-date features, fixes, and improvements. -I> The Syncfusion® Check for updates is available beginning with v17.1.0.32. +I> The Syncfusion® Check for updates is available beginning with v17.1.0.32. You can check the availability of updates in Visual Studio and then install the update version if required. -1. Choose ** Syncfusion® -> Check for Updates…** in the Visual Studio menu +1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu - ![ Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) + ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. 2. When an update is available, the Update dialog box appears. - ![ Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) + ![Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) -3. Syncfusion® Essential Studio® can be downloaded from the Syncfusion® website by clicking the **Download** button. +3. Syncfusion® Essential Studio® can be downloaded from the Syncfusion® website by clicking the **Download** button. diff --git a/Extension/ASPNET-Extension/Overview.md b/Extension/ASPNET-Extension/Overview.md index 622b7d65..665e6321 100644 --- a/Extension/ASPNET-Extension/Overview.md +++ b/Extension/ASPNET-Extension/Overview.md @@ -1,9 +1,9 @@ --- layout: post -title: ASP.NET Web Forms (Essential JS 1) Extension | Extension | Syncfusion -description: The Syncfusion ASP.NET Web Forms Extensions provide quick access to create or configure the Syncfusion ASP.NET projects along with Essential JS 1 components +title: ASP.NET Web Forms (Essential JS 1) Extension | Extension | Syncfusion +description: The Syncfusion ASP.NET Web Forms Extensions provide quick access to create or configure the Syncfusion ASP.NET projects along with Essential JS 1 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- @@ -11,36 +11,36 @@ documentation: ug ## Overview -The Syncfusion® ASP.NET (Essential JS 1) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio. The Syncfusion® ASP.NET Extensions supports Microsoft Visual Studio 2010 or higher. +The Syncfusion® ASP.NET (Essential® JS 1) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio. The Syncfusion® ASP.NET Extensions supports Microsoft Visual Studio 2010 or higher. -I> The Syncfusion® ASP.NET (Essential JS 1) menu option is available from v17.1.0.32. +I> The Syncfusion® ASP.NET (Essential® JS 1) menu option is available from v17.1.0.32. -The Syncfusion® provides the following extension supports in Visual Studio: +The Syncfusion® provides the following extension supports in Visual Studio: -1. [ Syncfusion® ASP.NET (Essential JS 1) Project Template](https://help.syncfusion.com/extension/aspnet-extension/syncfusion-project-templates): To create the Syncfusion® ASP.NET (Essential JS 1) WebSite or Web application by adding the required Syncfusion® references, Scripts, CSS, and Web.config entries. -2. [Project Conversion](https://help.syncfusion.com/extension/aspnet-extension/project-conversion): To convert an existing ASP.NET WebSite or Web application into the Syncfusion® ASP.NET (Essential JS 1) WebSite or Web application by adding the required Syncfusion® assemblies and resource files. -3. [Migrate Project](https://help.syncfusion.com/extension/aspnet-extension/project-migration): Migrate the existing Syncfusion® ASP.NET WebSite or Web Application from one Essential Studio® version to another version. -4. [Sample Creator](https://help.syncfusion.com/extension/aspnet-extension/sample-creator): Create the Syncfusion® ASP.NET (Essential JS 1) WebSite or Web application projects with the required Syncfusion® configuration to start development with the required Syncfusion® controls. -5. [Troubleshooter](https://help.syncfusion.com/extension/syncfusion-troubleshooter/syncfusion-troubleshooter): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. -6. [Toolbox Configuration](https://help.syncfusion.com/common/essential-studio/utilities#toolbox-configuration): To configure the Syncfusion® controls into the Visual Studio .NET toolbox. +1. [Syncfusion® ASP.NET (Essential® JS 1) Project Template](https://help.syncfusion.com/extension/aspnet-extension/syncfusion-project-templates): To create the Syncfusion® ASP.NET (Essential® JS 1) WebSite or Web application by adding the required Syncfusion® references, Scripts, CSS, and Web.config entries. +2. [Project Conversion](https://help.syncfusion.com/extension/aspnet-extension/project-conversion): To convert an existing ASP.NET WebSite or Web application into the Syncfusion® ASP.NET (Essential® JS 1) WebSite or Web application by adding the required Syncfusion® assemblies and resource files. +3. [Migrate Project](https://help.syncfusion.com/extension/aspnet-extension/project-migration): Migrate the existing Syncfusion® ASP.NET WebSite or Web Application from one Essential Studio® version to another version. +4. [Sample Creator](https://help.syncfusion.com/extension/aspnet-extension/sample-creator): Create the Syncfusion® ASP.NET (Essential® JS 1) WebSite or Web application projects with the required Syncfusion® configuration to start development with the required Syncfusion® controls. +5. [Troubleshooter](https://help.syncfusion.com/extension/syncfusion-troubleshooter/syncfusion-troubleshooter): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. +6. [Toolbox Configuration](https://help.syncfusion.com/common/essential-studio/utilities#toolbox-configuration): To configure the Syncfusion® controls into the Visual Studio .NET toolbox. **No project selected in Visual Studio** -![ Syncfusion® Menu when No project selected in Visual Studio](Overview-images/ Syncfusion® _Menu_OverView1.png) +![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Microsoft ASP.NET WebSite or Web application in Visual Studio** -![ Syncfusion® Menu when Selected Microsoft ASP.NET application in Visual Studio](Overview-images/ Syncfusion® _Menu_OverView2.png) +![Syncfusion® Menu when Selected Microsoft ASP.NET application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) -**Selected Syncfusion® ASP.NET (Essential JS1) WebSite or Web application in Visual Studio** +**Selected Syncfusion® ASP.NET (Essential® JS1) WebSite or Web application in Visual Studio** -![ Syncfusion® Menu when Selected Synfusion ASP.NET EJ1 application in Visual Studio](Overview-images/ Syncfusion® _Menu_OverView3.png) +![Syncfusion® Menu when Selected Synfusion® ASP.NET EJ1 application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) -N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. +N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. -The Syncfusion® ASP.NET Visual Studio Extensions are installed along with the following setups, +The Syncfusion® ASP.NET Visual Studio Extensions are installed along with the following setups, -* Essential Studio® for Enterprise Edition with the platform ASP.NET -* Essential Studio® for ASP.NET +* Essential Studio® for Enterprise Edition with the platform ASP.NET +* Essential Studio® for ASP.NET diff --git a/Extension/ASPNET-Extension/Project-Conversion.md b/Extension/ASPNET-Extension/Project-Conversion.md index 3e9725d8..e5fa7167 100644 --- a/Extension/ASPNET-Extension/Project-Conversion.md +++ b/Extension/ASPNET-Extension/Project-Conversion.md @@ -1,41 +1,41 @@ --- layout: post -title: Convert Project | ASP.NET Web Forms (Essential JS1) | Syncfusion -description: Syncfusion ASP.NET Web Forms (Essential JS1) Project Conversion Extension that converts an existing ASP.NET project into a Essential JS1 ASP.NET Project. +title: Convert Project | ASP.NET Web Forms (Essential JS1) | Syncfusion +description: Syncfusion ASP.NET Web Forms (Essential JS1) Project Conversion Extension that converts an existing ASP.NET project into a Essential JS1 ASP.NET Project. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Converting ASP.NET application to Syncfusion® ASP.NET application +# Converting ASP.NET application to Syncfusion® ASP.NET application -The Syncfusion® project conversion add-in for Visual Studio converts an existing ASP.NET application into the Syncfusion® ASP.NET (Essential JS 1) application by adding the necessary assemblies and resource files. +The Syncfusion® project conversion add-in for Visual Studio converts an existing ASP.NET application into the Syncfusion® ASP.NET (Essential® JS 1) application by adding the necessary assemblies and resource files. -I> The Syncfusion® ASP.NET Web Application Project Conversion utility is available beginning with v13.1.0.30. +I> The Syncfusion® ASP.NET Web Application Project Conversion utility is available beginning with v13.1.0.30. -The following steps will assist you to use the Syncfusion® Project conversion in your existing ASP.NET application: +The following steps will assist you to use the Syncfusion® Project conversion in your existing ASP.NET application: -> Before use, the Syncfusion® ASP.NET Web Forms Project Conversion, check whether the **ASP.NET Web Forms Extensions - Syncfusion® ** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. +> Before use, the Syncfusion® ASP.NET Web Forms Project Conversion, check whether the **ASP.NET Web Forms Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. 1. Open an existing Microsoft ASP.NET Project or create a new Microsoft ASP.NET Project. 2. Open the conversion dialog by selecting one of the following options: **Option 1** - Click ** Syncfusion® Menu** and choose **Essential Studio for ASP.NET Web Forms (EJ1) > Convert to Syncfusion® ASP.NET Application…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Convert to Syncfusion® ASP.NET Application…** in **Visual Studio**. - ![ Syncfusion Essential JS 1 ASP.NET Web Forms Project Conversion via Syncfusion® menu](Convert-Project_images/ Syncfusion® _Menu_Project_Conversion1.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Conversion via Syncfusion® menu](Convert-Project_images/Syncfusion_Menu_Project_Conversion1.png) - N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2** - Right-click the Project from Solution Explorer, select ** Syncfusion® Web (Essential JS 1)**, and choose the **Convert to Syncfusion® ASP.NET (Essential JS 1) Application...** Refer to the following screenshot for more information. + Right-click the Project from Solution Explorer, select **Syncfusion® Web (Essential® JS 1)**, and choose the **Convert to Syncfusion® ASP.NET (Essential® JS 1) Application...** Refer to the following screenshot for more information. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Project Conversion add-in](Convert-Project_images/Project-Conversion-img1.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Conversion add-in](Convert-Project_images/Project-Conversion-img1.png) 3. The Project Conversion Wizard appears, allowing you to configure the project. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Project Conversion wizard](Convert-Project_images/Project-Conversion-img2.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Conversion wizard](Convert-Project_images/Project-Conversion-img2.png) The following configurations are used in the Project Conversion wizard: @@ -43,15 +43,15 @@ The following steps will assist you to use the Syncfusion® project. + **Choose the Theme:** Based on the theme chosen, the project's master page will be updated. The Theme Preview section displays a preview of the components before converting them into a Syncfusion® project. ![Choose the theme to apply on the master page of the ASP.NET Web Forms project](Convert-Project_images/Project-Conversion-img4.png) - **Choose CDN Support:** The project's master page will be updated based on the required Syncfusion® CDN links. + **Choose CDN Support:** The project's master page will be updated based on the required Syncfusion® CDN links. - ![Choose CDN Support to refer the Syncfusion assets from CDN for ASP.NET Web Forms project](Convert-Project_images/Project-Conversion-img6.jpeg) + ![Choose CDN Support to refer the Syncfusion® assets from CDN for ASP.NET Web Forms project](Convert-Project_images/Project-Conversion-img6.jpeg) - **Copy Global Resources:** If you select the Copy Global Resources option, the Syncfusion® localization culture files will be shipped to the project from the Installed Location. + **Copy Global Resources:** If you select the Copy Global Resources option, the Syncfusion® localization culture files will be shipped to the project from the Installed Location. ![Choose Copy Global Resources to ship the localization culture files for ASP.NET Web Forms project](Convert-Project_images/Project-Conversion-img7.jpeg) @@ -61,16 +61,16 @@ The following steps will assist you to use the Syncfusion® project. If you choose **No**, the project will be converted to a Syncfusion® project without a backup. +4. When you click the **Convert** button, the **Project Backup** dialog will appear. If you click **Yes** in the dialog, it will backup the current project before converting it to a Syncfusion® project. If you choose **No**, the project will be converted to a Syncfusion® project without a backup. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Project Conversion backup dialog](Convert-Project_images/Project-Conversion-img9.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Conversion backup dialog](Convert-Project_images/Project-Conversion-img9.png) -5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project. +5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project. - ![Reference assemblies use of Syncfusion Essential JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img10.png) + ![Reference assemblies use of Syncfusion® Essential® JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img10.png) - ![Scripts and CSS for Syncfusion Essential JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img11.png) + ![Scripts and CSS for Syncfusion® Essential® JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img11.png) - ![Web.config assembly reference of Syncfusion Essential JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img12.png) + ![Web.config assembly reference of Syncfusion® Essential® JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img12.png) -6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file +6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNET-Extension/Project-Migration.md b/Extension/ASPNET-Extension/Project-Migration.md index e9a007d7..a29e6b91 100644 --- a/Extension/ASPNET-Extension/Project-Migration.md +++ b/Extension/ASPNET-Extension/Project-Migration.md @@ -1,53 +1,53 @@ --- layout: post -title: Upgrade Project | ASP.NET Web Forms | Syncfusion -description: Project Migration is a add-in that allows you to migrate existing Syncfusion ASP.NET Web Forms project from one Essential Studio version to another version +title: Upgrade Project | ASP.NET Web Forms | Syncfusion +description: Project Migration is a add-in that allows you to migrate existing Syncfusion ASP.NET Web Forms project from one Essential Studio version to another version platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Upgrading Syncfusion® ASP.NET application to latest version +# Upgrading Syncfusion® ASP.NET application to latest version -The Syncfusion® ASP.NET migration add-in for Visual Studio allows you to migrate an existing Syncfusion® ASP.NET application from one version of Essential Studio® version to another version. This reduces the amount of manual work required when migrating the Syncfusion® version. +The Syncfusion® ASP.NET migration add-in for Visual Studio allows you to migrate an existing Syncfusion® ASP.NET application from one version of Essential Studio® version to another version. This reduces the amount of manual work required when migrating the Syncfusion® version. -I> The Syncfusion® ASP.NET Web Application Project Migration utility is available beginning with v13.1.0.30. +I> The Syncfusion® ASP.NET Web Application Project Migration utility is available beginning with v13.1.0.30. -To migrate you’re existing Syncfusion® ASP.NET application, follow the steps below. +To migrate you’re existing Syncfusion® ASP.NET application, follow the steps below. -> Before use, the Syncfusion® ASP.NET Web Forms Project Migration, check whether the **ASP.NET Web Forms Extensions - Syncfusion® ** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. +> Before use, the Syncfusion® ASP.NET Web Forms Project Migration, check whether the **ASP.NET Web Forms Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. 1. To launch Migration Wizard, select one of the following options: **Option 1** - Click ** Syncfusion® Menu** and choose **Essential Studio for ASP.NET Web Forms (EJ1) > Migrate Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Migrate Project…** in **Visual Studio**. - ![ Syncfusion Essential JS 1 ASP.NET Web Forms Project Migration via Syncfusion® menu](Upgrade-Project_images/ Syncfusion® _Menu_Project_Migration1.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Migration via Syncfusion® menu](Upgrade-Project_images/Syncfusion_Menu_Project_Migration1.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2** - Right-click the ** Syncfusion® ASP.NET Application** from Solution Explorer and select ** Syncfusion® Web (Essential JS 1)**. Choose **Migrate the Essential JS 1 Project to Another version…** + Right-click the **Syncfusion® ASP.NET Application** from Solution Explorer and select **Syncfusion® Web (Essential® JS 1)**. Choose **Migrate the Essential® JS 1 Project to Another version…** - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Project Migration add-in](Upgrade-Project_images/Project-Migration_img1.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Migration add-in](Upgrade-Project_images/Project-Migration_img1.png) -2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine. +2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Project Migration wizard](Upgrade-Project_images/Project-Migration_img2.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Migration wizard](Upgrade-Project_images/Project-Migration_img2.png) 3. The **Project Migration** window allows you to configure the following options: - i. **Essential Studio Version:** Choose a version from the list of Syncfusion® versions that have been installed. + i. **Essential Studio® Version:** Choose a version from the list of Syncfusion® versions that have been installed. ii. **Assemblies From:** Choose the assembly location, from where the assembly will be added to the project. ![Choose the assembly location, from where the assembly is added to the project](Upgrade-Project_images/Project-Migration_img3.jpeg) -4. Click the **Migrate** Button. The **Project Backup** dialogue box appears. If you select **Yes** in the dialog, it will backup the current project before migrating the Syncfusion® project. If you select **No**, the project will be migrated to the required Syncfusion® version without a backup. +4. Click the **Migrate** Button. The **Project Backup** dialogue box appears. If you select **Yes** in the dialog, it will backup the current project before migrating the Syncfusion® project. If you select **No**, the project will be migrated to the required Syncfusion® version without a backup. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Project Migration backup dialog](Upgrade-Project_images/Project-Migration_img4.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Migration backup dialog](Upgrade-Project_images/Project-Migration_img4.png) -5. The Syncfusion® Reference Assemblies, Scripts, and CSS, Web. Config entries in the project are updated to the corresponding version. +5. The Syncfusion® Reference Assemblies, Scripts, and CSS, Web. Config entries in the project are updated to the corresponding version. -6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file +6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNET-Extension/Sample-Creator.md b/Extension/ASPNET-Extension/Sample-Creator.md index abafe14a..e719f178 100644 --- a/Extension/ASPNET-Extension/Sample-Creator.md +++ b/Extension/ASPNET-Extension/Sample-Creator.md @@ -1,43 +1,43 @@ --- layout: post -title: Create Samples | ASP.NET Web Forms (Essential JS 1) | Syncfusion -description: Sample Creator is the utility that allows you to create Syncfusion ASP.NET WebForms (Essential JS 1) Projects along with the samples +title: Create Samples | ASP.NET Web Forms (Essential JS 1) | Syncfusion +description: Sample Creator is the utility that allows you to create Syncfusion ASP.NET WebForms (Essential JS 1) Projects along with the samples platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Creating ASP.NET Samples through the Syncfusion® ASP.NET Sample Creator +# Creating ASP.NET Samples through the Syncfusion® ASP.NET Sample Creator -The Syncfusion® Sample Creator is a utility that allows you to create Syncfusion® ASP.NET (Essential JS 1) Projects with sample code for required Syncfusion® component features and configuration of Syncfusion® components. +The Syncfusion® Sample Creator is a utility that allows you to create Syncfusion® ASP.NET (Essential® JS 1) Projects with sample code for required Syncfusion® component features and configuration of Syncfusion® components. -To create the Syncfusion® ASP.NET (Essential JS 1) Application using the Sample Creator utility, follow the steps below: +To create the Syncfusion® ASP.NET (Essential® JS 1) Application using the Sample Creator utility, follow the steps below: -1. To launch the ASP.NET (Essential JS 1) Sample Creator, select one of the following options: +1. To launch the ASP.NET (Essential® JS 1) Sample Creator, select one of the following options: **Option 1:** - Click ** Syncfusion® Menu** and choose **Essential Studio for ASP.NET Web Forms (EJ1) > Launch Sample Creator…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Launch Sample Creator…** in **Visual Studio**. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms control panel to launch Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/ Syncfusion® _Menu_Sample_Creator.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms control panel to launch Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/Syncfusion_Menu_Sample_Creator.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2:** - Launch the Syncfusion® ASP.NET (Essential JS 1) Control Panel. To run the ASP.NET (Essential JS 1) Sample Creator, click the Sample Creator button. More information can be found in the screenshot below. + Launch the Syncfusion® ASP.NET (Essential® JS 1) Control Panel. To run the ASP.NET (Essential® JS 1) Sample Creator, click the Sample Creator button. More information can be found in the screenshot below. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms control panel to launch Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/SampleCreator-img1.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms control panel to launch Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/SampleCreator-img1.png) -2. The Syncfusion® components and their features are listed in the ASP.NET (Essential JS 1) Sample Creator. +2. The Syncfusion® components and their features are listed in the ASP.NET (Essential® JS 1) Sample Creator. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator wizard](Create-Samples_images/SampleCreator-img2.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator wizard](Create-Samples_images/SampleCreator-img2.png) - **Components Selection:** Choose the required components. The components are grouped with Syncfusion® products, and the components are grouped by product. + **Components Selection:** Choose the required components. The components are grouped with Syncfusion® products, and the components are grouped by product. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator controls selection](Create-Samples_images/SampleCreator-img3.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator controls selection](Create-Samples_images/SampleCreator-img3.jpeg) **Feature Selection:** Based on the components, the feature is enabled to choose the features of the corresponding components. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator features selection](Create-Samples_images/SampleCreator-img4.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator features selection](Create-Samples_images/SampleCreator-img4.jpeg) **Project Configuration** @@ -49,35 +49,35 @@ To create the Syncfusion® ASP.NET (Essen * **VS Version:** Choose the Visual Studio version and Framework. - * **Name:** Name your Syncfusion® ASP.NET Web Forms (Essential JS 1) Application. + * **Name:** Name your Syncfusion® ASP.NET Web Forms (Essential® JS 1) Application. * **Location:** Choose the target location of your project. - * **Theme Selection:** Choose the required theme. This section shows the controls preview before creating the Syncfusion® project. + * **Theme Selection:** Choose the required theme. This section shows the controls preview before creating the Syncfusion® project. - ![ Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator project configuration selection](Create-Samples_images/SampleCreator-img5.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator project configuration selection](Create-Samples_images/SampleCreator-img5.png) 2. Click the **Create** button. After you've finished creating the project, open it by clicking **Yes**. If you click **No**, the project's corresponding location will be opened. For more information, see the screenshot below. - ![The project successfully created using Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/SampleCreator-img6.png) + ![The project successfully created using Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/SampleCreator-img6.png) - 3. The new Syncfusion® ASP.NET (Essential JS 1) project is created with the resources. + 3. The new Syncfusion® ASP.NET (Essential® JS 1) project is created with the resources. * Added the required Controllers and View files in the project. - ![Required ASPX and Class files for Syncfusion Essential JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img7.png) + ![Required ASPX and Class files for Syncfusion® Essential® JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img7.png) - * Under Project Reference, the necessary Syncfusion® assemblies are added for selected components. + * Under Project Reference, the necessary Syncfusion® assemblies are added for selected components. - ![Required reference assemblies for Syncfusion Essential JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img8.png) + ![Required reference assemblies for Syncfusion® Essential® JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img8.png) - * Syncfusion® ASP.NET (Essential JS 1) scripts and theme files were included. + * Syncfusion® ASP.NET (Essential® JS 1) scripts and theme files were included. - ![Required Scripts and Themes files for Syncfusion Essential JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img9.png) + ![Required Scripts and Themes files for Syncfusion® Essential® JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img9.png) - * Configure the Web.Config file by adding the Syncfusion® reference assemblies, namespaces and controls. + * Configure the Web.Config file by adding the Syncfusion® reference assemblies, namespaces and controls. - ![Required Web.config assembliesa and namespaces entry for Syncfusion Essential JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img10.png) + ![Required Web.config assembliesa and namespaces entry for Syncfusion® Essential® JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img10.png) diff --git a/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md index e5a34891..6b35ea97 100644 --- a/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md +++ b/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md @@ -1,88 +1,88 @@ --- layout: post -title: Create Project | ASP.NET Web Forms | Syncfusion -description: Syncfusion provides Visual Studio Project Templates for the ASP.NET platform to create Syncfusion ASP.NET Web Application using Essential JS 1 components +title: Create Project | ASP.NET Web Forms | Syncfusion +description: Syncfusion provides Visual Studio Project Templates for the ASP.NET platform to create Syncfusion ASP.NET Web Application using Essential JS 1 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Creating Syncfusion® ASP.NET Web Application +# Creating SyncfusionASP.NET Web Application - Syncfusion® offers **Visual Studio Project Templates** for the Syncfusion® ASP.NET platform, which can be used to create a Syncfusion® ASP.NET Web Application or a Syncfusion® ASP.NET Web Site. +Syncfusion® offers **Visual Studio Project Templates** for the Syncfusion® ASP.NET platform, which can be used to create a Syncfusion® ASP.NET Web Application or a Syncfusion® ASP.NET Web Site. -I> Syncfusion® ASP.NET Website templates are available beginning with v12.2.0.36, and Syncfusion® ASP.NET Web Application templates are available beginning with v13.3.0.7. +I> Syncfusion® ASP.NET Website templates are available beginning with v12.2.0.36, and Syncfusion® ASP.NET Web Application templates are available beginning with v13.3.0.7. -To create the ** Syncfusion® ASP.NET (Essential JS 1) Application** using the **Visual Studio Project Template**, follow the steps below: +To create the **Syncfusion® ASP.NET (Essential® JS 1) Application** using the **Visual Studio Project Template**, follow the steps below: -> Before use the Syncfusion® ASP.NET Web Forms Project Template, check whether the **ASP.NET Web Forms Extensions - Syncfusion® ** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. +> Before use the Syncfusion® ASP.NET Web Forms Project Template, check whether the **ASP.NET Web Forms Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. -1. To create a Syncfusion® ASP.NET (Essential JS 1) Web Forms project, use one of the following methods: +1. To create a Syncfusion® ASP.NET (Essential® JS 1) Web Forms project, use one of the following methods: **Option 1** - Click ** Syncfusion® Menu** and choose **Essential Studio for ASP.NET Web Forms (EJ1) > Create New Syncfusion® ASPNET Web Forms Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Create New Syncfusion® ASPNET Web Forms Project…** in **Visual Studio**. - ![Choose Syncfusion ASP.NET Web Application or Syncfusion® ASP.NET Web Site from Visual Studio new project dialog via Syncfusion® menu](Create-Project_images/ Syncfusion® _Menu_ProjectTemplate.png) + ![Choose Syncfusion® ASP.NET Web Application or Syncfusion® ASP.NET Web Site from Visual Studio new project dialog via Syncfusion® menu](Create-Project_images/Syncfusion_Menu_ProjectTemplate.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2** - Choose **File > New > Project** and navigate to ** Syncfusion® > Web > Syncfusion® ASP.NET Web Forms Application** in **Visual Studio**. + Choose **File > New > Project** and navigate to **Syncfusion > Web > Syncfusion® ASP.NET Web Forms Application** in **Visual Studio**. - ![Choose Syncfusion ASP.NET Web Forms Application from Visual Studio new project dialog](Create-Project_images/ Syncfusion® -Project-Templates-img1.png) + ![Choose Syncfusion® ASP.NET Web Forms Application from Visual Studio new project dialog](Create-Project_images/Syncfusion-Project-Templates-img1.png) 2. Name the **project**, select the destination location, and configure the project's .NET Framework, then click **OK**. The Project Configuration Wizard is displayed. - N> The minimum target framework for Syncfusion® ASP.NET Project Templates is 3.5. + N> The minimum target framework for Syncfusion® ASP.NET Project Templates is 3.5. -3. Using the following Project Configuration window, select the options to configure the Syncfusion® ASP.NET Web Forms Application. +3. Using the following Project Configuration window, select the options to configure the Syncfusion® ASP.NET Web Forms Application. - ![ Syncfusion® Essential JS 1 ASP.NET Web Forms Project configuration wizard](Create-Project_images/ Syncfusion® -Project-Templates-img2.png) + ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project configuration wizard](Create-Project_images/Syncfusion-Project-Templates-img2.png) **Project Configurations** **Project Type:** Choose the appropriate Project Type either Website or WebApplication. - ![Choose appropriate Project Type version](Create-Project_images/ Syncfusion® -Project-Templates-img3.png) + ![Choose appropriate Project Type version](Create-Project_images/Syncfusion-Project-Templates-img3.png) **Theme:** Choose the appropriate theme. - ![Choose required theme](Create-Project_images/ Syncfusion® -Project-Templates-img4.png) + ![Choose required theme](Create-Project_images/Syncfusion-Project-Templates-img4.png) **Language:** Choose the language, either C# or VB. - ![Choose required language](Create-Project_images/ Syncfusion® -Project-Templates-img5.png) + ![Choose required language](Create-Project_images/Syncfusion-Project-Templates-img5.png) **Assemblies From:** Choose the assembly location, from where the assembly will be added to the project. - ![Choose the assembly location from where it is going to be added to the prject](Create-Project_images/ Syncfusion® -Project-Templates-img6.png) + ![Choose the assembly location from where it is going to be added to the prject](Create-Project_images/Syncfusion-Project-Templates-img6.png) -**Assets From:** Choose the Syncfusion® Essential JS assets to be added to the ASP.NET Web Forms Project from the NuGet, CDN, or Installed Location. +**Assets From:** Choose the Syncfusion® Essential® JS assets to be added to the ASP.NET Web Forms Project from the NuGet, CDN, or Installed Location. - ![Choose the Syncfusion Essential JS assets to ASP.NET Web Forms Project, either NuGet, CDN or Installed Location](Create-Project_images/ Syncfusion® -Project-Templates-img7.png) + ![Choose the Syncfusion® Essential® JS assets to ASP.NET Web Forms Project, either NuGet, CDN or Installed Location](Create-Project_images/Syncfusion-Project-Templates-img7.png) **Installed Version** Choose the version of the project that needs to be created. - ![Choose the Version](Create-Project_images/ Syncfusion® -Project-Templates-img8.png) + ![Choose the Version](Create-Project_images/Syncfusion-Project-Templates-img8.png) -4. Select the components, Assemblies, and Scripts that should be added to the project, and then click the Create button. The Syncfusion® ASP.NET Web Forms project will be created. +4. Select the components, Assemblies, and Scripts that should be added to the project, and then click the Create button. The Syncfusion® ASP.NET Web Forms project will be created. - ![ Syncfusion Essential ASP.NET Web Feature selection](Create-Project_images/ Syncfusion® -Project-Templates-img9.png) + ![Syncfusion® Essential® ASP.NET Web Feature selection](Create-Project_images/Syncfusion-Project-Templates-img9.png) - ![ Syncfusion Essential ASP.NET Web Feature selection](Create-Project_images/ Syncfusion® -Project-Templates-img14.PNG) + ![Syncfusion® Essential® ASP.NET Web Feature selection](Create-Project_images/Syncfusion-Project-Templates-img14.PNG) -5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project. +5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project. - ![References of Syncfusion Essential JS 1 ASP.NET Web Forms project](Create-Project_images/ Syncfusion® -Project-Templates-img10.png) + ![References of Syncfusion® Essential® JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img10.png) - ![Scripts and Themes of Syncfusion Essential JS 1 ASP.NET Web Forms project](Create-Project_images/ Syncfusion® -Project-Templates-img11.png) + ![Scripts and Themes of Syncfusion® Essential® JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img11.png) - ![Web.config references of Syncfusion Essential JS 1 ASP.NET Web Forms project](Create-Project_images/ Syncfusion® -Project-Templates-img12.png) + ![Web.config references of Syncfusion® Essential® JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img12.png) -6.Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +6.Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![ Syncfusion license registration information message box for Syncfusion® Essential JS 1 ASP.NET Web Forms project](Create-Project_images/ Syncfusion® -Project-Templates-img13.jpeg) + ![Syncfusion® license registration information message box for Syncfusion® Essential® JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img13.jpeg) diff --git a/Extension/ASPNET-Extension/Toolbox-Configuration.md b/Extension/ASPNET-Extension/Toolbox-Configuration.md index cdf5c09f..20934e81 100644 --- a/Extension/ASPNET-Extension/Toolbox-Configuration.md +++ b/Extension/ASPNET-Extension/Toolbox-Configuration.md @@ -1,7 +1,7 @@ --- layout: post -title: Toolbox Configuration | ASP.NET | Syncfusion -description: This section provides information regarding all the Syncfusion Essential Studio utilities and its usage +title: Toolbox Configuration | ASP.NET | Syncfusion +description: This section provides information regarding all the Syncfusion Essential Studio utilities and its usage platform: extension control: Essential Studio documentation: ug @@ -9,27 +9,27 @@ documentation: ug # Toolbox Configuration -The Syncfusion® Toolbox Installer utility incorporates the Syncfusion® ASP.NET Web Forms components into the Visual Studio.NET toolbox. +The Syncfusion® Toolbox Installer utility incorporates the Syncfusion® ASP.NET Web Forms components into the Visual Studio.NET toolbox. -N> Toolbox configuration support is not available in the Visual Studio Express Edition. However, you can manually configure the Syncfusion® components in the Visual Studio Express Toolbox. To do so, see [Manual Toolbox Configuration](https://help.syncfusion.com/common/faq/how-to-configure-the-toolbox-of-visual-studio-manually). +N> Toolbox configuration support is not available in the Visual Studio Express Edition. However, you can manually configure the Syncfusion® components in the Visual Studio Express Toolbox. To do so, see [Manual Toolbox Configuration](https://help.syncfusion.com/common/faq/how-to-configure-the-toolbox-of-visual-studio-manually). -If the “Configure Syncfusion® components in Visual Studio” checkbox is selected from the installer UI while installing the Syncfusion® ASP.NET Web Forms installer, Syncfusion® components will be automatically configured in the Visual Studio toolbox. +If the “Configure Syncfusion® components in Visual Studio” checkbox is selected from the installer UI while installing the Syncfusion® ASP.NET Web Forms installer, Syncfusion® components will be automatically configured in the Visual Studio toolbox. -To add the Syncfusion® ASP.NET Web Forms components via the Syncfusion® Toolbox Installer, perform the following steps: +To add the Syncfusion® ASP.NET Web Forms components via the Syncfusion® Toolbox Installer, perform the following steps: 1. To launch the Toolbox configuration utility, select one of the following options: **Option 1:** - Open the Syncfusion® Control Panel, click **Add On and Utilities > Toolbox Installer**. + Open the Syncfusion® Control Panel, click **Add On and Utilities > Toolbox Installer**. ![Add On and Utilities](Toolbox-Configuration_images/Toolbox-Configuration_img1.png) **Option 2:** - Click ** Syncfusion® menu** and choose **Essential Studio for ASP.NET Web Forms (EJ1) > Toolbox Configuration...** in **Visual Studio** + Click **Syncfusion® menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Toolbox Configuration...** in **Visual Studio** - ![Toolbox Installer via Syncfusion® menu](Toolbox-Configuration_images/ Syncfusion® _Menu_Toolbox.png) + ![Toolbox Installer via Syncfusion® menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. 2. Toolbox Installer will be opened. @@ -37,17 +37,17 @@ To add the Syncfusion® ASP.NET Web Forms The following options are available in Toolbox Configuration: - * Install VS2005 – Configures Framework 2.0 Syncfusion® controls in VS 2005 toolbox. - * Install VS2008 – Configures Framework 3.5 Syncfusion® controls in VS 2008 toolbox. - * Install VS2010 – Configures Framework 4.0 Syncfusion® controls in VS 2010 toolbox. - * Install VS2012 – Configures Framework 4.5 Syncfusion® controls in VS 2012 toolbox. - * Install VS2013 – Configures Framework 4.5.1 Syncfusion® controls in VS 2013 toolbox. - * Install VS2015 – Configures Framework 4.6 Syncfusion® controls in VS 2015 toolbox. - * Install VS2017 – Configures Framework 4.6 Syncfusion® controls in VS 2017 toolbox. - * Install VS2019 – Configures Framework 4.6 Syncfusion® controls in VS 2019 toolbox. - * Install VS2022 – Configures Framework 4.6 Syncfusion® components in VS 2022 toolbox. + * Install VS2005 – Configures Framework 2.0 Syncfusion® controls in VS 2005 toolbox. + * Install VS2008 – Configures Framework 3.5 Syncfusion® controls in VS 2008 toolbox. + * Install VS2010 – Configures Framework 4.0 Syncfusion® controls in VS 2010 toolbox. + * Install VS2012 – Configures Framework 4.5 Syncfusion® controls in VS 2012 toolbox. + * Install VS2013 – Configures Framework 4.5.1 Syncfusion® controls in VS 2013 toolbox. + * Install VS2015 – Configures Framework 4.6 Syncfusion® controls in VS 2015 toolbox. + * Install VS2017 – Configures Framework 4.6 Syncfusion® controls in VS 2017 toolbox. + * Install VS2019 – Configures Framework 4.6 Syncfusion® controls in VS 2019 toolbox. + * Install VS2022 – Configures Framework 4.6 Syncfusion® components in VS 2022 toolbox. - N> You can also configure Syncfusion® components from a lower version Framework assembly to higher version of Visual Studio. + N> You can also configure Syncfusion® components from a lower version Framework assembly to higher version of Visual Studio. 3. An Information message is displayed, indicating that Toolbox has been successfully configured. Click OK. diff --git a/Extension/ASPNET-Extension/Troubleshooting.md b/Extension/ASPNET-Extension/Troubleshooting.md index 105059a8..da0562ec 100644 --- a/Extension/ASPNET-Extension/Troubleshooting.md +++ b/Extension/ASPNET-Extension/Troubleshooting.md @@ -1,15 +1,15 @@ --- layout: post -title: Syncfusion Troubleshooter | ASP.NET | Syncfusion -description: Syncfusion Troubleshooter is Visual Studio extension to troubleshoot the configuration issues in Syncfusion assembly reference, webconfig entries in projects. +title: Syncfusion Troubleshooter | ASP.NET | Syncfusion +description: Syncfusion Troubleshooter is Visual Studio extension to troubleshoot the configuration issues in Syncfusion assembly reference, webconfig entries in projects. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Troubleshoot the project -Troubleshoot the project with the Syncfusion® configuration and apply the fix, such as wrong.NET Framework version of a Syncfusion® assembly to the project or missing any Syncfusion® dependent assembly of a referred assembly. The Syncfusion® Troubleshooter can perform the following tasks: +Troubleshoot the project with the Syncfusion® configuration and apply the fix, such as wrong.NET Framework version of a Syncfusion® assembly to the project or missing any Syncfusion® dependent assembly of a referred assembly. The Syncfusion® Troubleshooter can perform the following tasks: * Report the Configuration issues. @@ -17,41 +17,41 @@ Troubleshoot the project with the Syncfusion®® Troubleshooter by Visual Studio. +The steps below will assist you in using the Syncfusion® Troubleshooter by Visual Studio. -> Before use the Syncfusion® Troubleshooter for ASP.NET Web Forms, check whether the **ASP.NET Web Forms Extensions - Syncfusion® ** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. +> Before use the Syncfusion® Troubleshooter for ASP.NET Web Forms, check whether the **ASP.NET Web Forms Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. -1. To launch the Syncfusion® Troubleshooter Wizard, select one of the options below: +1. To launch the Syncfusion® Troubleshooter Wizard, select one of the options below: **Option 1** - Open an existing Syncfusion® ASP.NET Web Forms Application, Click ** Syncfusion® Menu** and choose **Essential Studio for ASP.NET Web Forms (EJ1) > Troubleshoot…** in Visual Studio. + Open an existing Syncfusion® ASP.NET Web Forms Application, Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Troubleshoot…** in Visual Studio. - ![ Syncfusion Troubleshooter via Syncfusion menu]( Syncfusion® Troubleshooter_images/ Syncfusion® _Menu_Troubleshooter.png) + ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) - N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2** - Right-click the Project file in Solution Explorer, then select the command ** Syncfusion® Troubleshooter…** + Right-click the Project file in Solution Explorer, then select the command **Syncfusion® Troubleshooter…** - ![ Syncfusion Troubleshooter add-in]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img1.png) + ![Syncfusion® Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.png) -2. Now, analyze the project, and if any issues are discovered, it will report the project configuration issues of Syncfusion® components in the Troubleshooter dialogue. If the project has no configuration issues, the dialogue box will indicate that no configuration changes are required in the following areas: +2. Now, analyze the project, and if any issues are discovered, it will report the project configuration issues of Syncfusion® components in the Troubleshooter dialogue. If the project has no configuration issues, the dialogue box will indicate that no configuration changes are required in the following areas: - * Syncfusion® assembly references. + * Syncfusion® assembly references. - * Syncfusion® NuGet Packages. + * Syncfusion® NuGet Packages. - * Syncfusion® Web.config Entries. + * Syncfusion® Web.config Entries. - * Syncfusion® Script files. + * Syncfusion® Script files. * Toolbox Configuration. - ![No configuration changes required dialog box]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img2.png) + ![No configuration changes required dialog box](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img2.png) - I> The Syncfusion® Troubleshooter command will be visible only for Syncfusion® projects, which means the project must contain the referred Syncfusion® assemblies or NuGet packages. + I> The Syncfusion® Troubleshooter command will be visible only for Syncfusion® projects, which means the project must contain the referred Syncfusion® assemblies or NuGet packages. - The Syncfusion® Troubleshooter handles the following project configuration issues: + The Syncfusion® Troubleshooter handles the following project configuration issues: 1. Assembly reference issues. @@ -65,134 +65,134 @@ The steps below will assist you in using the Syncfusion® Troubleshooter handles the assembly reference issues listed below in Syncfusion® Projects. +The Syncfusion® Troubleshooter handles the assembly reference issues listed below in Syncfusion® Projects. 1. Dependent assemblies are missing for referred assemblies from project. - **For Instance:** If the “ Syncfusion® .EJ.Pivot” assembly is referenced in the project but “ Syncfusion® .PivotAnalysis.Base” and other dependent assemblies of Syncfusion® .EJ.Pivot are not referenced in the project, the Syncfusion® Troubleshooter will report that the dependent assembly is missing. + **For Instance:** If the “Syncfusion.EJ.Pivot” assembly is referenced in the project but “Syncfusion.PivotAnalysis.Base” and other dependent assemblies of Syncfusion.EJ.Pivot are not referenced in the project, the Syncfusion® Troubleshooter will report that the dependent assembly is missing. - ![Dependent assemblies missing issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img3.png) + ![Dependent assemblies missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img3.png) -2. The Syncfusion® assembly version is mismatched. In the same project, compare all Syncfusion® assembly versions. If any Syncfusion® assembly version inconsistency is discovered, the Syncfusion® Troubleshooter will display the Syncfusion® assembly’s version mismatch. +2. The Syncfusion® assembly version is mismatched. In the same project, compare all Syncfusion® assembly versions. If any Syncfusion® assembly version inconsistency is discovered, the Syncfusion® Troubleshooter will display the Syncfusion® assembly’s version mismatch. - **For Instance:** If the “ Syncfusion® .OfficeChart.Base” assembly (v15.2450.0.40) is referred to in the project, but the assembly version referred to by other Syncfusion® assemblies is v15.2450.0.43. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® assembly version. + **For Instance:** If the “Syncfusion.OfficeChart.Base” assembly (v15.2450.0.40) is referred to in the project, but the assembly version referred to by other Syncfusion® assemblies is v15.2450.0.43. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® assembly version. - ![Assembly version mismatched issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img4.png) + ![Assembly version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img4.png) -3. .NET Framework version mismatch ( Syncfusion® Assemblies) with project's .NET Framework version. The details for the supported .NET Framework for Syncfusion® assemblies can be found at the following link. +3. .NET Framework version mismatch (Syncfusion® Assemblies) with project's .NET Framework version. The details for the supported .NET Framework for Syncfusion® assemblies can be found at the following link. - **For Instance:** The application's .NET Framework is v4.6, and the " Syncfusion® .EJ.PdfViewer" assembly (v16.4400.0.42 & .NET Framework version 4.0) is referred to in the same application. The Syncfusion® Troubleshooter will indicate that the Syncfusion® assembly's .NET Framework version is incompatible with the project's .NET Framework version. + **For Instance:** The application's .NET Framework is v4.6, and the "Syncfusion.EJ.PdfViewer" assembly (v16.4400.0.42 & .NET Framework version 4.0) is referred to in the same application. The Syncfusion® Troubleshooter will indicate that the Syncfusion® assembly's .NET Framework version is incompatible with the project's .NET Framework version. - ![Target Framework version of application]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img5.png) + ![Target Framework version of application](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img5.png) - ![Framework mismatch issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img6.png) + ![Framework mismatch issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img6.png) ### NuGet issues -The Syncfusion® Troubleshooter handles the following NuGet package issues in Syncfusion® projects. +The Syncfusion® Troubleshooter handles the following NuGet package issues in Syncfusion® projects. -1. Syncfusion® NuGet Packages are installed in multiple versions. If one Syncfusion® NuGet Package version differs from another, the Syncfusion® Troubleshooter will indicate that the Syncfusion® NuGet package version is mismatched. +1. Syncfusion® NuGet Packages are installed in multiple versions. If one Syncfusion® NuGet Package version differs from another, the Syncfusion® Troubleshooter will indicate that the Syncfusion® NuGet package version is mismatched. - **For Instance:** If you have multiple versions of the Syncfusion® Web platform packages installed (v16.4.0.54 and v17.1.0.38), the Syncfusion® Troubleshooter will display Syncfusion® package version mismatch. + **For Instance:** If you have multiple versions of the Syncfusion® Web platform packages installed (v16.4.0.54 and v17.1.0.38), the Syncfusion® Troubleshooter will display Syncfusion® package version mismatch. - ![ Syncfusion NuGet Packages version mismatched issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img7.png) + ![Syncfusion® NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) -2. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. +2. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. - **For Instance:** If you install the Syncfusion® Web NuGet package in your project without any dependencies, the Syncfusion® Troubleshooter will report that the Syncfusion® .Compression.Base and other dependent NuGet packages are missing. + **For Instance:** If you install the Syncfusion® Web NuGet package in your project without any dependencies, the Syncfusion® Troubleshooter will report that the Syncfusion.Compression.Base and other dependent NuGet packages are missing. - ![Dependent NuGet package missing issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img8.png) + ![Dependent NuGet package missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.png) I> To restore the missing dependent packages, an Internet connection is required. The dependent packages will not be restored if the internet is not available. ### Web.config issues -The Syncfusion® Troubleshooter handles with Web.config entry-related issues in Syncfusion® projects. +The Syncfusion® Troubleshooter handles with Web.config entry-related issues in Syncfusion® projects. -1. The version of the Syncfusion® assembly entry was mismatched. Each Syncfusion® assembly entry version/.NET Framework version will be compared to the application's corresponding referred Syncfusion® assembly. +1. The version of the Syncfusion® assembly entry was mismatched. Each Syncfusion assembly entry version/.NET Framework version will be compared to the application's corresponding referred Syncfusion® assembly. - **For Instance:** If the “ Syncfusion® .EJ.Pivot” assembly (v17.1450.0.38) is mentioned in the project, but the “ Syncfusion® .EJ.Pivot” assembly entry version (v16.4450.0.54) is mentioned in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® assembly entry version. + **For Instance:** If the “Syncfusion.EJ.Pivot” assembly (v17.1450.0.38) is mentioned in the project, but the “Syncfusion.EJ.Pivot” assembly entry version (v16.4450.0.54) is mentioned in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® assembly entry version. - ![ Syncfusion Toolbox Framework version mismatched issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img9.png) + ![Syncfusion® Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.png) -2. Syncfusion® assembly entry has multiple versions and is duplicated. When a Syncfusion® assembly entry is presented in Web.config that is not referred to in the project, or when multiple Syncfusion® assembly entries are presented in Web.config for the same Syncfusion® assembly, Syncfusion® Troubleshooter will display the duplicate assembly entry. +2. Syncfusion® assembly entry has multiple versions and is duplicated. When a Syncfusion® assembly entry is presented in Web.config that is not referred to in the project, or when multiple Syncfusion® assembly entries are presented in Web.config for the same Syncfusion® assembly, Syncfusion® Troubleshooter will display the duplicate assembly entry. - **For Instance:** If the project contains a “ Syncfusion® .EJ.Web” assembly (v17.1450.0.38) entry in the Web.config file, but the “ Syncfusion® .EJ.Web” assembly is not referred to in the project. Duplicate assembly entry will be displayed by Syncfusion® Troubleshooter. + **For Instance:** If the project contains a “Syncfusion.EJ.Web” assembly (v17.1450.0.38) entry in the Web.config file, but the “Syncfusion.EJ.Web” assembly is not referred to in the project. Duplicate assembly entry will be displayed by Syncfusion® Troubleshooter. - ![Duplicate Syncfusion reference assembly entry issue shown in Troubleshooter wizard ]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img10.png) + ![Duplicate Syncfusion® reference assembly entry issue shown in Troubleshooter wizard ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) - **For Instance:** If a project contains multiple “ Syncfusion® .EJ.Web” assembly entries (v16.4460.0.54 && v17.1460.0.38) with mismatched assembly version/.NET Framework version in Web.config, Syncfusion® Troubleshooter will display the Duplicate assembly entry and Multiple Syncfusion® assembly entries. + **For Instance:** If a project contains multiple “Syncfusion.EJ.Web” assembly entries (v16.4460.0.54 && v17.1460.0.38) with mismatched assembly version/.NET Framework version in Web.config, Syncfusion® Troubleshooter will display the Duplicate assembly entry and Multiple Syncfusion® assembly entries. - ![Multiple version Syncfusion reference assembly entry issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img11.png) + ![Multiple version Syncfusion® reference assembly entry issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) -3. The version of the namespace entry was mismatched. If any Namespace entry version (assembly version) in ASP.NET Web Application is mismatched with the corresponding referred assembly version, Syncfusion® Troubleshooter will display Namespace entry version mismatched. +3. The version of the namespace entry was mismatched. If any Namespace entry version (assembly version) in ASP.NET Web Application is mismatched with the corresponding referred assembly version, Syncfusion® Troubleshooter will display Namespace entry version mismatched. - **For Instance:** If the “ Syncfusion® .EJ” assembly (v17.1450.0.38) is referenced in the project and the “ Syncfusion® .JavaScript.DataVisualization” Namespace entry version (v16.4450.0.54) is referenced in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® namespace entry version. + **For Instance:** If the “Syncfusion.EJ” assembly (v17.1450.0.38) is referenced in the project and the “Syncfusion.JavaScript.DataVisualization” Namespace entry version (v16.4450.0.54) is referenced in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® namespace entry version. - ![Namespace entry missing issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img12.png) + ![Namespace entry missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.png) -4. Mismatch HTTP/Server handler entry. If any Syncfusion® HTTP/Server handler entry version is mismatched when compared to the corresponding referred assembly version in the project, the Syncfusion® Troubleshooter will show HTTP/Server handler entry mismatched. +4. Mismatch HTTP/Server handler entry. If any Syncfusion® HTTP/Server handler entry version is mismatched when compared to the corresponding referred assembly version in the project, the Syncfusion® Troubleshooter will show HTTP/Server handler entry mismatched. - **For Instance:** If the “ Syncfusion® .EJ.” assembly (v17.1450.0.38) is mentioned in the project, but the “ Syncfusion® .JavaScript.ImageHandler” HTTP/Server handler entry version (v16.4450.0.54) is specified in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® HTTP/Server handler entry version. + **For Instance:** If the “Syncfusion.EJ.” assembly (v17.1450.0.38) is mentioned in the project, but the “Syncfusion.JavaScript.ImageHandler” HTTP/Server handler entry version (v16.4450.0.54) is specified in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® HTTP/Server handler entry version. - ![ Syncfusion HTTP/Server handler entry mismatched issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img13.png) + ![Syncfusion® HTTP/Server handler entry mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.png) ### Toolbox Configuration Issues -The Syncfusion® Troubleshooter handles the Toolbox Configuration issues listed below in Syncfusion® projects. +The Syncfusion® Troubleshooter handles the Toolbox Configuration issues listed below in Syncfusion® projects. -1. If the project's .NET Framework version is not installed/configured, the Syncfusion® Troubleshooter will report that the Syncfusion® Toolbox .NET Framework version is mismatched. +1. If the project's .NET Framework version is not installed/configured, the Syncfusion® Troubleshooter will report that the Syncfusion® Toolbox .NET Framework version is mismatched. - **For Instance:** The .NET Framework version of the project is 4.5, and Syncfusion® Toolbox is not installed. 4.6 framework assemblies only in the corresponding Visual Studio, the Syncfusion® Troubleshooter will display Syncfusion® Toolbox framework version mismatch. + **For Instance:** The .NET Framework version of the project is 4.5, and Syncfusion® Toolbox is not installed. 4.6 framework assemblies only in the corresponding Visual Studio, the Syncfusion® Troubleshooter will display Syncfusion® Toolbox framework version mismatch. - ![ Syncfusion Toolbox Framework version mismatched issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img14.png) + ![Syncfusion® Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.png) -2. If the configured version of Syncfusion® Toolbox differs from the most recent Syncfusion® assembly reference version or NuGet package version in the same project, the Syncfusion® Troubleshooter will indicate that the Syncfusion® Toolbox version is mismatch. +2. If the configured version of Syncfusion® Toolbox differs from the most recent Syncfusion® assembly reference version or NuGet package version in the same project, the Syncfusion® Troubleshooter will indicate that the Syncfusion® Toolbox version is mismatch. - **For Instance:** If the most recent Syncfusion® assembly reference version is v17.1.0.38 but the Toolbox assemblies are configured with v17.1.0.32, the Syncfusion® Troubleshooter will report Syncfusion® Toolbox version mismatch. + **For Instance:** If the most recent Syncfusion® assembly reference version is v17.1.0.38 but the Toolbox assemblies are configured with v17.1.0.32, the Syncfusion Troubleshooter will report Syncfusion® Toolbox version mismatch. - ![ Syncfusion Toolbox version mismatched issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img15.png) + ![Syncfusion® Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.png) ### Script file issues -The Syncfusion® Troubleshooter handles the following Script file issues in Syncfusion® projects. +The Syncfusion® Troubleshooter handles the following Script file issues in Syncfusion® projects. -1. The version of the Syncfusion® script file is mismatch. Each Syncfusion® script file version will be compared to the latest version of the corresponding referred Syncfusion® assembly in the application. +1. The version of the Syncfusion® script file is mismatch. Each Syncfusion® script file version will be compared to the latest version of the corresponding referred Syncfusion® assembly in the application. - **For Instance:** If Syncfusion® assemblies (v17.1450.0.38) and Syncfusion® script file (v16.4.0.54) are referenced in the project. The Syncfusion® Troubleshooter will display a Syncfusion® script file version (v16.4.0.54) that is incompatible with the project's/package version of Syncfusion® (v17.1.0.38). + **For Instance:** If Syncfusion® assemblies (v17.1450.0.38) and Syncfusion® script file (v16.4.0.54) are referenced in the project. The Syncfusion® Troubleshooter will display a Syncfusion® script file version (v16.4.0.54) that is incompatible with the project's/package version of Syncfusion® (v17.1.0.38). - ![ Syncfusion script file version mismatched issue shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img16.png) + ![Syncfusion® script file version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img16.png) - **For Instance:** If Syncfusion® assemblies (v17.1450.0.38) are referred to in the project, but Syncfusion® script file version (v16.4.0.54) is referred to in View files when script files are referred to via a CDN link. The Syncfusion® Troubleshooter will report that the Syncfusion® script file version (v16.4.0.54) is incompatible with the project's Syncfusion® assembly/package version (v17.1.0.38) from CDN. + **For Instance:** If Syncfusion® assemblies (v17.1450.0.38) are referred to in the project, but Syncfusion® script file version (v16.4.0.54) is referred to in View files when script files are referred to via a CDN link. The Syncfusion® Troubleshooter will report that the Syncfusion® script file version (v16.4.0.54) is incompatible with the project's Syncfusion® assembly/package version (v17.1.0.38) from CDN. - ![ Syncfusion script file version mismatched issue based on CDN link shown in Troubleshooter wizard]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img17.png) + ![Syncfusion® script file version mismatched issue based on CDN link shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img17.png) -2. Syncfusion® script files that are duplicates. When a Syncfusion® script file is presented in the project location, which is referred to in View files by CDN link, or when Syncfusion® script files are presented in multiple locations in the same project, Syncfusion® Troubleshooter will display duplicate script files. +2. Syncfusion® script files that are duplicates. When a Syncfusion® script file is presented in the project location, which is referred to in View files by CDN link, or when Syncfusion® script files are presented in multiple locations in the same project, Syncfusion® Troubleshooter will display duplicate script files. - **For Instance:** If the project has a “ej.web.all.min.js” script file entry in the View file and a “ej.web.all.min.js” script file in the project location (Scripts\ej), the Syncfusion® Troubleshooter will show duplicate Syncfusion® script files presented in Scripts\ej due to this script file being referred from CDN. + **For Instance:** If the project has a “ej.web.all.min.js” script file entry in the View file and a “ej.web.all.min.js” script file in the project location (Scripts\ej), the Syncfusion® Troubleshooter will show duplicate Syncfusion® script files presented in Scripts\ej due to this script file being referred from CDN. - ![ Syncfusion script file duplicate issue by CDN with local script]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img18.png) + ![Syncfusion® script file duplicate issue by CDN with local script](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img18.png) - **For Instance:** If a project has the “ej.web.all.min.js” script file available in multiple project locations ("\Scripts\ej" and "\Scripts\"), the Syncfusion® Troubleshooter will display Duplicate Syncfusion® script files in Scripts. + **For Instance:** If a project has the “ej.web.all.min.js” script file available in multiple project locations ("\Scripts\ej" and "\Scripts\"), the Syncfusion® Troubleshooter will display Duplicate Syncfusion® script files in Scripts. - ![ Syncfusion script file duplicate issue by mulitple location ]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img19.png) + ![Syncfusion® script file duplicate issue by mulitple location ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img19.png) ## Apply the solution -1. Check the corresponding check box of the issue to be resolved after loading the Syncfusion® Troubleshooter dialog. Then, check “Fix Issue(s)” button. +1. Check the corresponding check box of the issue to be resolved after loading the Syncfusion® Troubleshooter dialog. Then, check “Fix Issue(s)” button. - ![ Syncfusion Troubleshooter wizard with project configuration issues]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img20.png) + ![Syncfusion® Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img20.png) 2. A dialog appears, prompting you to create a backup of the project before proceeding with the troubleshooting process. Click the "Yes" button if you need to backup the project before troubleshooting. - ![ Syncfusion Troubleshooter backup dialog]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img21.jpeg) + ![Syncfusion® Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img21.jpeg) -3. Wait a moment while the Syncfusion® Troubleshooter resolves the issues you selected. When the troubleshooting process is finished, a message will appear in the Visual Studio status bar that says, "Troubleshooting process completed successfully." +3. Wait a moment while the Syncfusion® Troubleshooter resolves the issues you selected. When the troubleshooting process is finished, a message will appear in the Visual Studio status bar that says, "Troubleshooting process completed successfully." - ![ Syncfusion Troubleshooter process success status message in visual studio status bar]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img22.jpeg) + ![Syncfusion® Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img22.jpeg) -4. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +4. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![ Syncfusion license registration required information dialog in Syncfusion Troubleshooter]( Syncfusion® Troubleshooter_images/ Syncfusion® Troubleshooter-img23.jpeg) \ No newline at end of file + ![Syncfusion® license registration required information dialog in Syncfusion® Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img23.jpeg) \ No newline at end of file diff --git a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md index 8296b79f..9eb4e55d 100644 --- a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md +++ b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md @@ -3,15 +3,15 @@ layout: post title: Command Line installation | Extension | Syncfusion description: command line installation platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Command Line installation -The following steps help you install the Syncfusion® Web Sample Creator setup through Command Line in Silent mode. +The following steps help you install the Syncfusion® Web Sample Creator setup through Command Line in Silent mode. -1. Double-click the Syncfusion Web Sample Creator Setup file. The Self-Extractor Wizard opens and extracts the package automatically. +1. Double-click the Syncfusion® Web Sample Creator Setup file. The Self-Extractor Wizard opens and extracts the package automatically. 2. The syncfusionwebsamplecreator.exe file is extracted into the Temp folder. 3. Run `%temp%`. The Temp folder opens. The `syncfusionwebsamplecreator.exe` file is available in one of the folders. 4. Copy the syncfusionwebsamplecreator.exe file to the local drive. Example: D:\temp @@ -24,6 +24,6 @@ The following steps help you install the Syncfusion&r Refer to the following screenshot for more information. - ![Command line arguments to install Syncfusion® web sample creator from command prompt](Command-Line-installation_images/Command-Line-installation-img1.png) + ![Command line arguments to install Syncfusion® web sample creator from command prompt](Command-Line-installation_images/Command-Line-installation-img1.png) I> The syncfusionessentialextension.exe setup has renamed to syncfusionwebsamplecreator.exe from 2015 Volume 4 release. \ No newline at end of file diff --git a/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md b/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md index e6fa4dcd..60f50cf3 100644 --- a/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md +++ b/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md @@ -1,29 +1,29 @@ --- layout: post title: Download ASPNET MVC Extension | Extension | Syncfusion -description: Learn here about download asp.net mvc extension in Syncfusion Essential ASP.NET MVC Extension Control, its elements, and more. +description: Learn here about download asp.net mvc extension in Syncfusion Essential ASP.NET MVC Extension Control, its elements, and more. platform: extension -control: Syncfusion® Extensions +control: Syncfusion Extensions documentation: ug --- -# Download Syncfusion® Web Sample Creator +# Download Syncfusion® Web Sample Creator -1. Download the latest Syncfusion® Web Sample Creator setup from the following location: [https://www.syncfusion.com/downloads/extension](https://www.syncfusion.com/downloads/extension) +1. Download the latest Syncfusion® Web Sample Creator setup from the following location: [https://www.syncfusion.com/downloads/extension](https://www.syncfusion.com/downloads/extension) Refer the following screenshot for more information. - ![Download link for Syncfusion® Essential Studio® Web Sample Creator](Download-ASPNET-MVC-Extension_images/Download-ASPNET-MVC-Extension-img1.jpeg) + ![Download link for Syncfusion® Essential Studio® Web Sample Creator](Download-ASPNET-MVC-Extension_images/Download-ASPNET-MVC-Extension-img1.jpeg) - I> It is a prerequisite to have the complete Essential Studio® suite or ASP.NET MVC or ASP.NET MVC (Classic) installed while using Syncfusion® ASP.NET MVC Extension. This is applicable from v.12.1.0.43. + I> It is a prerequisite to have the complete Essential Studio® suite or ASP.NET MVC or ASP.NET MVC (Classic) installed while using Syncfusion® ASP.NET MVC Extension. This is applicable from v.12.1.0.43. -2. You can download the corresponding syncfusionwebsamplecreator.exe Version directly from the Syncfusion® Dashboard. After installing the complete Essential Studio® suite or ASP.NET MVC or ASP.NET MVC (Classic) setup, follow the given steps: +2. You can download the corresponding syncfusionwebsamplecreator.exe Version directly from the Syncfusion® Dashboard. After installing the complete Essential Studio® suite or ASP.NET MVC or ASP.NET MVC (Classic) setup, follow the given steps: - * Launch the Syncfusion® Dashboard + * Launch the Syncfusion® Dashboard * Navigate to the “ASP.NET MVC” tab available on the left side. - * Click the “SAMPLE CREATOR” button. It downloads the corresponding version of Syncfusion® Web Sample Creator setup. When you have already installed the Syncfusion® Web Sample Creator setup then it will launch the “Sample Creator” utility instead of downloading. + * Click the “SAMPLE CREATOR” button. It downloads the corresponding version of Syncfusion® Web Sample Creator setup. When you have already installed the Syncfusion® Web Sample Creator setup then it will launch the “Sample Creator” utility instead of downloading. - ![Syncfusion Essential studio control panel to launch the Sample Creator](Download-ASPNET-MVC-Extension_images/Download-ASPNET-MVC-Extension-img2.jpeg) + ![Syncfusion® Essential studio® control panel to launch the Sample Creator](Download-ASPNET-MVC-Extension_images/Download-ASPNET-MVC-Extension-img2.jpeg) I> The syncfusionessentialextension.exe setup has renamed to syncfusionwebsamplecreator.exe from 2015 Volume 4 release. diff --git a/Extension/ASPNET-MVC-Extension/Overview.md b/Extension/ASPNET-MVC-Extension/Overview.md index 05e07de8..20d63d2c 100644 --- a/Extension/ASPNET-MVC-Extension/Overview.md +++ b/Extension/ASPNET-MVC-Extension/Overview.md @@ -1,39 +1,39 @@ --- layout: post title: ASP.NET MVC (Essential JS 1) Extension | Extension | Syncfusion -description: An Extension provides you with quick access so that you can create or configure the Syncfusion ASP.NET MVC projects along with Essential JS 1 components +description: An Extension provides you with quick access so that you can create or configure the Syncfusion ASP.NET MVC projects along with Essential JS 1 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # ASPNET MVC Extension -The Syncfusion® ASP.NET MVC (Essential® JS 1) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® MVC Extension supports Microsoft Visual Studio 2010 or higher. +The Syncfusion® ASP.NET MVC (Essential® JS 1) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® MVC Extension supports Microsoft Visual Studio 2010 or higher. -I> The Syncfusion® ASP.NET MVC (Essential® JS 1) menu option is available from v17.1.0.32. +I> The Syncfusion® ASP.NET MVC (Essential® JS 1) menu option is available from v17.1.0.32. -The Syncfusion® provides the following extension supports in Visual Studio: +The Syncfusion® provides the following extension supports in Visual Studio: -1. [Syncfusion ASP.NET MVC (Essential® JS 1) Project Template](https://help.syncfusion.com/extension/aspnet-mvc-extension/syncfusion-project-templates): To create the Syncfusion® ASP.NET MVC (Essential JS 1) or ASP.NET MVC (Classic) application by adding the required Essential JS 1 components. -2. [Project Conversion](https://help.syncfusion.com/extension/aspnet-mvc-extension/project-conversion): To convert an existing ASP.NET MVC application into a Syncfusion® ASP.NET MVC (Essential JS 1) or ASP.NET MVC (Classic) application by adding the required Syncfusion® assemblies and resource files. -3. [Migrate Project](https://help.syncfusion.com/extension/aspnet-mvc-extension/project-migration): Migrate the existing Syncfusion® ASP.NET MVC or ASP.NET MVC (Classic) application from one Essential Studio® version to another version. -4. [Sample Creator](https://help.syncfusion.com/extension/aspnet-mvc-extension/sample-creator): Create the Syncfusion® ASP.NET MVC (Essential JS 1) or ASP.NET MVC (Classic) Projects with the required Syncfusion® configuration to start development with the required Syncfusion® controls. -5. [Troubleshooter](https://help.syncfusion.com/extension/syncfusion-troubleshooter/syncfusion-troubleshooter): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. +1. [Syncfusion® ASP.NET MVC (Essential® JS 1) Project Template](https://help.syncfusion.com/extension/aspnet-mvc-extension/syncfusion-project-templates): To create the Syncfusion® ASP.NET MVC (Essential® JS 1) or ASP.NET MVC (Classic) application by adding the required Essential® JS 1 components. +2. [Project Conversion](https://help.syncfusion.com/extension/aspnet-mvc-extension/project-conversion): To convert an existing ASP.NET MVC application into a Syncfusion® ASP.NET MVC (Essential® JS 1) or ASP.NET MVC (Classic) application by adding the required Syncfusion® assemblies and resource files. +3. [Migrate Project](https://help.syncfusion.com/extension/aspnet-mvc-extension/project-migration): Migrate the existing Syncfusion® ASP.NET MVC or ASP.NET MVC (Classic) application from one Essential Studio® version to another version. +4. [Sample Creator](https://help.syncfusion.com/extension/aspnet-mvc-extension/sample-creator): Create the Syncfusion® ASP.NET MVC (Essential® JS 1) or ASP.NET MVC (Classic) Projects with the required Syncfusion® configuration to start development with the required Syncfusion® controls. +5. [Troubleshooter](https://help.syncfusion.com/extension/syncfusion-troubleshooter/syncfusion-troubleshooter): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. **No project selected in Visual Studio** -![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Microsoft ASP.NET MVC application in Visual Studio** -![Syncfusion Menu when Selected Microsoft ASP.NET MVC application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) +![Syncfusion® Menu when Selected Microsoft ASP.NET MVC application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) -**Selected Syncfusion® ASP.NET MVC (Essential JS1) application in Visual Studio** +**Selected Syncfusion® ASP.NET MVC (Essential® JS1) application in Visual Studio** -![Syncfusion Menu when Selected Synfusion ASP.NET MVC EJ1 application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) +![Syncfusion® Menu when Selected Synfusion ASP.NET MVC EJ1 application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) -N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. +N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. diff --git a/Extension/ASPNET-MVC-Extension/Project-Conversion.md b/Extension/ASPNET-MVC-Extension/Project-Conversion.md index 94d36766..75b1d3af 100644 --- a/Extension/ASPNET-MVC-Extension/Project-Conversion.md +++ b/Extension/ASPNET-MVC-Extension/Project-Conversion.md @@ -1,27 +1,27 @@ --- layout: post title: Project Conversion | ASP.NET MVC (Essential JS 1) | Syncfusion -description: Project Conversion is a add-in that converts an existing ASP.NET MVC Project into a Syncfusion ASP.NET MVC Project by adding required Essential JS 1 components +description: Project Conversion is a add-in that converts an existing ASP.NET MVC Project into a Syncfusion ASP.NET MVC Project by adding required Essential JS 1 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # ASP.NET MVC Project Conversion -Project Conversion is a Visual Studio add-in that converts an existing ASP.NET MVC Project into a Syncfusion® ASP.NET MVC Project by adding the required assemblies and resource files. +Project Conversion is a Visual Studio add-in that converts an existing ASP.NET MVC Project into a Syncfusion® ASP.NET MVC Project by adding the required assemblies and resource files. -Syncfusion ASP.NET MVC and ASP.NET MVC (Classic) Project Conversion Utility is included here, +Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) Project Conversion Utility is included here, -* Essential Studio® for Enterprise Edition with the platforms ASP.NETMVC or ASP.NET MVC(Classic) -* Essential Studio® for ASP.NET MVC -* Essential Studio® for ASP.NET MVC (Classic) +* Essential Studio® for Enterprise Edition with the platforms ASP.NETMVC or ASP.NET MVC(Classic) +* Essential Studio® for ASP.NET MVC +* Essential Studio® for ASP.NET MVC (Classic) -I> The Project conversion Visual Studio add-in is available from the v11.1.0.21 and this is not applicable from v.12.1.0.43 to v.13.1.0.30. The Syncfusion® ASP.NET MVC (Web) and ASP.NET MVC (Classic) Project Conversion Utilities are excluded from the MVC Extension setup and integrated into Essential Studio® ASP.NET MVC and ASP.NET MVC (Classic) platforms. +I> The Project conversion Visual Studio add-in is available from the v11.1.0.21 and this is not applicable from v.12.1.0.43 to v.13.1.0.30. The Syncfusion® ASP.NET MVC (Web) and ASP.NET MVC (Classic) Project Conversion Utilities are excluded from the MVC Extension setup and integrated into Essential Studio® ASP.NET MVC and ASP.NET MVC (Classic) platforms. ## ASP.NET MVC (Classic) Conversion\Migration: -By default, the Syncfusion® ASP.NET MVC Extensions are configured in Visual Studio. When you want the ASP.NET MVC (Classic) extension, you can install it from the installed location. +By default, the Syncfusion® ASP.NET MVC Extensions are configured in Visual Studio. When you want the ASP.NET MVC (Classic) extension, you can install it from the installed location. ### Project Conversion and Migration (ASP.NET MVC(Classic): @@ -29,31 +29,31 @@ Location : `{Drive}\Program Files (x86)\Syncfusion\Essential Studio\\U For Example - VS2013 : `C:\Program Files (x86)\Syncfusion\Essential Studio\13.2.0.18\Utilities\Extensions\ASP.NET MVC\Project Conversion\4.5.1\Syncfusion Web (Classic) Conversion and Migration.vsix` -## Convert into Syncfusion® MVC (Web) project +## Convert into Syncfusion® MVC (Web) project -The following steps help you use the Syncfusion® Project Conversion in the existing ASP.NET MVC (Web) Project. +The following steps help you use the Syncfusion® Project Conversion in the existing ASP.NET MVC (Web) Project. -> Before use, the Syncfusion® ASP.NET MVC (Essential JS 1) Project Conversion, check whether the **Syncfusion Essential JS1 AspNet MVC VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. +> Before use, the Syncfusion® ASP.NET MVC (Essential® JS 1) Project Conversion, check whether the **Syncfusion® Essential® JS1 AspNet MVC VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. 1. Open an existing Microsoft MVC Project or create a new Microsoft MVC Project. 2. To open Project Conversion Wizard, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET MVC (EJ1) > Convert to Syncfusion® ASP.NET MVC Application…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Convert to Syncfusion® ASP.NET MVC Application…** in **Visual Studio**. - ![Syncfusion Essential JS 1 ASP.NET MVC Web Project Conversion via Synfusion menu](Convert-into-Syncfusion-MVC-project_images/Syncfusion_Menu_Project_Conversion.png) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project Conversion via Synfusion® menu](Convert-into-Syncfusion-MVC-project_images/Syncfusion_Menu_Project_Conversion.png) - N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Right-click the Project from Solution Explorer, select **Syncfusion Essential JS 1**, and choose **Convert to Syncfusion® MVC (Essential JS 1) Application...** Refer to the following screenshot for more information. + Right-click the Project from Solution Explorer, select **Syncfusion® Essential® JS 1**, and choose **Convert to Syncfusion® MVC (Essential® JS 1) Application...** Refer to the following screenshot for more information. - ![Syncfusion Essential JS 1 ASP.NET MVC Web Project Conversion add-in](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img1.png) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project Conversion add-in](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img1.png) 3. Project Conversion Wizard opens so that you can configure the project. - ![Syncfusion Essential JS 1 ASP.NET MVC Web Project Conversion wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img2.jpg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project Conversion wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img2.jpg) The following configurations are used in the Project Conversion Wizard. @@ -62,22 +62,22 @@ The following steps help you use the Syncfusion®< Choose the assembly location: 1. Added From GAC - Refer the assemblies from the Global Assembly Cache - 2. Added from Installed Location - Refer the assemblies from the Syncfusion® Installed locations. + 2. Added from Installed Location - Refer the assemblies from the Syncfusion® Installed locations. 3. Add Referenced Assemblies to Solution - Copy and refer to the assemblies from project's solution file lib directory. ![Choose the assembly location from where assemblies to be referred to the ASP.NET MVC project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img3.jpeg) **Choose the Theme:** - The master page of project will be updated based on selected theme. The Theme Preview section shows the controls preview before convert into a Syncfusion® project. + The master page of project will be updated based on selected theme. The Theme Preview section shows the controls preview before convert into a Syncfusion® project. ![Choose the theme to apply on the master page of the ASP.NET MVC project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img4.jpeg) **Choose CDN Support:** - The master page of the project will be updated based on required Syncfusion® CDN links. + The master page of the project will be updated based on required Syncfusion® CDN links. - ![Choose CDN Support to refer the Syncfusion® assets from CDN for ASP.NET MVC project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img20.jpeg) + ![Choose CDN Support to refer the Syncfusion® assets from CDN for ASP.NET MVC project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img20.jpeg) **Choose Copy Global Resources:** @@ -85,38 +85,38 @@ The following steps help you use the Syncfusion®< ![Choose Copy Global Resources to ship the localization culture files for ASP.NET MVC project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img21.jpeg) -4. Choose the required controls from Components section and Click the **Convert** button to convert it into a Syncfusion® Project. +4. Choose the required controls from Components section and Click the **Convert** button to convert it into a Syncfusion Project. - ![Select the required components from the Components section in the Syncfusion® ASP.NET MVC Project Conversion Wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img5.jpg) + ![Select the required components from the Components section in the Syncfusion® ASP.NET MVC Project Conversion Wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img5.jpg) -5. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before converting it to Syncfusion® project. If click No it will convert the project to Syncfusion® project without backup. +5. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before converting it to Syncfusion® project. If click No it will convert the project to Syncfusion® project without backup. - ![Syncfusion Essential JS 1 ASP.NET MVC Web Project Conversion backup dialog](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img6.jpg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project Conversion backup dialog](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img6.jpg) -6. The required Syncfusion® Reference Assemblies, Scripts and CSS are included in the MVC Project. Refer to the following screenshots for more information. +6. The required Syncfusion® Reference Assemblies, Scripts and CSS are included in the MVC Project. Refer to the following screenshots for more information. - ![Syncfusion Essential JS 1 ASP.NET MVC scripts and themes](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img7.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC scripts and themes](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img7.jpeg) - ![Syncfusion Essential JS 1 ASP.NET MVC required reference assemblies](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img8.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC required reference assemblies](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img8.jpeg) - ![Syncfusion Essential JS 1 ASP.NET MVC Web.config entries](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img9.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Web.config entries](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img9.jpeg) -6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. +6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. -## Convert into Syncfusion® MVC (Mobile) project +## Convert into Syncfusion® MVC (Mobile) project -The following steps help you use the Syncfusion® Project Conversion in the existing ASP.NET MVC Project. +The following steps help you use the Syncfusion® Project Conversion in the existing ASP.NET MVC Project. 1. Open an existing Microsoft MVC Project or create a new Microsoft MVC Project. -2. Right-click on Project and select Syncfusion® VS Extensions and choose the Convert to Syncfusion® MVC (Web) Application. Refer the following screenshot for more information. +2. Right-click on Project and select Syncfusion® VS Extensions and choose the Convert to Syncfusion® MVC (Web) Application. Refer the following screenshot for more information. - ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project Conversion add-in](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img10.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project Conversion add-in](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img10.jpeg) 3. Project Conversion Wizard opens so that you can configure the project. - ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project Conversion wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img11.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project Conversion wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img11.jpeg) The following configurations are used in the Project Conversion Wizard. @@ -125,7 +125,7 @@ The following steps help you use the Syncfusion®< Choose the assembly location: 1. Added From GAC - Refer the assemblies from the Global Assembly Cache - 2. Added from Installed Location - Refer the assemblies from the Syncfusion® Installed locations. + 2. Added from Installed Location - Refer the assemblies from the Syncfusion® Installed locations. 3. Add Referenced Assemblies to Solution - Copy and refer to the assemblies from project's solution file lib directory. ![Choose the assembly location from where assemblies to be referred to the ASP.NET MVC Mobile project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img3.jpeg) @@ -138,9 +138,9 @@ The following steps help you use the Syncfusion®< **Choose CDN Support:** - The master page of the project will be updated based on required Syncfusion® CDN links. + The master page of the project will be updated based on required Syncfusion® CDN links. - ![Choose CDN Support to refer the Syncfusion® assets from CDN for ASP.NET MVC Mobile project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img20.jpeg) + ![Choose CDN Support to refer the Syncfusion® assets from CDN for ASP.NET MVC Mobile project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img20.jpeg) **Choose Copy Global Resources:** @@ -148,32 +148,32 @@ The following steps help you use the Syncfusion®< ![Choose Copy Global Resources to ship the localization culture files for ASP.NET MVC Mobile project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img21.jpeg) -4. Click the Convert button to convert it into a Syncfusion® Project. +4. Click the Convert button to convert it into a Syncfusion® Project. -5. The required Syncfusion® Reference Assemblies, Scripts and CSS are included in the MVC Project. Refer to the following screenshots for more information. +5. The required Syncfusion® Reference Assemblies, Scripts and CSS are included in the MVC Project. Refer to the following screenshots for more information. - ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project required reference assemblies](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img13.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project required reference assemblies](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img13.jpeg) - ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project required scripts](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img14.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project required scripts](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img14.jpeg) - ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project required themes](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img15.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project required themes](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img15.jpeg) - ![Syncfusion assembly reference entry in Webconfig file of the Essential JS 1 ASP.NET MVC Mobile Project](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img16.jpeg) + ![Syncfusion® assembly reference entry in Webconfig file of the Essential® JS 1 ASP.NET MVC Mobile Project](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img16.jpeg) -## Rendering Control after Syncfusion® MVC (Web/Mobile) Conversion: +## Rendering Control after Syncfusion® MVC (Web/Mobile) Conversion: -Once you convert your ASP.NET MVC project to Syncfusion® MVC Project, perform the following steps to render the Syncfusion Controls to your project.                -1. The CSS, Scripts, Syncfusion® References and required Web.config file entries are added to your project by Syncfusion® ASP.NET MVC Conversion.   +Once you convert your ASP.NET MVC project to Syncfusion® MVC Project, perform the following steps to render the Syncfusion® Controls to your project.                +1. The CSS, Scripts, Syncfusion® References and required Web.config file entries are added to your project by Syncfusion® ASP.NET MVC Conversion.   2. Add the required Script and CSS files references in the master page (_Layout.cshtml/Layout.vbhtml file). Please refer to below screenshot for more information. ![Required Script and CSS files references in the master page _Layout.cshtml or Layout.vbhtml file](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img17.jpeg) -3. Now, include the Syncfusion controls to your project. Refer to the following screenshot for more information. +3. Now, include the Syncfusion® controls to your project. Refer to the following screenshot for more information. - ![Syncfusion Essential JS 1 ASP.NET MVC datepicker control snippet](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img18.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC datepicker control snippet](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img18.jpeg) 4. Run the project and the following output is displayed. - ![Syncfusion Essential JS 1 ASP.NET MVC datepicker control output](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img19.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC datepicker control output](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img19.jpeg) diff --git a/Extension/ASPNET-MVC-Extension/Project-Migration.md b/Extension/ASPNET-MVC-Extension/Project-Migration.md index de0440ce..2399ba3c 100644 --- a/Extension/ASPNET-MVC-Extension/Project-Migration.md +++ b/Extension/ASPNET-MVC-Extension/Project-Migration.md @@ -1,27 +1,27 @@ --- layout: post title: Project Migration | ASP.NET MVC (Essential JS 1) | Syncfusion -description: Project Migration is a add-in that helps migrate existing Syncfusion Essential JS 1 ASP.NET MVC project from one Syncfusion version to another version +description: Project Migration is a add-in that helps migrate existing Syncfusion Essential JS 1 ASP.NET MVC project from one Syncfusion version to another version platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # ASP.NET MVC Project Migration -Project Migration is a Visual Studio add-in that helps migrate the existing Syncfusion® ASP.NET MVC (Web), Syncfusion® ASP.NET MVC (Mobile) Or Syncfusion® ASP.NET MVC (Classic) project from one Syncfusion® version to another Syncfusion® version. +Project Migration is a Visual Studio add-in that helps migrate the existing Syncfusion® ASP.NET MVC (Web), Syncfusion® ASP.NET MVC (Mobile) Or Syncfusion® ASP.NET MVC (Classic) project from one Syncfusion® version to another Syncfusion® version. -Syncfusion ASP.NET MVC and ASP.NET MVC (Classic) Project Migration Utility is included here, +Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) Project Migration Utility is included here, -* Essential Studio® for Enterprise Edition with the platforms ASP.NET MVC or ASP.NET MVC(Classic) -* Essential Studio® for ASP.NET MVC -* Essential Studio® for ASP.NET MVC (Classic) +* Essential Studio® for Enterprise Edition with the platforms ASP.NET MVC or ASP.NET MVC(Classic) +* Essential Studio® for ASP.NET MVC +* Essential Studio® for ASP.NET MVC (Classic) -I> This is not applicable from v.12.1.0.43 to v.13.1.0.30. The Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) Project Migration Utilities are excluded from MVC Extension setup and integrated into Essential Studio® ASP.NET MVC and ASP.NET MVC (Classic) platforms. +I> This is not applicable from v.12.1.0.43 to v.13.1.0.30. The Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) Project Migration Utilities are excluded from MVC Extension setup and integrated into Essential Studio® ASP.NET MVC and ASP.NET MVC (Classic) platforms. ## ASP.NET MVC (Classic) Conversion\Migration: -By default, the Syncfusion® ASP.NET MVC Extensions are configured in Visual Studio. When you want the ASP.NET MVC (Classic) extension, you can install it from the installed location. +By default, the Syncfusion® ASP.NET MVC Extensions are configured in Visual Studio. When you want the ASP.NET MVC (Classic) extension, you can install it from the installed location. Project Conversion and Migration (ASP.NET MVC(Classic): @@ -29,44 +29,44 @@ Location: `{Drive}\Program Files (x86)\Syncfusion\Essential Studio\\Ut For Example - VS2013: `C:\Program Files (x86)\Syncfusion\Essential Studio\13.2.0.18\Utilities\Extensions\ASP.NET MVC\Project Conversion\4.5.1\Syncfusion Web (Classic) Conversion and Migration.vsix` -## Migrate Syncfusion® MVC Project +## Migrate Syncfusion® MVC Project -The following steps help you migrate from one version to another version of your existing Syncfusion® ASP.NET MVC application. +The following steps help you migrate from one version to another version of your existing Syncfusion® ASP.NET MVC application. -> Before use, the Syncfusion® ASP.NET MVC (Essential JS 1) Project Migration, check whether the **Syncfusion® Essential® JS1 AspNet MVC VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. +> Before use, the Syncfusion® ASP.NET MVC (Essential® JS 1) Project Migration, check whether the **Syncfusion® Essential® JS1 AspNet MVC VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. 1. To open Migration Wizard, follow either one of the options below: **Option 1:** - Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Migrate Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Migrate Project…** in **Visual Studio**. - ![Syncfusion Essential JS 1 ASP.NET MVC Project Migration via Syncfusion menu](Migrate-Syncfusion-Project_images/SyncfusionMenu_ProjectMigration_img.png) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Project Migration via Syncfusion® menu](Migrate-Syncfusion-Project_images/SyncfusionMenu_ProjectMigration_img.png) - N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Right-click the **Syncfusion® ASP.NET MVC Application** from Solution Explorer and select **Syncfusion® Essential® JS 1**. Choose **Migrate the Essential® JS 1 Project to Another Version...** + Right-click the **Syncfusion® ASP.NET MVC Application** from Solution Explorer and select **Syncfusion® Essential® JS 1**. Choose **Migrate the Essential® JS 1 Project to Another Version...** - ![Syncfusion Essential JS 1 ASP.NET MVC Project Migration add-in](Migrate-Syncfusion-Project_images/ProjectMigration_img.png) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Project Migration add-in](Migrate-Syncfusion-Project_images/ProjectMigration_img.png) -2. The Project Migration window appears. You can choose the required Syncfusion® version that is installed in the machine that is either Syncfusion® ASP.NET MVC or Syncfusion® ASP.NET MVC (Classic). +2. The Project Migration window appears. You can choose the required Syncfusion® version that is installed in the machine that is either Syncfusion® ASP.NET MVC or Syncfusion® ASP.NET MVC (Classic). - ![Syncfusion Essential JS 1 ASP.NET MVC Project Migration wizard](Migrate-Syncfusion-Project_images/ProjectMigration-img2.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Project Migration wizard](Migrate-Syncfusion-Project_images/ProjectMigration-img2.jpeg) 3. The Project Migration window allows you to configure the following options: - * Essential Studio® Version: Select any version from the list of Installed Versions. + * Essential Studio® Version: Select any version from the list of Installed Versions. * Assemblies From: The option Assemblies from add the assembly to project from the following locations. 1. Added From GAC - Refer the assemblies from the Global Assembly Cache - 2. Added from Installed Location - Refer the assemblies from the Syncfusion® Installed locations. + 2. Added from Installed Location - Refer the assemblies from the Syncfusion® Installed locations. 3. Add Referenced Assemblies to Solution - Copy and refer to the assemblies from project's solution file lib directory. -4. Click the Migrate Button. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before migrate the Syncfusion® project. If click No it will migrate the project to required Syncfusion® version without backup. +4. Click the Migrate Button. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before migrate the Syncfusion® project. If click No it will migrate the project to required Syncfusion® version without backup. - ![Syncfusion Essential JS 1 ASP.NET MVC Project Migration backup dialog](Migrate-Syncfusion-Project_images/ProjectMigration-img3.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Project Migration backup dialog](Migrate-Syncfusion-Project_images/ProjectMigration-img3.jpeg) -5. The Syncfusion® Reference Assemblies, Scripts and CSS are updated to the corresponding version in the project. +5. The Syncfusion® Reference Assemblies, Scripts and CSS are updated to the corresponding version in the project. -6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. \ No newline at end of file +6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNET-MVC-Extension/Sample-Creator.md b/Extension/ASPNET-MVC-Extension/Sample-Creator.md index 05962444..79dd62bf 100644 --- a/Extension/ASPNET-MVC-Extension/Sample-Creator.md +++ b/Extension/ASPNET-MVC-Extension/Sample-Creator.md @@ -1,49 +1,49 @@ --- layout: post title: Sample Creator | ASP.NET MVC (Essential JS 1) | Syncfusion -description: Sample Creator is the utility that allows you to create Syncfusion ASP.NET MVC Projects along with the samples based on Controls and Features selection +description: Sample Creator is the utility that allows you to create Syncfusion ASP.NET MVC Projects along with the samples based on Controls and Features selection platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Sample Creator in ASP.NET MVC Extensions -Sample Creator is the utility that allows you to create Syncfusion® ASP.NET MVC/Syncfusion ASP.NET MVC (Classic) Projects along with the samples based on Controls and Features selection. +Sample Creator is the utility that allows you to create Syncfusion® ASP.NET MVC/Syncfusion® ASP.NET MVC (Classic) Projects along with the samples based on Controls and Features selection. -## Create Syncfusion® MVC Project from Sample Creator +## Create Syncfusion® MVC Project from Sample Creator -The following steps help you to create the Syncfusion® ASP.NET MVC Project via the Sample Creator utility. +The following steps help you to create the Syncfusion® ASP.NET MVC Project via the Sample Creator utility. -1. To launch ASP.NET MVC (Essential® JS 1) Sample Creator application, follow either one of the options below: +1. To launch ASP.NET MVC (Essential® JS 1) Sample Creator application, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET MVC (EJ1) > Launch Sample Creator…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Launch Sample Creator…** in **Visual Studio**. - ![launch the Essential JS 1 ASP.NET MVC Sample Creator via Syncfusion® menu](Sample-Creator_images/Syncfusion_Menu_SampleCreator.png) + ![launch the Essential® JS 1 ASP.NET MVC Sample Creator via Syncfusion® menu](Sample-Creator_images/Syncfusion_Menu_SampleCreator.png) - N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Launch the Syncfusion® Essential Studio® Dashboard and select the ASP.NET MVC (Essential JS 1)/ASP.NET MVC (Classic) platform. Select the Sample Creator button to launch the ASP.NET MVC (Essential JS 1) Sample Creator application. Refer to the following screenshot for more information. + Launch the Syncfusion® Essential Studio® Dashboard and select the ASP.NET MVC (Essential® JS 1)/ASP.NET MVC (Classic) platform. Select the Sample Creator button to launch the ASP.NET MVC (Essential® JS 1) Sample Creator application. Refer to the following screenshot for more information. - ![Syncfusion Essential Studio® control panel to launch the Essential JS 1 ASP.NET MVC Sample Creator](Sample-Creator_images/Sample-Creator-img1.png) + ![Syncfusion® Essential Studio® control panel to launch the Essential® JS 1 ASP.NET MVC Sample Creator](Sample-Creator_images/Sample-Creator-img1.png) -2. Syncfusion® Sample Creator Wizard displaying the **Controls and its Feature Selection** section. +2. Syncfusion® Sample Creator Wizard displaying the **Controls and its Feature Selection** section. - ![Syncfusion Essential JS 1 ASP.NET MVC Sample Creator Wizard](Sample-Creator_images/Sample-Creator-img2.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator Wizard](Sample-Creator_images/Sample-Creator-img2.jpeg) ### Controls Selection - Listed here are the Syncfusion® ASP.NET MVC controls so you can choose the required controls. And the controls are grouped product wise. + Listed here are the Syncfusion® ASP.NET MVC controls so you can choose the required controls. And the controls are grouped product wise. - ![Syncfusion Essential JS 1 ASP.NET MVC Sample Creator Controls Selection](Sample-Creator_images/Sample-Creator-img3.png) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator Controls Selection](Sample-Creator_images/Sample-Creator-img3.png) ### Feature Selection Based on the controls, the Feature is enabled to choose the features of the corresponding controls. -![Syncfusion Essential JS 1 ASP.NET MVC Sample Creator Feature Selection](Sample-Creator_images/Sample-Creator-img4.png) +![Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator Feature Selection](Sample-Creator_images/Sample-Creator-img4.png) ### Project Configuration @@ -53,33 +53,33 @@ You can configure the following project details in the Sample Creator. * Language – Select the language, either C# or VB. * VS Version – Choose the Project version * .NET Framework – Choose the .NET Framework version. -* View Engine – Select either Razor or ASPX. By default, Syncfusion® supports only Razor view engine for ASP.NET MVC projects. +* View Engine – Select either Razor or ASPX. By default, Syncfusion® supports only Razor view engine for ASP.NET MVC projects. * Compress Style Sheets – Option to compress style sheets. * Compress Scripts – Option to compress the scripts. -* Name – Name your Syncfusion® MVC Application. +* Name – Name your Syncfusion® MVC Application. * Location – Choose the target location of your project. -* Theme Selection – Choose the required theme. The Theme Preview section shows the controls preview before create the Syncfusion® project. +* Theme Selection – Choose the required theme. The Theme Preview section shows the controls preview before create the Syncfusion® project. -![Syncfusion Essential JS 1 ASP.NET MVC Sample Creator Project Configuration section](Sample-Creator_images/Sample-Creator-img6.jpeg) +![Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator Project Configuration section](Sample-Creator_images/Sample-Creator-img6.jpeg) -When you click the Create button, the new Syncfusion® ASP.NET MVC project is created. The following is added in the project: +When you click the Create button, the new Syncfusion® ASP.NET MVC project is created. The following is added in the project: * Added the required Controller and View files in the project. ![Required Controller and View files added in the project for selected controls](Sample-Creator_images/Sample-Creator-img7.png) -* Included the required Syncfusion® ASP.NET MVC scripts and themes files. +* Included the required Syncfusion® ASP.NET MVC scripts and themes files. - ![Required Syncfusion ASP.NET MVC scripts and themes files added in the project](Sample-Creator_images/Sample-Creator-img8.png) + ![Required Syncfusion® ASP.NET MVC scripts and themes files added in the project](Sample-Creator_images/Sample-Creator-img8.png) -* The required Syncfusion® assemblies are added for selected controls under Project Reference. +* The required Syncfusion® assemblies are added for selected controls under Project Reference. - ![Required Syncfusion assemblies added in the project for the selected controls](Sample-Creator_images/Sample-Creator-img9.png) + ![Required Syncfusion® assemblies added in the project for the selected controls](Sample-Creator_images/Sample-Creator-img9.png) -* Configure the Web.Config file by adding the Syncfusion® reference assemblies. +* Configure the Web.Config file by adding the Syncfusion® reference assemblies. - ![Required Syncfusion assemblies configured in Web.config file for the selected controls](Sample-Creator_images/Sample-Creator-img10.jpeg) + ![Required Syncfusion® assemblies configured in Web.config file for the selected controls](Sample-Creator_images/Sample-Creator-img10.jpeg) * Once the project is created you can open the project by clicking the Yes button. Refer the following screenshot for more information. - ![The project successfully created using Syncfusion Essential JS 1 ASP.NET MVC Sample Creator](Sample-Creator_images/Sample-Creator-img11.jpeg) \ No newline at end of file + ![The project successfully created using Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator](Sample-Creator_images/Sample-Creator-img11.jpeg) \ No newline at end of file diff --git a/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md b/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md index 0cfd9f05..d0d23186 100644 --- a/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md +++ b/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md @@ -1,54 +1,54 @@ --- layout: post -title: Step by Step Installation | Extension | Syncfusion -description: Step by Step Installation procedure to install Syncfusion Web Sample Creator +title: Step by Step Installation | Extension | Syncfusion +description: Step by Step Installation procedure to install Syncfusion Web Sample Creator platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Step-by-Step Installation -The following procedure illustrates how to install Syncfusion® Web Sample Creator. Before install the Syncfusion® Web Sample Creator, make sure any of the following setups are installed. +The following procedure illustrates how to install Syncfusion® Web Sample Creator. Before install the Syncfusion® Web Sample Creator, make sure any of the following setups are installed. - * Essential Studio® for Enterprise Edition with all platforms - * Essential Studio® for ASP.NET MVC - * Essential Studio® for ASP.NET - * Essential Studio® for ASP.NET Core - * Essential Studio® for ASP.NET MVC(Classic) + * Essential Studio® for Enterprise Edition with all platforms + * Essential Studio® for ASP.NET MVC + * Essential Studio® for ASP.NET + * Essential Studio® for ASP.NET Core + * Essential Studio® for ASP.NET MVC(Classic) -1. Double-click the Syncfusion® Web Sample Creator Setup file. The Self-Extractor Wizard opens and extracts the package automatically. +1. Double-click the Syncfusion® Web Sample Creator Setup file. The Self-Extractor Wizard opens and extracts the package automatically. - ![Syncfusion Web Sample Creator Setup Self-Extractor Wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img1.jpeg) + ![Syncfusion® Web Sample Creator Setup Self-Extractor Wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img1.jpeg) N> The WinZip Self-Extractor extracts the syncfusionwebsamplecreator_(version).exe dialog, displaying the unzip operation of the package. - If complete Essential Studio® suite or any of the required Essential Studio® platform setups are installed, Syncfusion® Web Sample Creator setup will be installed. + If complete Essential Studio® suite or any of the required Essential Studio® platform setups are installed, Syncfusion® Web Sample Creator setup will be installed. - ![Syncfusion Web Sample Creator setup installation wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img2.jpeg) + ![Syncfusion® Web Sample Creator setup installation wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img2.jpeg) - If complete Essential Studio® suite or any of the required Essential Studio® platform setups are not installed, Syncfusion® Web Sample Creator setup will show the below message. + If complete Essential Studio® suite or any of the required Essential Studio® platform setups are not installed, Syncfusion® Web Sample Creator setup will show the below message. - ![Syncfusion Web Sample Creator setup validation message](Step-by-Step-Installation_images/Step-by-Step-Installation-img7.jpeg) + ![Syncfusion® Web Sample Creator setup validation message](Step-by-Step-Installation_images/Step-by-Step-Installation-img7.jpeg) 2. After reading the terms, click the I accept the terms and conditions check box. -3. Click the Next button. The Installation location window opens. It shows the Syncfusion® Essential Studio® setup installed location. +3. Click the Next button. The Installation location window opens. It shows the Syncfusion® Essential Studio® setup installed location. - ![Syncfusion Web Sample Creator setup install location wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img4.jpeg) + ![Syncfusion® Web Sample Creator setup install location wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img4.jpeg) - N> It does not allow you to change the install path since its Add on setup for Syncfusion® Essential Studio. + N> It does not allow you to change the install path since its Add on setup for Syncfusion® Essential Studio®. 4. To install it in the displayed default location, click the Install button. - ![Syncfusion Web Sample Creator setup installation progress](Step-by-Step-Installation_images/Step-by-Step-Installation-img5.jpeg) + ![Syncfusion® Web Sample Creator setup installation progress](Step-by-Step-Installation_images/Step-by-Step-Installation-img5.jpeg) 5. The Completed screen will be displayed once the selected package is installed. - ![Syncfusion Web Sample Creator setup installation completed wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img6.jpeg) + ![Syncfusion® Web Sample Creator setup installation completed wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img6.jpeg) -5. Select the `Run Syncfusion® Control Panel` check box to launch the `Syncfusion Control Panel` after installed. +5. Select the `Run Syncfusion® Control Panel` check box to launch the `Syncfusion® Control Panel` after installed. -6. Click Finish button. Syncfusion® Web Sample Creator is installed in your system and the [Syncfusion Control Panel](https://help.syncfusion.com/extension/aspnet-mvc-extension/sample-creator) is launched automatically. +6. Click Finish button. Syncfusion® Web Sample Creator is installed in your system and the [Syncfusion® Control Panel](https://help.syncfusion.com/extension/aspnet-mvc-extension/sample-creator) is launched automatically. I>The syncfusionessentialextension.exe setup has renamed to syncfusionwebsamplecreator.exe from 2015 Volume 4 release. diff --git a/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md index 4233cf05..c4cfd0de 100644 --- a/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md +++ b/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md @@ -1,27 +1,27 @@ --- layout: post title: Project Templates | ASP.NET MVC (Essential JS 1) | Syncfusion -description: Syncfusion provides the Visual Studio Project Templates for the ASP.NET MVC platform to create a Syncfusion MVC application using Essential JS 1 components +description: Syncfusion provides the Visual Studio Project Templates for the ASP.NET MVC platform to create a Syncfusion MVC application using Essential JS 1 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Templates for ASP.NET MVC (Essential® JS 1) +# Syncfusion® Project Templates for ASP.NET MVC (Essential® JS 1) -Syncfusion provides the Visual Studio Project Templates for the Syncfusion® ASP.NET MVC, Syncfusion® ASP.NET MVC (Classic) and ASP.NET MVC (Mobile) platforms to create a Syncfusion® MVC application. +Syncfusion® provides the Visual Studio Project Templates for the Syncfusion® ASP.NET MVC, Syncfusion® ASP.NET MVC (Classic) and ASP.NET MVC (Mobile) platforms to create a Syncfusion® MVC application. -Syncfusion ASP.NET MVC and ASP.NET MVC (Classic) Project Templates are included here, +Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) Project Templates are included here, -* Essential Studio® for Enterprise Edition with the platforms ASP.NETMVC or ASP.NET MVC(Classic) -* Essential Studio® for ASP.NET MVC -* Essential Studio® for ASP.NET MVC (Classic) +* Essential Studio® for Enterprise Edition with the platforms ASP.NETMVC or ASP.NET MVC(Classic) +* Essential Studio® for ASP.NET MVC +* Essential Studio® for ASP.NET MVC (Classic) -I> This is not applicable from v.12.1.0.43 to v.13.1.0.30. Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) Project Templates are excluded from MVC Extension setup and integrated into Essential Studio® ASP.NET MVC and ASP.NET MVC (Classic) platforms. +I> This is not applicable from v.12.1.0.43 to v.13.1.0.30. Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) Project Templates are excluded from MVC Extension setup and integrated into Essential Studio® ASP.NET MVC and ASP.NET MVC (Classic) platforms. ## ASP.NET MVC Extensions: -By default, the Syncfusion® ASP.NET MVC extensions are configured in Visual Studio. When you want the ASP.NET MVC (Classic) extension, you can install it from the installed location. +By default, the Syncfusion® ASP.NET MVC extensions are configured in Visual Studio. When you want the ASP.NET MVC (Classic) extension, you can install it from the installed location. Project Templates (ASP.NET MVC (Classic): @@ -29,33 +29,33 @@ Location: `{Drive}\Program Files (x86)\Syncfusion\Essential Studio\\Ut For Example – VS2013:`C:\Program Files (x86)\Syncfusion\Essential Studio\13.2.0.18\Utilities\Extensions\ASP.NET MVC\Classic\4.5.1\Syncfusion.MVC.VSPackage.Web.Classic.vsix` -Refer to the following steps to create the Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) applications. +Refer to the following steps to create the Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) applications. -## Create Syncfusion® MVC (Web) Project +## Create Syncfusion® MVC (Web) Project -The following steps help you create the Syncfusion® ASP.NET MVC (Essential JS 1) Application via the Visual Studio Project Template: +The following steps help you create the Syncfusion® ASP.NET MVC (Essential® JS 1) Application via the Visual Studio Project Template: -> Before use the Syncfusion® ASP.NET MVC (Essential JS 1) Project Template, check whether the **Syncfusion® Essential® JS1 AspNet MVC VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. +> Before use the Syncfusion® ASP.NET MVC (Essential® JS 1) Project Template, check whether the **Syncfusion® Essential® JS1 AspNet MVC VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. -1. To create a Syncfusion® ASP.NET MVC (Essential JS 1) project, follow either one of the options below: +1. To create a Syncfusion® ASP.NET MVC (Essential® JS 1) project, follow either one of the options below: **Option 1:** - Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Create New Syncfusion® Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion ASP.NET MVC Web Application from Visual Studio new project dialog via Syncfusion menu](Create-Syncfusion-MVC-Project_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion® ASP.NET MVC Web Application from Visual Studio new project dialog via Syncfusion® menu](Create-Syncfusion-MVC-Project_images/Syncfusion_Menu_ProjectTemplate.png) - N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Choose **File > New > Project** and navigate to **Syncfusion > Web > Syncfusion® ASP.NET MVC (Essential JS 1) Application** in **Visual Studio**. + Choose **File > New > Project** and navigate to **Syncfusion® > Web > Syncfusion® ASP.NET MVC (Essential® JS 1) Application** in **Visual Studio**. - ![Choose Syncfusion ASP.NET MVC Web Application from Visual Studio new project dialog](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img1.png) + ![Choose Syncfusion® ASP.NET MVC Web Application from Visual Studio new project dialog](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img1.png) 2. Name the Project, choose the destination location as required and set the Framework of the project then click OK. The Project Configuration Wizard appears.   -3. Choose the options to configure the Syncfusion® ASP.NET MVC Application by using the following Project Configuration window. +3. Choose the options to configure the Syncfusion® ASP.NET MVC Application by using the following Project Configuration window. - ![Syncfusion Essential JS 1 ASP.NET MVC Web Project configuration wizard](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img2.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project configuration wizard](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img2.jpeg) ### Project configurations: @@ -79,15 +79,15 @@ The following steps help you create the Syncfusion&re ![Choose the assembly location from where it is going to be added to the project](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img7.jpeg) - **Use CDN Support:** The master page of the project will be updated based on required Syncfusion® CDN links. + **Use CDN Support:** The master page of the project will be updated based on required Syncfusion® CDN links. ![Choose CDN support](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img28.jpeg) -4. When you have not chosen the Add Samples option then the Syncfusion® ASP.NET MVC/ Syncfusion® ASP.NET MVC (Classic) project is created with required assemblies, CSS and Script files only. +4. When you have not chosen the Add Samples option then the Syncfusion® ASP.NET MVC/ Syncfusion® ASP.NET MVC (Classic) project is created with required assemblies, CSS and Script files only. 5. By choosing the Add Samples option you can add the code examples for your selected controls and its features. - ![Syncfusion Essential JS 1 ASP.NET MVC Web Feature selection](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img8.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Feature selection](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img8.jpeg) **Select Control:** Choose the control based on your need. @@ -97,34 +97,34 @@ The following steps help you create the Syncfusion&re ![Choose required features](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img10.jpeg) -6. Once the Project Configuration Wizard is done, the Syncfusion® MVC Project is created. +6. Once the Project Configuration Wizard is done, the Syncfusion® MVC Project is created. ![Required View and Controller files are added in the project for the selected controls](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img11.jpeg) -7. Syncfusion® references, Scripts, CSS and required Web.config entries are added to the Project. +7. Syncfusion® references, Scripts, CSS and required Web.config entries are added to the Project. - ![Required Syncfusion assemblies added in the project created for the selected controls](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img12.jpeg) + ![Required Syncfusion® assemblies added in the project created for the selected controls](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img12.jpeg) ![Required scripts and themes added in the project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img13.jpeg) ![Web.config file configured for the selected controls in the project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img14.jpeg) -8. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. +8. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required message box for Syncfusion Essential JS 1 ASP.NET MVC web projects](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img29.jpeg) + ![Syncfusion® license registration required message box for Syncfusion® Essential® JS 1 ASP.NET MVC web projects](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img29.jpeg) -## Create Syncfusion® MVC (Mobile) Project +## Create Syncfusion® MVC (Mobile) Project -The following steps help you create the Syncfusion® ASP.NET MVC (Mobile) Project via the Visual Studio Project Template. +The following steps help you create the Syncfusion® ASP.NET MVC (Mobile) Project via the Visual Studio Project Template. -1. To create a Syncfusion® Project, choose **New Project -> Syncfusion® -> Mobile -> Syncfusion® ASP.NET MVC(Mobile) Application** from Visual Studio. +1. To create a Syncfusion® Project, choose **New Project -> Syncfusion® -> Mobile -> Syncfusion® ASP.NET MVC(Mobile) Application** from Visual Studio. - ![Choose Syncfusion ASP.NET MVC Mobile Application from Visual Studio new project dialog](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img15.jpeg) + ![Choose Syncfusion® ASP.NET MVC Mobile Application from Visual Studio new project dialog](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img15.jpeg) 2. Name the Project, choose the destination location as required and set the Framework of the project then click OK. The Project Configuration Wizard appears.   -3. Choose the options to configure the Syncfusion® ASP.NET MVC Application by using the following Project Configuration window. +3. Choose the options to configure the Syncfusion® ASP.NET MVC Application by using the following Project Configuration window. - ![Syncfusion Essential JS 1 ASP.NET MVC Mobile project configuration wizard](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img16.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile project configuration wizard](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img16.jpeg) ### Project configurations: @@ -152,18 +152,18 @@ The following steps help you create the Syncfusion&re ![Choose the required controls](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img22.jpeg) -4. Once the Project Configuration Wizard is done, the Syncfusion® MVC Project is created. +4. Once the Project Configuration Wizard is done, the Syncfusion® MVC Project is created. - ![Required view and controller files added in the Syncfusion Essential JS 1 ASP.NET MVC Mobile project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img23.jpeg) + ![Required view and controller files added in the Syncfusion® Essential® JS 1 ASP.NET MVC Mobile project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img23.jpeg) -5. Syncfusion® references, Scripts, CSS and required Web.config entries are added to the Project. +5. Syncfusion® references, Scripts, CSS and required Web.config entries are added to the Project. ![Required assemblies added as a reference in the project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img24.jpeg) ![Required themes and scripts added to the project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img25.jpeg) - ![Syncfusion Essential JS 1 ASP.NET MVC Mobile project required scripts](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img26.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile project required scripts](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img26.jpeg) - ![Syncfusion Essential JS 1 ASP.NET MVC Mobile project Web.config configuration](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img27.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile project Web.config configuration](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img27.jpeg) diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/create-project.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/create-project.md index d206fb79..3eead6fd 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/create-project.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/create-project.md @@ -1,33 +1,33 @@ --- layout: post title: Project Templates | ASP.NET Core (Essential JS 2) | Syncfusion -description: Syncfusion provides Project Templates for ASP.NET Core to create the Syncfusion ASP.NET Core Application using EJ2 Core components from Visual Studio Code. +description: Syncfusion provides Project Templates for ASP.NET Core to create the Syncfusion ASP.NET Core Application using EJ2 Core components from Visual Studio Code. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Creating a Syncfusion® ASP.NET Core Application +# Creating a Syncfusion® ASP.NET Core Application -Syncfusion provides **Visual Studio Code project templates** for creating Syncfusion® ASP.NET Core application. Syncfusion® ASP.NET Core generates application that include the necessary Syncfusion® NuGet packages, namespaces, and component render code for the Calendar, Button, and DataGrid components, as well as the style for making Syncfusion® component development easier. +Syncfusion® provides **Visual Studio Code project templates** for creating Syncfusion® ASP.NET Core application. Syncfusion® ASP.NET Core generates application that include the necessary Syncfusion® NuGet packages, namespaces, and component render code for the Calendar, Button, and DataGrid components, as well as the style for making Syncfusion® component development easier. -> The Syncfusion® Visual Studio Code project template provides support for ASP.NET Core project templates from v20.1.0.47. +> The Syncfusion® Visual Studio Code project template provides support for ASP.NET Core project templates from v20.1.0.47. -The following instructions assist you in creating **Syncfusion ASP.NET Core Applications** using **Visual Studio Code**: +The following instructions assist you in creating **Syncfusion® ASP.NET Core Applications** using **Visual Studio Code**: -1. To create a Syncfusion® ASP.NET Core application in Visual Studio Code, open the command palette by pressing **Ctrl+Shift+P**. Search for the word **Syncfusion** in the Visual Studio Code palette to get the templates provided by Syncfusion. +1. To create a Syncfusion® ASP.NET Core application in Visual Studio Code, open the command palette by pressing **Ctrl+Shift+P**. Search for the word **Syncfusion®** in the Visual Studio Code palette to get the templates provided by Syncfusion®. ![command-palette](images/command-palette.png) -2. Select **Syncfusion ASP.NET Core Template Studio: Launch**, then press **Enter** key. The template studio wizard for configuring the Syncfusion® ASP.NET Core application is launched. Then, provide the Project Name and Project Path. +2. Select **Syncfusion® ASP.NET Core Template Studio: Launch**, then press **Enter** key. The template studio wizard for configuring the Syncfusion® ASP.NET Core application is launched. Then, provide the Project Name and Project Path. ![core-wizard](images/launch-window.png) -3. Select either **Next** or the **Project Type** tab. Syncfusion® ASP.NET Core Project Types will be displayed. Select one of the following Syncfusion® ASP.NET Core project types: +3. Select either **Next** or the **Project Type** tab. Syncfusion® ASP.NET Core Project Types will be displayed. Select one of the following Syncfusion® ASP.NET Core project types: - * Syncfusion® Web Application (Model-View-Controller) - * Syncfusion® Angular - * Syncfusion® React.js + * Syncfusion® Web Application (Model-View-Controller) + * Syncfusion® Angular + * Syncfusion® React.js ![project-type](images/project-type.png) @@ -35,12 +35,12 @@ The following instructions assist you in creating **Syncfusion ASP.NET Core Appl ![project-configuration](images/project-configuration.png) - > In assets from the Installed location option will be available when the Syncfusion® Essential® JavaScript 2 build has been installed. + > In assets from the Installed location option will be available when the Syncfusion® Essential® JavaScript 2 build has been installed. -5. Click the **Create** button. The Syncfusion® ASP.NET Core application will be created. The created Syncfusion® ASP.NET Core application has the Syncfusion® NuGet packages, NPM Packages, styles, and the component render code for the Syncfusion® component added to the index page.T +5. Click the **Create** button. The Syncfusion® ASP.NET Core application will be created. The created Syncfusion® ASP.NET Core application has the Syncfusion® NuGet packages, NPM Packages, styles, and the component render code for the Syncfusion® component added to the index page.T -6. You can run the application to see the Syncfusion® components. Click **F5** or go to **Run>Start Debugging**. +6. You can run the application to see the Syncfusion® components. Click **F5** or go to **Run>Start Debugging**. ![debugging](images/debugging.png) -7. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. +7. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/download-and-installation.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/download-and-installation.md index 3026d587..be3d8b23 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/download-and-installation.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/download-and-installation.md @@ -1,19 +1,19 @@ --- layout: post title: Download and Installation | ASP.NET Core (Essential JS2) | Syncfusion -description: How to download and install the Syncfusion ASP.NET Core (Essential JS2) Visual Studio Code Extensions from Visual Studio Code Market Place +description: How to download and install the Syncfusion ASP.NET Core (Essential JS2) Visual Studio Code Extensions from Visual Studio Code Market Place platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -Syncfusion publishes the Visual Studio Code extension in Visual Studio Code marketplace. You can either install it from the Visual Studio Code or download and install it from the Visual Studio Code marketplace. +Syncfusion® publishes the Visual Studio Code extension in Visual Studio Code marketplace. You can either install it from the Visual Studio Code or download and install it from the Visual Studio Code marketplace. ## Prerequisites -To install the Syncfusion® ASP.NET Core Visual Studio Code extension and the creation of Syncfusion® ASP.NET Core apps using any of the project types (Syncfusion Web Application (Model-View-Controller), Syncfusion® Angular, and Syncfusion® React), the following required software must be installed: +To install the Syncfusion® ASP.NET Core Visual Studio Code extension and the creation of Syncfusion® ASP.NET Core apps using any of the project types (Syncfusion® Web Application (Model-View-Controller), Syncfusion® Angular, and Syncfusion® React), the following required software must be installed: * [Visual Studio Code 1.29.0 or later](https://code.visualstudio.com/download) * [Visual Studio 2019 16.3 Preview 2](https://visualstudio.microsoft.com/vs/) or later @@ -24,7 +24,7 @@ To install the Syncfusion® ASP.NET Core Vi ## Install through the Visual Studio Code extensions -The following steps explain how to install the Syncfusion® ASP.NET Core Visual Studio Code extensions from Visual Studio Code: +The following steps explain how to install the Syncfusion® ASP.NET Core Visual Studio Code extensions from Visual Studio Code: 1. Open Visual Studio Code. @@ -32,32 +32,32 @@ The following steps explain how to install the Syncfusion® ASP.NET Core application by using the Syncfusion® ASP.NET Core extensions from the Visual Studio Code Palette. Find the Syncfusion® ASP.NET Core Template Studio: Launch from Visual Studio Code commands to open the Syncfusion® ASP.NET Core Template Studio wizard. +6. Now, you can create a new Syncfusion® ASP.NET Core application by using the Syncfusion® ASP.NET Core extensions from the Visual Studio Code Palette. Find the Syncfusion® ASP.NET Core Template Studio: Launch from Visual Studio Code commands to open the Syncfusion® ASP.NET Core Template Studio wizard. ![command-palette](images/command-palette.png) ## Install from the Visual Studio Code Marketplace -The following steps explain how to install Syncfusion® ASP.NET Core applications from the Visual Studio Code Marketplace: +The following steps explain how to install Syncfusion® ASP.NET Core applications from the Visual Studio Code Marketplace: -1. Open the Syncfusion® ASP.NET Core Visual Studio Code Extension in Visual Studio Code Marketplace. +1. Open the Syncfusion® ASP.NET Core Visual Studio Code Extension in Visual Studio Code Marketplace. -2. Click Install from Visual Studio Code Marketplace to open the popup with the information, “**Open Visual Studio Code.**” Then, click Open Visual Studio Code, and Syncfusion® ASP.NET Core Extension will open in Visual Studio Code. +2. Click Install from Visual Studio Code Marketplace to open the popup with the information, “**Open Visual Studio Code.**” Then, click Open Visual Studio Code, and Syncfusion® ASP.NET Core Extension will open in Visual Studio Code. -3. Click the Install button in the “**ASP.NET Core VS Code Extensions - Syncfusion**” extension. +3. Click the Install button in the “**ASP.NET Core VS Code Extensions - Syncfusion®**” extension. 4. Use the Reload Window command in the Visual Studio Code palette and reload Visual Studio Code after installation. By using **Ctrl+Shift+P**, you can bring up the command palette and select Reload Window from the list of Visual Studio Code commands. ![reload-window](images/reload-window.png) -5. Now, you can create a new Syncfusion® ASP.NET Core application by using the Syncfusion® ASP.NET Core extensions from the Visual Studio Code Palette. Find the **Syncfusion ASP.NET Core Template Studio: Launch** from Visual Studio Code commands to open the Syncfusion® ASP.NET Core Template Studio wizard. +5. Now, you can create a new Syncfusion® ASP.NET Core application by using the Syncfusion® ASP.NET Core extensions from the Visual Studio Code Palette. Find the **Syncfusion® ASP.NET Core Template Studio: Launch** from Visual Studio Code commands to open the Syncfusion® ASP.NET Core Template Studio wizard. ![command-palette](images/command-palette.png) \ No newline at end of file diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/overview.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/overview.md index 370dd47f..8f6c9cfe 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/overview.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/overview.md @@ -1,7 +1,7 @@ --- layout: post title: ASP.NET Core (Essential JS 2) Extension | Extension | Syncfusion -description: The Syncfusion ASP.NET Core Extensions provide quick access to create or configure the Syncfusion ASP.NET projects along with Essential JS 2 components. +description: The Syncfusion ASP.NET Core Extensions provide quick access to create or configure the Syncfusion ASP.NET projects along with Essential JS 2 components. platform: extension control: Syncfusion Extensions documentation: ug @@ -9,8 +9,8 @@ documentation: ug # Overview of ASP.NET Core Extension for Visual Studio Code -The Syncfusion® ASP.NET Core Extension for Visual Studio Code makes it simple to use the Syncfusion® ASP.NET Core components in the ASP.NET Core application by simply configuring the Syncfusion® NPM or NuGet packages and themes. +The Syncfusion® ASP.NET Core Extension for Visual Studio Code makes it simple to use the Syncfusion® ASP.NET Core components in the ASP.NET Core application by simply configuring the Syncfusion® NPM or NuGet packages and themes. -The Syncfusion® ASP.NET Core Extension provides the following support in Visual Studio Code: +The Syncfusion® ASP.NET Core Extension provides the following support in Visual Studio Code: -[Create-Project](create-project): Creates Syncfusion® ASP.NET Core application (Syncfusion Web Application (Model-View-Controller), Syncfusion® Angular, Syncfusion® React.js) with the necessary configuration to use in Syncfusion® ASP.NET Core component during development. +[Create-Project](create-project): Creates Syncfusion® ASP.NET Core application (Syncfusion® Web Application (Model-View-Controller), Syncfusion® Angular, Syncfusion® React.js) with the necessary configuration to use in Syncfusion® ASP.NET Core component during development. diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Overview.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Overview.md index 4b2b182b..4fc61d0d 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Overview.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Overview.md @@ -1,9 +1,9 @@ --- layout: post title: ASP.NET Core (Essential JS 2) Extension | Extension | Syncfusion -description: The Syncfusion ASP.NET Core Extensions provide quick access to create or configure the Syncfusion ASP.NET projects along with Essential JS 2 components. +description: The Syncfusion ASP.NET Core Extensions provide quick access to create or configure the Syncfusion ASP.NET projects along with Essential JS 2 components. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- @@ -11,20 +11,20 @@ documentation: ug ## Overview -The Syncfusion® ASP.NET Core (Essential JS 2) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio. +The Syncfusion® ASP.NET Core (Essential® JS 2) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio. -> Syncfusion® Extension is published in Visual Studio Marketplace. You can download ASP.NET Core (EJ2) Extensions [here](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETCoreExtensions) +> Syncfusion® Extension is published in Visual Studio Marketplace. You can download ASP.NET Core (EJ2) Extensions [here](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETCoreExtensions) ## IMPORTANT -The Syncfusion® ASP.NET Core (Essential JS 2) menu option is available from v17.1.0.32. +The Syncfusion® ASP.NET Core (Essential® JS 2) menu option is available from v17.1.0.32. -The Syncfusion® provides the following supports in Visual Studio: +The Syncfusion® provides the following supports in Visual Studio: -1. [Project-Template](syncfusion-project-templates): Creates the Syncfusion® ASP.NET Core (Essential JS 2) application by adding the required Essential JS 2 components. -2. [Convert project](project-conversion): Converts an existing ASP.NET Core application into a Syncfusion® ASP.NET Core (Essential JS 2) application by adding the required Syncfusion® assemblies and resource files. -3. [Upgrade project](project-migration): Upgrades the existing Syncfusion® ASP.NET Core (Essential JS 2) application from one Essential Studio® version to another version. -4. [Creator sample](sample-creator): Creates the Syncfusion® ASP.NET Core (Essential JS2) application with the sample code of required controls and features. +1. [Project-Template](syncfusion-project-templates): Creates the Syncfusion® ASP.NET Core (Essential® JS 2) application by adding the required Essential® JS 2 components. +2. [Convert project](project-conversion): Converts an existing ASP.NET Core application into a Syncfusion® ASP.NET Core (Essential® JS 2) application by adding the required Syncfusion® assemblies and resource files. +3. [Upgrade project](project-migration): Upgrades the existing Syncfusion® ASP.NET Core (Essential® JS 2) application from one Essential Studio® version to another version. +4. [Creator sample](sample-creator): Creates the Syncfusion® ASP.NET Core (Essential® JS2) application with the sample code of required controls and features. ### No project selected in Visual Studio @@ -34,8 +34,8 @@ The Syncfusion® provides the following sup ![selected microsoft](images/selected-project.png) -### Selected Syncfusion® ASP.NET Core (Essential JS2) application in Visual Studio +### Selected Syncfusion® ASP.NET Core (Essential® JS2) application in Visual Studio -![selected syncfusion](images/selected-syncfusion-project.png) +![selected syncfusion®](images/selected-syncfusion-project.png) -> From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. +> From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Conversion.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Conversion.md index fb10ae71..199cd8e6 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Conversion.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Conversion.md @@ -1,55 +1,55 @@ --- layout: post title: Project Conversion | ASP.NET Core (Essential JS 2) | Syncfusion -description: Project Conversion is a add-in that converts ASP.NET Core application into a Syncfusion ASP.NET Core application by adding required Essential JS 2 components +description: Project Conversion is a add-in that converts ASP.NET Core application into a Syncfusion ASP.NET Core application by adding required Essential JS 2 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Conversion +# Syncfusion® Project Conversion -Syncfusion ASP.NET Core conversion is a Visual Studio add-in that converts an existing ASP.NET Core application into a Syncfusion® ASP.NET Core (Essential JS 2) Web application by adding the required assemblies and resource files. +Syncfusion® ASP.NET Core conversion is a Visual Studio add-in that converts an existing ASP.NET Core application into a Syncfusion® ASP.NET Core (Essential® JS 2) Web application by adding the required assemblies and resource files. -> The Syncfusion® ASP.NET Core (Essential® JS 2) Web Application Project conversion utility is available from v16.3.0.17. Before use, the Syncfusion® ASP.NET Core Project Conversion, check whether the **ASP.NET Core Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetcore/documentation/visual-studio-integration/download-and-installation) help topic. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. +> The Syncfusion® ASP.NET Core (Essential® JS 2) Web Application Project conversion utility is available from v16.3.0.17. Before use, the Syncfusion® ASP.NET Core Project Conversion, check whether the **ASP.NET Core Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetcore/documentation/visual-studio-integration/download-and-installation) help topic. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. -The steps below help you to convert the ASP.NET Core application to the Syncfusion® ASP.NET Core application via the Visual Studio 2019: +The steps below help you to convert the ASP.NET Core application to the Syncfusion® ASP.NET Core application via the Visual Studio 2019: 1. Open an existing Microsoft ASP.NET Core Web Application or create a new Microsoft ASP.NET Core Web Application. -2. To open the Syncfusion® Project Conversion Wizard, follow either one of the options below: +2. To open the Syncfusion® Project Conversion Wizard, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET Core > Convert to Syncfusion® ASP.NET Core Application…** in **Visual Studio Menu**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core > Convert to Syncfusion® ASP.NET Core Application…** in **Visual Studio Menu**. ![convert project](images/convert-new-app.png) - > From Visual Studio 2019, Syncfusion® menu is available under **Extensions** in Visual Studio menu. + > From Visual Studio 2019, Syncfusion® menu is available under **Extensions** in Visual Studio menu. ![convert project](images/convert-new-app-2019.png) **Option 2:** - Right-click the **Project** from Solution Explorer, select **Syncfusion Web**, and choose the **Convert to Syncfusion® ASP.NET Core Application…** + Right-click the **Project** from Solution Explorer, select **Syncfusion® Web**, and choose the **Convert to Syncfusion® ASP.NET Core Application…** - ![convert to syncfusion](images/convert-to-syncfusion-ASpnet-core.png) + ![convert to syncfusion®](images/convert-to-syncfusion-ASpnet-core.png) -3. The Syncfusion® ASP.NET Core Project Conversion window will appear. You can choose the required version of Syncfusion® ASP.NET Core, Assets from, and Themes to convert the application. +3. The Syncfusion® ASP.NET Core Project Conversion window will appear. You can choose the required version of Syncfusion® ASP.NET Core, Assets from, and Themes to convert the application. ![project conversion wizard](images/project-conversion-wizard.png) The following configurations are used in the Project conversion wizard. - **Assets From:** Load the Syncfusion® Essential® JS 2 assets to ASP.NET Core Project, from either NPM, CDN, or Installed Location. + **Assets From:** Load the Syncfusion® Essential® JS 2 assets to ASP.NET Core Project, from either NPM, CDN, or Installed Location. - > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. + > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. **Choose the Theme:** Choose the required theme. 4. Check the **“Enable a backup before converting”** checkbox if you want to take the project backup and choose the location. -5. The required Syncfusion® NuGet packages, Scripts and CSS are included in the ASP.NET Core Web application. Refer to the following screenshots for more information. +5. The required Syncfusion® NuGet packages, Scripts and CSS are included in the ASP.NET Core Web application. Refer to the following screenshots for more information. ![dependencies](images/dependencies.png) @@ -61,4 +61,4 @@ The steps below help you to convert the ASP.NET Core application to the Syncfusi ![BackupLocation](images/BackupLocation.png) -6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file +6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Migration.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Migration.md index bfe584c5..2d528f12 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Migration.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Migration.md @@ -1,58 +1,58 @@ --- layout: post title: Project Migration | ASP.NET Core (Essential JS 2) | Syncfusion -description: Project Migration is a add-in that allows you to migrate the existing Syncfusion ASP.NET Core Application from one Essential Studio version to another version +description: Project Migration is a add-in that allows you to migrate the existing Syncfusion ASP.NET Core Application from one Essential Studio version to another version platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Upgrading Syncfusion® ASP.NET Core application to latest version +# Upgrading Syncfusion® ASP.NET Core application to latest version -The Syncfusion® ASP.NET Core migration add-in for Visual Studio allows you to migrate an existing Syncfusion® ASP.NET Core application from one version of Essential Studio® version to another version. This reduces the amount of manual work required when migrating the Syncfusion® version. +The Syncfusion® ASP.NET Core migration add-in for Visual Studio allows you to migrate an existing Syncfusion® ASP.NET Core application from one version of Essential Studio® version to another version. This reduces the amount of manual work required when migrating the Syncfusion® version. ## IMPORTANT -The Syncfusion® ASP.NET Core (Essential JS 2) Web Application Project Migration utility is available from v16.3.0.17. +The Syncfusion® ASP.NET Core (Essential® JS 2) Web Application Project Migration utility is available from v16.3.0.17. -> Before use, the Syncfusion® ASP.NET Core Project Migration, check whether the **ASP.NET Core Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetcore/documentation/visual-studio-integration/download-and-installation) help topic. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. +> Before use, the Syncfusion® ASP.NET Core Project Migration, check whether the **ASP.NET Core Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetcore/documentation/visual-studio-integration/download-and-installation) help topic. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. -The steps below will assist you to upgrade the Syncfusion® version in the Syncfusion® ASP.NET Core application via Visual Studio 2019: +The steps below will assist you to upgrade the Syncfusion® version in the Syncfusion® ASP.NET Core application via Visual Studio 2019: -1. Open the Syncfusion® ASP.NET Core application that uses the Syncfusion® component. +1. Open the Syncfusion® ASP.NET Core application that uses the Syncfusion® component. 2. To open the Migration Wizard, either one of the following options should be followed: **Option 1** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET Core > Migrate Project…** in **Visual Studio Menu**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core > Migrate Project…** in **Visual Studio Menu**. ![migrate project](images/migrate-project.png) - > From Visual Studio 2019, Syncfusion® menu is available under **Extensions** in Visual Studio menu. + > From Visual Studio 2019, Syncfusion® menu is available under **Extensions** in Visual Studio menu. **Option 2** - Right-click the **Syncfusion ASP.NET Core Application** from Solution Explorer and select **Syncfusion Web**. Choose **Migrate the Syncfusion® ASP.NET Core Project to Another Version…** + Right-click the **Syncfusion® ASP.NET Core Application** from Solution Explorer and select **Syncfusion® Web**. Choose **Migrate the Syncfusion® ASP.NET Core Project to Another Version…** ![migrate syncfuion project](images/migrate-syncfusion-EJ2.png) -3. The Syncfusion® Project Migration window will appear. You can choose the required version of Syncfusion® ASP.NET Core to migrate. +3. The Syncfusion® Project Migration window will appear. You can choose the required version of Syncfusion® ASP.NET Core to migrate. ![project migration](images/project-migration.png) - > The versions are loaded from the Syncfusion® ASP.NET Core NuGet packages which published in [NuGet.org](https://www.nuget.org/packages?q=Tags%3A%22aspnetcore%22syncfusion) and it requires internet connectivity. + > The versions are loaded from the Syncfusion® ASP.NET Core NuGet packages which published in [NuGet.org](https://www.nuget.org/packages?q=Tags%3A%22aspnetcore%22syncfusion) and it requires internet connectivity. - **Assets From:** Load the Syncfusion® Essential® JS 2 assets to ASP.NET Core Project, from either NPM, CDN or Installed Location. + **Assets From:** Load the Syncfusion® Essential® JS 2 assets to ASP.NET Core Project, from either NPM, CDN or Installed Location. - > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. + > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. 4. Check the **“Enable a backup before migrating”** checkbox if you want to take the project backup and choose location. -5. The Syncfusion® Reference Assemblies, Scripts, and CSS are updated to the corresponding version in the project. +5. The Syncfusion® Reference Assemblies, Scripts, and CSS are updated to the corresponding version in the project. If you enabled project backup before migrating, the old project was saved in the specified backup path location, as shown below once the migration process completed ![BackupLocation](images/BackupLocation.png) -6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file +6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Sample-Creator.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Sample-Creator.md index 4b820974..3e3779a0 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Sample-Creator.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Sample-Creator.md @@ -1,39 +1,39 @@ --- layout: post title: Sample Creator | ASP.NET Core (Essential JS 2) | Syncfusion -description: Sample Creator is a utility that allows you to create the Syncfusion ASP.NET Core (Essential JS 2) Projects with required Syncfusion controls +description: Sample Creator is a utility that allows you to create the Syncfusion ASP.NET Core (Essential JS 2) Projects with required Syncfusion controls platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Creating Syncfusion® ASP.NET Core application +# Creating Syncfusion® ASP.NET Core application -The Syncfusion® Sample Creator is a tool that lets you make Syncfusion® ASP.NET Core (Essential JS 2) projects with sample code for required Syncfusion® component features and Syncfusion® control configuration. +The Syncfusion® Sample Creator is a tool that lets you make Syncfusion® ASP.NET Core (Essential® JS 2) projects with sample code for required Syncfusion® component features and Syncfusion® control configuration. -> The Syncfusion® ASP.NET Core (Essential JS 2) Sample Creator utility is available from v16.3.0.17. +> The Syncfusion® ASP.NET Core (Essential® JS 2) Sample Creator utility is available from v16.3.0.17. -The following steps is used to create the Syncfusion® ASP.NET Core (Essential JS 2) Application by using the Sample Creator utility: +The following steps is used to create the Syncfusion® ASP.NET Core (Essential® JS 2) Application by using the Sample Creator utility: -1. Follow one of the options below to launch the ASP.NET Core (Essential JS 2) Sample Creator application: +1. Follow one of the options below to launch the ASP.NET Core (Essential® JS 2) Sample Creator application: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET Core (EJ2) > Launch Sample Creator…** in **Visual Studio.** + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ2) > Launch Sample Creator…** in **Visual Studio.** ![sample creator](images/sample-creator.png) **Option 2:** - Launch the Syncfusion® ASP.NET Core (Essential JS 2) Control Panel and click the Sample Creator button to launch the ASP.NET Core (Essential JS 2) Sample Creator utility. For further information, see the screenshot below. + Launch the Syncfusion® ASP.NET Core (Essential® JS 2) Control Panel and click the Sample Creator button to launch the ASP.NET Core (Essential® JS 2) Sample Creator utility. For further information, see the screenshot below. ![control-panel](images/sample-creator-control-panel.png) -2. Syncfusion® controls and features are listed in the ASP.NET Core (Essential JS 2) Sample Creator. +2. Syncfusion® controls and features are listed in the ASP.NET Core (Essential® JS 2) Sample Creator. ![controls-list](images/controls-list.png) - **Controls Selection:** Choose the required controls. The controls are grouped with Syncfusion® products. + **Controls Selection:** Choose the required controls. The controls are grouped with Syncfusion® products. ![control selection](images/controls-selection.png) @@ -59,15 +59,15 @@ The following steps is used to create the Syncfusion& > .NET 8.0 is available from v23.2.4 and support from Visual Studio 2022. - **Assets From**: Choose the Syncfusion® Essential® JS 2 assets to ASP.NET Core Project, either NPM, CDN, or Installed Location. + **Assets From**: Choose the Syncfusion® Essential® JS 2 assets to ASP.NET Core Project, either NPM, CDN, or Installed Location. - > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. + > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. - **Name**: Name your Syncfusion® ASP.NET Core (Essential JS 2) Application. + **Name**: Name your Syncfusion® ASP.NET Core (Essential® JS 2) Application. **Location**: Choose the target location of your project. - **Theme Selection**: Choose the required theme. This section shows the controls preview before creating the Syncfusion® project. + **Theme Selection**: Choose the required theme. This section shows the controls preview before creating the Syncfusion® project. ![theme selection](images/theme-selection.png) @@ -75,16 +75,16 @@ The following steps is used to create the Syncfusion& ![create](images/create-button.png) -3. The new Syncfusion® ASP.NET Core (Essential JS 2) project is created with the resources. +3. The new Syncfusion® ASP.NET Core (Essential® JS 2) project is created with the resources. * Added the required Controllers and View files in the project. ![controllers](images/required-controllers.png) - * Included the required Syncfusion® ASP.NET Core (Essential JS 2) scripts and theme files. + * Included the required Syncfusion® ASP.NET Core (Essential® JS 2) scripts and theme files. ![scripts and css](images/scripts-css.png) - * Restored the required Syncfusion® NuGet packages for selected controls under dependencies. + * Restored the required Syncfusion® NuGet packages for selected controls under dependencies. ![nuget packages](images/nuget-packges.png) \ No newline at end of file diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md index 051d76f5..3ecc6eb6 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md @@ -1,59 +1,59 @@ --- layout: post title: Scaffolding | ASP.NET Core | Syncfusion -description: Code-generation Framework for Syncfusion ASP.NET Core platform to quickly create the Controller and Views in a short time. +description: Code-generation Framework for Syncfusion ASP.NET Core platform to quickly create the Controller and Views in a short time. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # ASP.NET Core Scaffolding -Syncfusion provides **Visual Studio Scaffolding** for Syncfusion® ASP.NET Core platform to quickly add code that interacts with data models and reduce the amount of time to develop with data operation in your project. Scaffolding provides an easier way to create Views and Controller action methods for Syncfusion® ASP.NET Core DataGrid, Charts, Scheduler, Diagram, Tree Grid, Rich Text Editor, Document Editor, and PDF Viewer controls. +Syncfusion® provides **Visual Studio Scaffolding** for Syncfusion® ASP.NET Core platform to quickly add code that interacts with data models and reduce the amount of time to develop with data operation in your project. Scaffolding provides an easier way to create Views and Controller action methods for Syncfusion® ASP.NET Core DataGrid, Charts, Scheduler, Diagram, Tree Grid, Rich Text Editor, Document Editor, and PDF Viewer controls. > Check that at least one Entity Framework model exists, and the application has been compiled once. If no Entity Framework model exist in your application, refer to this [documentation](https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/adding-model?view=aspnetcore-3.1) to generate the Entity Framework model. After the model file has been added, check that the required DBContext and properties have been added. Build the application before try scaffolding. If any changes have been done in the model properties, rebuild the application once before performing scaffolding. -> The Syncfusion® ASP.NET Core UI Scaffolder is available from 18.4.0.39 to ASP.NET Core web application. +> The Syncfusion® ASP.NET Core UI Scaffolder is available from 18.4.0.39 to ASP.NET Core web application. ## Add a scaffolded item The following steps explain you how to add a scaffolded item to your ASP.NET Core Web application. -> Before use, the Syncfusion® ASP.NET Core Scaffolding, check whether the **ASP.NET Core Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetcore/documentation/visual-studio-integration/VS2019-Extensions/download-and-installation/) help topic. +> Before use, the Syncfusion® ASP.NET Core Scaffolding, check whether the **ASP.NET Core Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetcore/documentation/visual-studio-integration/VS2019-Extensions/download-and-installation/) help topic. 1. Right-click the **Controllers** folder in the Solution Explorer, click **Add**, and then select **New Scaffolded Item…** - ![Syncfusion Scaffolded add-in](images/Scaffolding_Add_Item1.png) + ![Syncfusion® Scaffolded add-in](images/Scaffolding_Add_Item1.png) - 2. In the **Add Scaffold dialog**, select **Syncfusion ASP.NET Core UI Scaffolder**, and then click **‘Add’**. + 2. In the **Add Scaffold dialog**, select **Syncfusion® ASP.NET Core UI Scaffolder**, and then click **‘Add’**. - ![Choose Syncfusion® Scaffolding from Visual Studio Add scaffold dialog](images/Scaffolding_Add_Item2.png) + ![Choose Syncfusion® Scaffolding from Visual Studio Add scaffold dialog](images/Scaffolding_Add_Item2.png) - 3. In the Syncfusion® UI Scaffolder dialog, select the desired Syncfusion® control to perform scaffolding, and then click **Next**. + 3. In the Syncfusion® UI Scaffolder dialog, select the desired Syncfusion® control to perform scaffolding, and then click **Next**. ![Choose required control](images/Scaffolding_Add_Item3.png) - 4. Selected control model dialog will be launched in the Syncfusion® UI Scaffolder. Enter the **Controller Name** and **View Name** as application requirements, and then select the required **Model Class** of the active project and its relevant **Data Context Class**, and then click **Next**. + 4. Selected control model dialog will be launched in the Syncfusion® UI Scaffolder. Enter the **Controller Name** and **View Name** as application requirements, and then select the required **Model Class** of the active project and its relevant **Data Context Class**, and then click **Next**. ![Choose required Model](images/Scaffolding_Add_Item4.png) - 5. Selected control feature dialog will be launched in the Syncfusion® UI Scaffolder. Choose the required features, update the required data field, and then click **Add**. + 5. Selected control feature dialog will be launched in the Syncfusion® UI Scaffolder. Choose the required features, update the required data field, and then click **Add**. ![Choose required selected control features](images/Scaffolding_Add_Item5.png) - 6. The **Controller** and the corresponding **View** files will be added into the application with the selected features of Syncfusion® control code snippet. + 6. The **Controller** and the corresponding **View** files will be added into the application with the selected features of Syncfusion® control code snippet. ![Required Controller and View files added in the project for the selected control](images/Scaffolding_Add_Item6.png) 7. Then, add navigation to the created view file based on your requirement to open in the webpage. - 8. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. + 8. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. -## Syncfusion® ASP.NET Core Command-line Scaffolding +## Syncfusion® ASP.NET Core Command-line Scaffolding -Syncfusion provides **Scaffolding command-line** for Syncfusion® ASP.NET Core to quickly add code that interacts with data models and reduce the amount of time to develop with data operation in your project. Scaffolding provides an easier way to create view file and Controller action methods for Syncfusion® ASP.NET Core DataGrid, Charts, Scheduler, Diagram, Tree Grid, Rich Text Editor, Document Editor, and PDF Viewer controls. +Syncfusion® provides **Scaffolding command-line** for Syncfusion® ASP.NET Core to quickly add code that interacts with data models and reduce the amount of time to develop with data operation in your project. Scaffolding provides an easier way to create view file and Controller action methods for Syncfusion® ASP.NET Core DataGrid, Charts, Scheduler, Diagram, Tree Grid, Rich Text Editor, Document Editor, and PDF Viewer controls. N>Check that at least one Entity Framework model exists. If no Entity Framework model exist in your application, refer to this [documentation](https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/adding-model?view=aspnetcore-3.1) to generate the Entity Framework model. After the model file has been added, check that the required DBContext and properties are added. Now, build the application, and try scaffolding. If any changes made in the model properties, rebuild the application once before perform scaffolding. @@ -113,15 +113,15 @@ The following steps explains how to add a scaffolded item from command-line to y ![CommandLine Scaffold](images/commandline.png) -5. As we can see controller and view files generated successfully and also added the Syncfusion® NuGet packages and styles which is required to render Syncfusion® control. +5. As we can see controller and view files generated successfully and also added the Syncfusion® NuGet packages and styles which is required to render Syncfusion® control. ![ASPNETCore added Files](images/Corefiles.png) ![ASPNETCore Service Changes](images/CoreScript.png) -## How to render Syncfusion® control? +## How to render Syncfusion® control? -Refer to the following UG links to render Syncfusion® control after performed scaffolding. +Refer to the following UG links to render Syncfusion® control after performed scaffolding. [Configure using Syncfusion.EJ2.AspNet.Core package](https://ej2.syncfusion.com/aspnetcore/documentation/getting-started/visual-studio-2017/) diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Notifications.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Notifications.md index baf55b2d..f02afe55 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Notifications.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Notifications.md @@ -1,49 +1,49 @@ --- layout: post title: Notifications | ASP.NET Core | Syncfusion -description: For displaying the notifications about trial and newer version update information for Syncfusion applications. +description: For displaying the notifications about trial and newer version update information for Syncfusion applications. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Notifications +# Syncfusion® Notifications -Syncfusion enhances the user experience in ASP.NET Core applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. +Syncfusion® enhances the user experience in ASP.NET Core applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. -N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. +N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. ## Notification Configuration -The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. +The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. -It can be accessed by clicking **Tools -> Options -> Syncfusion® -> ASP.NET Core** +It can be accessed by clicking **Tools -> Options -> Syncfusion® -> ASP.NET Core** ![Option Page](images/core-optionPage.png) ## Notification Types -**1. Syncfusion® Trial Application Notification** +**1. Syncfusion® Trial Application Notification** -When you utilize Syncfusion® trial assemblies in your ASP.NET Core application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion. +When you utilize Syncfusion® trial assemblies in your ASP.NET Core application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion®. ![Trial Notification](images/core-trial.png) -**2. Newer Syncfusion® NuGet Package Notification** +**2. Newer Syncfusion® NuGet Package Notification** -If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. +If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. ![NuGet Notification](images/core-nuget.png) -**3. Newer Essential Studio® Build Notification** +**3. Newer Essential Studio® Build Notification** -If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio ASP.NET Core - EJ2,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your ASP.NET Core development projects. +If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® ASP.NET Core - EJ2,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your ASP.NET Core development projects. ![Build Notification](images/core-build.png) **4. Invalid License Key Notification** -If you have mistakenly used an incorrect license key or used a license from another version or platform in your ASP.NET Core application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. +If you have mistakenly used an incorrect license key or used a license from another version or platform in your ASP.NET Core application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. ![Invalid Notification](images/core-invalid.png) diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Project-Templates.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Project-Templates.md index 37cd32e3..c112e86c 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Project-Templates.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Project-Templates.md @@ -1,43 +1,43 @@ --- layout: post title: Project Templates | ASP.NET Core (Essential JS 2) | Syncfusion -description: Syncfusion provides Visual Studio Project Templates for ASP.NET Core platform to create the Syncfusion ASP.NET Core Application using Essential JS 2 components +description: Syncfusion provides Visual Studio Project Templates for ASP.NET Core platform to create the Syncfusion ASP.NET Core Application using Essential JS 2 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Templates of ASP.NET Core (Essential JS 2) +# Syncfusion® Project Templates of ASP.NET Core (Essential® JS 2) -Syncfusion provides the **Visual Studio Project Templates** for the Syncfusion® ASP.NET Core platform to create the Syncfusion® ASP.NET Core Web Application using Essential® JS 2 components. +Syncfusion® provides the **Visual Studio Project Templates** for the Syncfusion® ASP.NET Core platform to create the Syncfusion® ASP.NET Core Web Application using Essential® JS 2 components. -> The Syncfusion® ASP.NET Core (Essential JS 2) project templates are available from v16.2.0.41. +> The Syncfusion® ASP.NET Core (Essential® JS 2) project templates are available from v16.2.0.41. -The following steps is used to create the **Syncfusion ASP.NET Core (Essential JS 2) Web Application** through the **Visual Studio Project Template**. +The following steps is used to create the **Syncfusion® ASP.NET Core (Essential® JS 2) Web Application** through the **Visual Studio Project Template**. -> Before use the Syncfusion® ASP.NET Core Project Template, check whether the **ASP.NET Core Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetcore/documentation/visual-studio-integration/download-and-installation) help topic. +> Before use the Syncfusion® ASP.NET Core Project Template, check whether the **ASP.NET Core Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetcore/documentation/visual-studio-integration/download-and-installation) help topic. -1. To create the Syncfusion® ASP.NET Core (Essential JS 2) project, follow either one of the options below: +1. To create the Syncfusion® ASP.NET Core (Essential® JS 2) project, follow either one of the options below: **Option 1** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET Core (EJ2) > Create New Syncfusion® Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ2) > Create New Syncfusion® Project…** in **Visual Studio**. ![new project](images/new-project.png) - > From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. + > From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. ![new project](images/SyncfusionMenu.png) **Option 2** - Choose **File > New > Project** and navigate to **Syncfusion > .NET Core > Syncfusion® ASP.NET Core (Essential JS 2) Web Application** in **Visual Studio**. + Choose **File > New > Project** and navigate to **Syncfusion® > .NET Core > Syncfusion® ASP.NET Core (Essential® JS 2) Web Application** in **Visual Studio**. - ![syncfusion template](images/syncfusion-template.png) + ![syncfusion® template](images/syncfusion-template.png) 2. Name the **Project**, choose the destination location, and then click **OK**. The Project Configuration Wizard appears. -3. Choose the options to configure the Syncfusion® ASP.NET Core (Essential JS 2) Application in the following Project Configuration dialog. +3. Choose the options to configure the Syncfusion® ASP.NET Core (Essential® JS 2) Application in the following Project Configuration dialog. ![project configuration](images/project-configuration.png) @@ -56,15 +56,15 @@ The following steps is used to create the **Syncfusion ASP.NET Core (Essential J | Angular | .NET 5.0, .NET 6.0, and .NET 7.0 | Material, Fabric, Fluent, Bootstrap, Bootstrap 4, Bootstrap 5, High Contrast, Tailwind CSS | CDN, NPM | | React | .NET 5.0, .NET 6.0, and .NET 7.0 | Material, Fabric, Fluent, Bootstrap, Bootstrap 4, Bootstrap 5, High Contrast, Tailwind CSS | CDN, NPM | - > The Syncfusion® ASP.NET Core (Essential® JS 2) Project Template provides ASP.NET Core, Angular, and React project templates support from v17.1.0.47. + > The Syncfusion® ASP.NET Core (Essential® JS 2) Project Template provides ASP.NET Core, Angular, and React project templates support from v17.1.0.47. **.NET Core Version**: Select the version of ASP.NET Core Project. ![.net core version](images/net-core-version.png) - **Assets From**: Load the Syncfusion® Essential® JS 2 assets to ASP.NET Core Project, either NPM, CDN, or Installed Location. + **Assets From**: Load the Syncfusion® Essential® JS 2 assets to ASP.NET Core Project, either NPM, CDN, or Installed Location. - > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. + > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. **Theme Selection**: Themes will be listed out based on the selected project type and choose the required theme from the available list. @@ -76,11 +76,11 @@ The following steps is used to create the **Syncfusion ASP.NET Core (Essential J ![authentication type](images/authentication.png) -4. Click Create, the Syncfusion® ASP.NET Core (Essential JS 2) Application has been created. +4. Click Create, the Syncfusion® ASP.NET Core (Essential® JS 2) Application has been created. ![css refernce](images/readme-file.PNG) -5. The required Syncfusion® NuGet/NPM packages, Scripts, and CSS have been added to the Project. +5. The required Syncfusion® NuGet/NPM packages, Scripts, and CSS have been added to the Project. **Web App and Web App (Model-View-Controller):** @@ -90,13 +90,13 @@ The following steps is used to create the **Syncfusion ASP.NET Core (Essential J **Angular:** - **NPM**: All the Syncfusion® Angular NPM packages entries will be added in package.json, it will automatically restore while build the application or save the package.json file before compile the project. + **NPM**: All the Syncfusion® Angular NPM packages entries will be added in package.json, it will automatically restore while build the application or save the package.json file before compile the project. **Styles**: CSS entries will be added in index.html based on the selected .NET Core version. **React:** - **NPM**: All the Syncfusion® React NPM packages entries will be added in package.json, it will automatically restore while build the application or save the package.json file before compile the project. + **NPM**: All the Syncfusion® React NPM packages entries will be added in package.json, it will automatically restore while build the application or save the package.json file before compile the project. **Styles**: CSS entries will be added in or index.html based on the selected project .Net Core version. @@ -104,9 +104,9 @@ The following steps is used to create the **Syncfusion ASP.NET Core (Essential J ![css refernce](images/project-structure.png) -6. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +6. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![syncfusion license](images/syncfusion-license.png) + ![syncfusion® license](images/syncfusion-license.png) ## Authentication Configuration diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/check-for-updates.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/check-for-updates.md index dc4e28f7..45d554bf 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/check-for-updates.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/check-for-updates.md @@ -1,28 +1,28 @@ --- layout: post title: Check for Updates | ASP.NET Core (Essential JS2) | Syncfusion -description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. +description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. platform: extension control: Visual Studio Extensions documentation: ug --- -# Check for updates in Syncfusion® ASP.NET Core +# Check for updates in Syncfusion® ASP.NET Core -Syncfusion provides the check for update extensions to find latest version of essential release was available, if it was available then provide option update most recent version of the Essential Studio® release. So that, you always get the latest features, fixes, and improvements by installing the latest version. +Syncfusion® provides the check for update extensions to find latest version of essential® release was available, if it was available then provide option update most recent version of the Essential Studio® release. So that, you always get the latest features, fixes, and improvements by installing the latest version. -> The Syncfusion® Check for updates is available from v17.1.0.32. +> The Syncfusion® Check for updates is available from v17.1.0.32. You can check updates availability in Visual Studio, and then install the update version if required. -1. Choose **Syncfusion > Check for Updates…** in the Visual Studio menu. +1. Choose **Syncfusion® > Check for Updates…** in the Visual Studio menu. ![Check for updates](images/check-for-updates.png) - > From Visual Studio 2019, Choose Extensions > Syncfusion® > Check for Updates… in the Visual Studio menu. + > From Visual Studio 2019, Choose Extensions > Syncfusion® > Check for Updates… in the Visual Studio menu. 2. When there is an update, **Update** dialog box opens ![update](images/update.png) -3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. \ No newline at end of file +3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. \ No newline at end of file diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/download-and-installation.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/download-and-installation.md index 097e0b2b..6a67457e 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/download-and-installation.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/download-and-installation.md @@ -1,20 +1,20 @@ --- layout: post title: Download and Installation | ASP.NET Core (Essential JS2) | Syncfusion -description: How to download and install the Syncfusion ASP.NET Core (Essential JS2) Visual Studio Extensions from Visual Studio Market Place +description: How to download and install the Syncfusion ASP.NET Core (Essential JS2) Visual Studio Extensions from Visual Studio Market Place platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -Syncfusion publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETCoreExtensions). You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. +Syncfusion® publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETCoreExtensions). You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. ## Prerequisites -The following software prerequisites must be installed to install the Syncfusion® ASP.NET Core extension, as well as to creating, adding snippet, converting, and upgrading Syncfusion® ASP.NET Core applications. +The following software prerequisites must be installed to install the Syncfusion® ASP.NET Core extension, as well as to creating, adding snippet, converting, and upgrading Syncfusion® ASP.NET Core applications. * [Visual Studio 2019 or later](https://visualstudio.microsoft.com/downloads). @@ -22,7 +22,7 @@ The following software prerequisites must be installed to install the Syncfusion ## Install through the Visual Studio Manage Extensions -The steps below assist you to how to install the Syncfusion® ASP.NET Core extensions from **Visual Studio Manage Extensions**. +The steps below assist you to how to install the Syncfusion® ASP.NET Core extensions from **Visual Studio Manage Extensions**. 1. Open the Visual Studio 2019. @@ -30,11 +30,11 @@ The steps below assist you to how to install the Syncfusion® extensions from the Visual Studio. +8. Now, under the menu **Extensions**, you can use the Syncfusion® extensions from the Visual Studio. ![SyncfusionMenu](images/SyncfusionMenu.png) ## Install from the Visual Studio Marketplace -The steps below illustrate how to download and install the Syncfusion® ASP.NET Core extension from the Visual Studio Marketplace. +The steps below illustrate how to download and install the Syncfusion® ASP.NET Core extension from the Visual Studio Marketplace. -1. Download the [Syncfusion ASP.NET Core Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETCoreExtensions) from the Visual Studio Marketplace. +1. Download the [Syncfusion® ASP.NET Core Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETCoreExtensions) from the Visual Studio Marketplace. 2. Close all Visual Studio instances running, if any. @@ -62,6 +62,6 @@ The steps below illustrate how to download and install the Syncfusion® extensions from the Visual Studio under the **Extensions** menu. +5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the **Extensions** menu. ![SyncfusionMenu](images/SyncfusionMenu.png) \ No newline at end of file diff --git a/Extension/ASPNETCore-Extension/Overview.md b/Extension/ASPNETCore-Extension/Overview.md index 975f72ee..d308eb48 100644 --- a/Extension/ASPNETCore-Extension/Overview.md +++ b/Extension/ASPNETCore-Extension/Overview.md @@ -1,9 +1,9 @@ --- layout: post title: ASP.NET Core (Essential JS 1) Extension | Extension | Syncfusion -description: An Extensions provide quick access to create or configure the Syncfusion ASP.NET Core projects along with Essential JS 1 components +description: An Extensions provide quick access to create or configure the Syncfusion ASP.NET Core projects along with Essential JS 1 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- @@ -11,35 +11,35 @@ documentation: ug ## Overview -The Syncfusion® ASP.NET Core (Essential JS 1) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® ASP.NET Core Extensions supports Microsoft Visual Studio 2017. +The Syncfusion® ASP.NET Core (Essential® JS 1) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® ASP.NET Core Extensions supports Microsoft Visual Studio 2017. -I> The Syncfusion® ASP.NET Core (Essential JS 1) menu option is available from v17.1.0.32. +I> The Syncfusion® ASP.NET Core (Essential® JS 1) menu option is available from v17.1.0.32. -The Syncfusion® provides the following extension supports in Visual Studio: +The Syncfusion® provides the following extension supports in Visual Studio: -1. [Syncfusion ASP.NET Core (Essential JS 1) Project Template](https://help.syncfusion.com/extension/aspnetcore-extension/syncfusion-project-templates): To create the Syncfusion® ASP.NET Core (Essential JS 1) application by adding the required Essential JS 1 components. -2. [Project Conversion](https://help.syncfusion.com/extension/aspnetcore-extension/project-conversion): To convert an existing ASP.NET Core application into a Syncfusion® ASP.NET Core (Essential JS 1) Web application by adding the required Syncfusion® assemblies and resource files. -3. [Migrate Project](https://help.syncfusion.com/extension/aspnetcore-extension/project-migration): Migrate the existing Syncfusion® ASP.NET Core Web Application from one Essential Studio® version to another version. -4. [Sample Creator](https://help.syncfusion.com/extension/aspnetcore-extension/sample-creator): Create the Syncfusion® ASP.NET Core (Essential JS 1) Projects with the required Syncfusion® configuration to start development with the required Syncfusion® controls. -5. [Troubleshooter](https://help.syncfusion.com/extension/syncfusion-troubleshooter/syncfusion-troubleshooter): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. +1. [Syncfusion® ASP.NET Core (Essential® JS 1) Project Template](https://help.syncfusion.com/extension/aspnetcore-extension/syncfusion-project-templates): To create the Syncfusion® ASP.NET Core (Essential® JS 1) application by adding the required Essential® JS 1 components. +2. [Project Conversion](https://help.syncfusion.com/extension/aspnetcore-extension/project-conversion): To convert an existing ASP.NET Core application into a Syncfusion® ASP.NET Core (Essential® JS 1) Web application by adding the required Syncfusion® assemblies and resource files. +3. [Migrate Project](https://help.syncfusion.com/extension/aspnetcore-extension/project-migration): Migrate the existing Syncfusion® ASP.NET Core Web Application from one Essential Studio® version to another version. +4. [Sample Creator](https://help.syncfusion.com/extension/aspnetcore-extension/sample-creator): Create the Syncfusion® ASP.NET Core (Essential® JS 1) Projects with the required Syncfusion® configuration to start development with the required Syncfusion® controls. +5. [Troubleshooter](https://help.syncfusion.com/extension/syncfusion-troubleshooter/syncfusion-troubleshooter): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. **No project selected in Visual Studio** -![Syncfusion Menu when No project selected in Visual Studio](Overview_images/Syncfusion_Menu_OverView1.png) +![Syncfusion® Menu when No project selected in Visual Studio](Overview_images/Syncfusion_Menu_OverView1.png) **Selected Microsoft ASP.NET Core application in Visual Studio** -![Syncfusion Menu when Selected Microsoft ASP.NET Core application in Visual Studio](Overview_images/Syncfusion_Menu_OverView2.png) +![Syncfusion® Menu when Selected Microsoft ASP.NET Core application in Visual Studio](Overview_images/Syncfusion_Menu_OverView2.png) -**Selected Syncfusion® ASP.NET Core (Essential JS1) application in Visual Studio** +**Selected Syncfusion® ASP.NET Core (Essential® JS1) application in Visual Studio** -![Syncfusion Menu when Selected Synfusion ASP.NET Core EJ1 application in Visual Studio](Overview_images/Syncfusion_Menu_OverView3.png) +![Syncfusion® Menu when Selected Synfusion ASP.NET Core EJ1 application in Visual Studio](Overview_images/Syncfusion_Menu_OverView3.png) -N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. +N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. -The Syncfusion® ASP.NET Core Visual Studio Extensions are installed along with the following setups, +The Syncfusion® ASP.NET Core Visual Studio Extensions are installed along with the following setups, -* Essential Studio® for Enterprise Edition with the platform ASP.NET Core -* Essential Studio® for ASP.NET Core +* Essential Studio® for Enterprise Edition with the platform ASP.NET Core +* Essential Studio® for ASP.NET Core diff --git a/Extension/ASPNETCore-Extension/Project-Conversion.md b/Extension/ASPNETCore-Extension/Project-Conversion.md index 76959fb5..631de03b 100644 --- a/Extension/ASPNETCore-Extension/Project-Conversion.md +++ b/Extension/ASPNETCore-Extension/Project-Conversion.md @@ -1,57 +1,57 @@ --- layout: post title: Project Conversion | ASP.NET Core (Essential JS 1) | Syncfusion -description: Project Conversion is a add-in that converts an existing ASP.NET Core project into Syncfusion ASP.NET Core project by adding required Essential JS 1 components +description: Project Conversion is a add-in that converts an existing ASP.NET Core project into Syncfusion ASP.NET Core project by adding required Essential JS 1 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Conversion +# Syncfusion® Project Conversion -Syncfusion Project Conversion is a Visual Studio add-in that converts an existing ASP.NET Core application into a Syncfusion® ASP.NET Core Web application by adding the required assemblies and resource files. +Syncfusion® Project Conversion is a Visual Studio add-in that converts an existing ASP.NET Core application into a Syncfusion® ASP.NET Core Web application by adding the required assemblies and resource files. -I> The Syncfusion® ASP.NET Core Web Application Project Conversion utility is available from v15.2.0.40. +I> The Syncfusion® ASP.NET Core Web Application Project Conversion utility is available from v15.2.0.40. -## Convert into Syncfusion® ASP.NET Core Web Application +## Convert into Syncfusion® ASP.NET Core Web Application -The following steps help you to use the Syncfusion® Project Conversion in the existing ASP.NET Core Web Application. +The following steps help you to use the Syncfusion® Project Conversion in the existing ASP.NET Core Web Application. -> Before use, the Syncfusion® ASP.NET Core (Essential JS 1) Project Conversion, check whether the **Syncfusion Essential® JS1 AspNet Core VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. +> Before use, the Syncfusion® ASP.NET Core (Essential® JS 1) Project Conversion, check whether the **Syncfusion® Essential® JS1 AspNet Core VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. 1. Open an existing Microsoft ASP.NET Core Web Application or create a new Microsoft ASP.NET Core Web Application. 2. To open Project Conversion Wizard, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET Core (EJ1) > Convert to Syncfusion® ASP.NET Core Application…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Convert to Syncfusion® ASP.NET Core Application…** in **Visual Studio**. - ![Syncfusion Essential JS 1 ASP.NET Core Project Conversion via Syncfusion® menu](Project-Conversion_images/Syncfusion_Menu_Project_Conversion.png) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project Conversion via Syncfusion® menu](Project-Conversion_images/Syncfusion_Menu_Project_Conversion.png) - N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Right-click the Project from Solution Explorer, select **Syncfusion Essential® JS 1**, and then choose **Convert to Syncfusion® ASP.NET Core (Essential JS 1) Application...** Refer to the following screenshot for more information. + Right-click the Project from Solution Explorer, select **Syncfusion® Essential® JS 1**, and then choose **Convert to Syncfusion® ASP.NET Core (Essential® JS 1) Application...** Refer to the following screenshot for more information. - ![Syncfusion Essential JS 1 ASP.NET Core Project Conversion add-in](Project-Conversion_images/Project-Conversion_img1.png) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project Conversion add-in](Project-Conversion_images/Project-Conversion_img1.png) 3. Project Conversion Wizard opens to configure the project. - ![Syncfusion Essential JS 1 ASP.NET Core Project Conversion wizard](Project-Conversion_images/Project-Conversion-img2.jpg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project Conversion wizard](Project-Conversion_images/Project-Conversion-img2.jpg) **Choose the assets from:** * Bower - Refer to the assets from Bower package manager. - * CDN - Refer to the assets from Syncfusion® CDN links. + * CDN - Refer to the assets from Syncfusion® CDN links. - * Installed Location - Refer to the assets from Syncfusion® installed locations. + * Installed Location - Refer to the assets from Syncfusion® installed locations. - ![Choose the required assets for Syncfusion Essential JS 1 ASP.NET Core project](Project-Conversion_images/Project-Conversion-img3.jpeg) + ![Choose the required assets for Syncfusion® Essential® JS 1 ASP.NET Core project](Project-Conversion_images/Project-Conversion-img3.jpeg) **Choose the Theme:** - The master page of project will be updated based on selected theme. The Theme Preview section shows the controls preview before convert into a Syncfusion® project + The master page of project will be updated based on selected theme. The Theme Preview section shows the controls preview before convert into a Syncfusion® project ![Choose the theme to apply on the master page of the ASP.NET Core project](Project-Conversion_images/Project-Conversion-img4.jpeg) @@ -60,33 +60,33 @@ The following steps help you to use the Syncfusion&re The localization culture files will be shipped into Scripts\ej\i18n directory of the project. ![Choose Copy Global Resources to ship the localization culture files for ASP.NET Core project](Project-Conversion_images/Project-Conversion-img14.jpeg) -4. Choose the required controls from Components section and Click the **Convert** button to convert it into a Syncfusion® Project. +4. Choose the required controls from Components section and Click the **Convert** button to convert it into a Syncfusion® Project. - ![Select the required components from the Components selection in the Syncfusion ASP.NET Core Project Conversion Wizard](Project-Conversion_images/ProjectConversion-img5.jpg) + ![Select the required components from the Components selection in the Syncfusion® ASP.NET Core Project Conversion Wizard](Project-Conversion_images/ProjectConversion-img5.jpg) - The **Project Backup** dialog will be opened. If click Yes it will backup the current project before converting it to Syncfusion® project. If click No it will convert the project to Syncfusion® project without backup. + The **Project Backup** dialog will be opened. If click Yes it will backup the current project before converting it to Syncfusion® project. If click No it will convert the project to Syncfusion® project without backup. - ![Syncfusion Essential JS 1 ASP.NET Core Project converson backup dialog](Project-Conversion_images/Project-Conversion-img6.jpg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project converson backup dialog](Project-Conversion_images/Project-Conversion-img6.jpg) -5. The required Syncfusion® NuGet/Bower packages, Scripts and CSS are included in the ASP.NET Core Web Application. Refer to the following screenshots for more information. +5. The required Syncfusion® NuGet/Bower packages, Scripts and CSS are included in the ASP.NET Core Web Application. Refer to the following screenshots for more information. - ![Required Syncfusion Essential JS 1 ASP.NET Core NuGet/Bower packages](Project-Conversion_images/Project-Conversion-img7.jpeg) + ![Required Syncfusion® Essential® JS 1 ASP.NET Core NuGet/Bower packages](Project-Conversion_images/Project-Conversion-img7.jpeg) - ![Required Syncfusion Essential JS 1 ASP.NET Core themes and scripts](Project-Conversion_images/Project-Conversion-img8.jpeg) + ![Required Syncfusion® Essential® JS 1 ASP.NET Core themes and scripts](Project-Conversion_images/Project-Conversion-img8.jpeg) -6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. +6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. -## Rendering Control after Syncfusion® ASP.NET Core Conversion +## Rendering Control after Syncfusion® ASP.NET Core Conversion -Once you converted your ASP.NET Core Web Application to Syncfusion® ASP.NET Core Web Application using Syncfusion® Visual Studio Extension, Perform the following steps to render the Syncfusion® controls to your project. +Once you converted your ASP.NET Core Web Application to Syncfusion® ASP.NET Core Web Application using Syncfusion® Visual Studio Extension, Perform the following steps to render the Syncfusion® controls to your project. -1. Include the Syncfusion control snippets to any of the view page of your project. Refer the following screenshot for more information. +1. Include the Syncfusion® control snippets to any of the view page of your project. Refer the following screenshot for more information. - ![Syncfusion Essential JS 1 ASP.NET Core datepicker control code snippet](Project-Conversion_images\Project-Conversion-img11.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core datepicker control code snippet](Project-Conversion_images\Project-Conversion-img11.jpeg) 2. Then run the project and the following output will be displayed. - ![Syncfusion Essential JS 1 ASP.NET Core datepicker control output](Project-Conversion_images\Project-Conversion-img12.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core datepicker control output](Project-Conversion_images\Project-Conversion-img12.jpeg) I> Refer all the required external and internal scripts only once in the page with proper order. Refer this [link](https://help.syncfusion.com/js/control-initialization#adding-the-required-javascript-files) to know about order of script reference. \ No newline at end of file diff --git a/Extension/ASPNETCore-Extension/Project-Migration.md b/Extension/ASPNETCore-Extension/Project-Migration.md index 0508fb49..1a9792b2 100644 --- a/Extension/ASPNETCore-Extension/Project-Migration.md +++ b/Extension/ASPNETCore-Extension/Project-Migration.md @@ -1,52 +1,52 @@ --- layout: post title: Project Migration | ASP.NET Core (Essential JS 1) | Syncfusion -description: Project Migration is a add-in that allows you to migrate existing Syncfusion ASP.NET Core Web Application from one Essential Studio version to another version +description: Project Migration is a add-in that allows you to migrate existing Syncfusion ASP.NET Core Web Application from one Essential Studio version to another version platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Migration for ASP.NET Core Web Application +# Syncfusion® Project Migration for ASP.NET Core Web Application -Syncfusion Project Migration is a Visual Studio add-in that allows you to migrate the existing Syncfusion® ASP.NET Core Web Application from one Essential Studio® version to another version. +Syncfusion® Project Migration is a Visual Studio add-in that allows you to migrate the existing Syncfusion® ASP.NET Core Web Application from one Essential Studio® version to another version. -I> The Syncfusion® ASP.NET Core Web Application Project Migration utility is available from v15.2.0.40. +I> The Syncfusion® ASP.NET Core Web Application Project Migration utility is available from v15.2.0.40. -## Migrate Syncfusion® Project +## Migrate Syncfusion® Project -The following steps help you to migrate your existing Syncfusion® ASP.NET Core Web Application. +The following steps help you to migrate your existing Syncfusion® ASP.NET Core Web Application. -> Before use, the Syncfusion® ASP.NET Core (Essential JS 1) Project Migration, check whether the **Syncfusion Essential® JS1 AspNet Core VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. +> Before use, the Syncfusion® ASP.NET Core (Essential® JS 1) Project Migration, check whether the **Syncfusion® Essential® JS1 AspNet Core VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio version® is not same for both the Extension and build, then the Project Migration will not be shown. 1. To open Migration Wizard, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET Core (EJ1) > Migrate Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Migrate Project…** in **Visual Studio**. - ![Syncfusion Essential JS 1 ASP.NET Core Project Migration via Syncfusion menu](Project-Migration_images/Syncfusion_Menu_Project_Migration.png) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project Migration via Syncfusion® menu](Project-Migration_images/Syncfusion_Menu_Project_Migration.png) - N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Right-click the **Syncfusion ASP.NET Core Web Application** from Solution Explorer and select **Syncfusion Essential® JS 1**. Choose **Migrate the Essential® JS 1 Project to Another Version...** + Right-click the **Syncfusion® ASP.NET Core Web Application** from Solution Explorer and select **Syncfusion® Essential® JS 1**. Choose **Migrate the Essential® JS 1 Project to Another Version...** - ![Syncfusion Essential JS 1 ASP.NET Core Project Migration add-in](Project-Migration_images/Project-Migration_img1.png) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project Migration add-in](Project-Migration_images/Project-Migration_img1.png) -2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine. +2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine. - ![Syncfusion Essential JS 1 ASP.NET Core Project Migration window](Project-Migration_images/Project-Migration-img2.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project Migration window](Project-Migration_images/Project-Migration-img2.jpeg) 3. The **Project Migration** window allows you to configure the following options: - i. **Essential Studio Version:** Select any version from the list of installed versions. + i. **Essential Studio® Version:** Select any version from the list of installed versions. - ii. **Assets From:** Load the Syncfusion® assets to ASP.NET Core Project, either Bower, CDN or Installed Location. + ii. **Assets From:** Load the Syncfusion® assets to ASP.NET Core Project, either Bower, CDN or Installed Location. -4. Click the Migrate Button. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before migrate the Syncfusion® project. If click No it will migrate the project to required Syncfusion® version without backup +4. Click the Migrate Button. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before migrate the Syncfusion® project. If click No it will migrate the project to required Syncfusion® version without backup - ![Syncfusion Essential JS 1 ASP.NET Core Project Migration backup dialog](Project-Migration_images/Project-Migration-img3.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project Migration backup dialog](Project-Migration_images/Project-Migration-img3.jpeg) -5. The Syncfusion® NuGet/Bower Packages, Scripts and CSS are updated to the corresponding version in the project. +5. The Syncfusion® NuGet/Bower Packages, Scripts and CSS are updated to the corresponding version in the project. -6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. \ No newline at end of file +6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNETCore-Extension/Sample-Creator.md b/Extension/ASPNETCore-Extension/Sample-Creator.md index f67200cb..862a093b 100644 --- a/Extension/ASPNETCore-Extension/Sample-Creator.md +++ b/Extension/ASPNETCore-Extension/Sample-Creator.md @@ -3,50 +3,50 @@ layout: post title: Sample Creator | ASP.NET Core (Essential JS 1) | Syncfusion description: Sample Creator is the utility that allows you to create Syncfusion ASP.NET Core Projects along with the samples based on Controls and Features selection platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Sample Creator -Sample Creator is the utility that allows you to create Syncfusion® ASP.NET Core Projects along with the samples based on Controls and Features selection. +Sample Creator is the utility that allows you to create Syncfusion® ASP.NET Core Projects along with the samples based on Controls and Features selection. -I> The Syncfusion® ASP.NET Core Sample Creator utility is available from v15.2.0.40. +I> The Syncfusion® ASP.NET Core Sample Creator utility is available from v15.2.0.40. -## Create Syncfusion® ASP.NET Core Web Application from Sample Creator +## Create Syncfusion® ASP.NET Core Web Application from Sample Creator -The following steps help you to create the Syncfusion® ASP.NET Core Web Application via the Sample Creator utility. +The following steps help you to create the Syncfusion® ASP.NET Core Web Application via the Sample Creator utility. -1. To launch ASP.NET Core (Essential® JS 1) Sample Creator application, follow either one of the options below: +1. To launch ASP.NET Core (Essential® JS 1) Sample Creator application, follow either one of the options below: **Option 1:** - Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Launch Sample Creator…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Launch Sample Creator…** in **Visual Studio**. - ![launch the Sample Creator via Syncfusion menu](Sample-Creator_images/Syncfusion_Menu_SampleCreator.png) + ![launch the Sample Creator via Syncfusion® menu](Sample-Creator_images/Syncfusion_Menu_SampleCreator.png) - N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Launch the Syncfusion® ASP.NET Core (Essential® JS 1) Control Panel. Select the Sample Creator button to launch the ASP.NET Core (Essential JS 1) Sample Creator application. Refer to the following screenshot for more information. + Launch the Syncfusion® ASP.NET Core (Essential® JS 1) Control Panel. Select the Sample Creator button to launch the ASP.NET Core (Essential® JS 1) Sample Creator application. Refer to the following screenshot for more information. - ![Syncfusion Essential Studio Essential JS 1 ASP.NET Core control panel to launch the Sample Creator](Sample-Creator_images/SampleCreator-img1.png) + ![Syncfusion® Essential Studio® Essential® JS 1 ASP.NET Core control panel to launch the Sample Creator](Sample-Creator_images/SampleCreator-img1.png) -2. Syncfusion® Sample Creator Wizard displaying the **Controls and its Feature Selection** section +2. Syncfusion® Sample Creator Wizard displaying the **Controls and its Feature Selection** section - ![Syncfusion Essential JS 1 ASP.NET Core Sample Creator wizard](Sample-Creator_images/SampleCreator-img2.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator wizard](Sample-Creator_images/SampleCreator-img2.jpeg) ### Controls Selection -Listed here are the Syncfusion® ASP.NET Core controls so you can choose the required controls. +Listed here are the Syncfusion® ASP.NET Core controls so you can choose the required controls. - ![Syncfusion Essential JS 1 ASP.NET Core Sample Creator Controls selection](Sample-Creator_images/SampleCreator-img3.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator Controls selection](Sample-Creator_images/SampleCreator-img3.jpeg) ### Feature Selection Based on the controls, the Feature is enabled to choose the features of the corresponding controls. - ![Syncfusion Essential JS 1 ASP.NET Core Sample Creator Features selection](Sample-Creator_images/SampleCreator-img4.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator Features selection](Sample-Creator_images/SampleCreator-img4.jpeg) ### Project Configuration @@ -61,31 +61,31 @@ Based on the controls, the Feature is enabled to choose the features of the corr * .NET Framework – Choose the .NET Framework version. - * Assets From – Load the Syncfusion® assets to ASP.NET Core Project, either Bower, CDN or Installed Location. + * Assets From – Load the Syncfusion® assets to ASP.NET Core Project, either Bower, CDN or Installed Location. - * Name – Name your Syncfusion® ASP.NET Core Application. + * Name – Name your Syncfusion® ASP.NET Core Application. * Location – Choose the target location of your project. - * Theme Selection – Choose the required theme.The Theme Preview section shows the controls preview before create the Syncfusion® project. + * Theme Selection – Choose the required theme.The Theme Preview section shows the controls preview before create the Syncfusion® project. - ![Syncfusion Essential JS 1 ASP.NET Core Sample Creator project configuration section](Sample-Creator_images/SampleCreator-img6.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator project configuration section](Sample-Creator_images/SampleCreator-img6.jpeg) -2. When you click the Create button, the new Syncfusion® ASP.NET Core project is created. The following resources are added in the project: +2. When you click the Create button, the new Syncfusion® ASP.NET Core project is created. The following resources are added in the project: * Added the required View(.cshtml) and Class files in the project. ![Required View and Class files add in the project for the chosen controls](Sample-Creator_images/SampleCreator-img7.jpeg) - * Included the required Syncfusion® scripts and themes files. + * Included the required Syncfusion® scripts and themes files. ![Required scripts and themes files included in the project](Sample-Creator_images/SampleCreator-img8.jpeg) - * Restored the required Syncfusion® NuGet/Bower packages for selected controls under dependencies. + * Restored the required Syncfusion® NuGet/Bower packages for selected controls under dependencies. - ![Required NuGet/Bower packages restored for the selected Syncfusion Essential JS 1 ASP.NET Core controls](Sample-Creator_images/SampleCreator-img9.jpeg) + ![Required NuGet/Bower packages restored for the selected Syncfusion® Essential® JS 1 ASP.NET Core controls](Sample-Creator_images/SampleCreator-img9.jpeg) 3. Once the project is created you can open the project by clicking the Yes button. If you click No button the corresponding location of the project will be opened. Refer the following screenshot for more information. - ![The project successfully created using Syncfusion Essential JS 1 ASP.NET Core Sample Creator](Sample-Creator_images/SampleCreator-img11.jpeg) + ![The project successfully created using Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator](Sample-Creator_images/SampleCreator-img11.jpeg) diff --git a/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md index 0905eb45..df0171da 100644 --- a/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md +++ b/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md @@ -1,43 +1,43 @@ --- layout: post title: Project Templates | ASP.NET Core (Essential JS 1) | Syncfusion -description: Syncfusion provides Visual Studio Project Templates for ASP.NET Core platform to create the Syncfusion ASP.NET Core Application using Essential JS 1 components +description: Syncfusion provides Visual Studio Project Templates for ASP.NET Core platform to create the Syncfusion ASP.NET Core Application using Essential JS 1 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Templates +# Syncfusion® Project Templates -Syncfusion provides the **Visual** **Studio** **Project** **Templates** for the Syncfusion® ASP.NET Core platform to create Syncfusion® ASP.NET Core Web Application. +Syncfusion® provides the **Visual** **Studio** **Project** **Templates** for the Syncfusion® ASP.NET Core platform to create Syncfusion® ASP.NET Core Web Application. -I> The Syncfusion® ASP.NET Core project templates are available from v15.2.0.40. +I> The Syncfusion® ASP.NET Core project templates are available from v15.2.0.40. -## Create Syncfusion® ASP.NET Core Application +## Create Syncfusion® ASP.NET Core Application -The following steps help you to create the **Syncfusion** **ASP****.****NET** **Core** **Application** through the **Visual** **Studio** **Project** **Template**. +The following steps help you to create the **Syncfusion®** **ASP****.****NET** **Core** **Application** through the **Visual** **Studio** **Project** **Template**. -> Before use the Syncfusion® ASP.NET Core (Essential JS 1) Project Template, check whether the **Syncfusion Essential® JS1 AspNet Core VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. +> Before use the Syncfusion® ASP.NET Core (Essential® JS 1) Project Template, check whether the **Syncfusion® Essential® JS1 AspNet Core VSExtensions** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. -1. To create a Syncfusion® ASP.NET Core (Essential JS 1) project, follow either one of the options below: +1. To create a Syncfusion® ASP.NET Core (Essential® JS 1) project, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET Core (EJ1) > Create New Syncfusion® Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion ASP.NET Core Application from Visual Studio New Project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion® ASP.NET Core Application from Visual Studio New Project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) - N>In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N>In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Choose **File > New > Project** and navigate to **Syncfusion > .NET Core > Syncfusion® ASP.NET Core (Essential JS 1) Web Application** in **Visual Studio**. + Choose **File > New > Project** and navigate to **Syncfusion® > .NET Core > Syncfusion® ASP.NET Core (Essential® JS 1) Web Application** in **Visual Studio**. - ![Choose Syncfusion ASP.NET Core Application from Visual Studio New Project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates_img1.png) + ![Choose Syncfusion® ASP.NET Core Application from Visual Studio New Project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates_img1.png) 2. Name the **Project**, choose the destination location when required and set the Framework of the project, then click **OK**. The Project Configuration Wizard appears. - N> Minimum target Framework is 4.5.2 for Syncfusion® ASP.NET Core Project Templates. + N> Minimum target Framework is 4.5.2 for Syncfusion® ASP.NET Core Project Templates. -3. Choose the options to configure the Syncfusion® ASP.NET Core Application by using the following Project Configuration dialog. +3. Choose the options to configure the Syncfusion® ASP.NET Core Application by using the following Project Configuration dialog. ### Project configurations: @@ -45,24 +45,24 @@ The following steps help you to create the **Syncfusion** **ASP****.****NET** ** **.NET Core Version:** Select the version of ASP.NET Core Project, either ASP.NET Core 1.0 or ASP.NET Core 1.1. - **Assets From:** Load the Syncfusion® assets to ASP.NET Core Project, either Bower, CDN or Installed Location. + **Assets From:** Load the Syncfusion® assets to ASP.NET Core Project, either Bower, CDN or Installed Location. **Theme Selection:** Choose the required Theme. - **Components:** Choose the Required Syncfusion® components to configure. + **Components:** Choose the Required Syncfusion® components to configure. - ![Syncfusion Essential JS 1 ASP.NET Core Project Configuration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img2.jpeg) + ![Syncfusion® Essential® JS 1 ASP.NET Core Project Configuration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img2.jpeg) -4. Once you click Create button, the Syncfusion® ASP.NET Core Application is created. +4. Once you click Create button, the Syncfusion® ASP.NET Core Application is created. -5. Required Syncfusion® NuGet/Bower packages, Scripts and CSS are added to the Project. +5. Required Syncfusion® NuGet/Bower packages, Scripts and CSS are added to the Project. - ![Required Syncfusion NuGet/Bower packages added to the Syncfusion Essential JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img3.jpeg) + ![Required Syncfusion® NuGet/Bower packages added to the Syncfusion® Essential® JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img3.jpeg) - ![Required Syncfusion Scripts and Themes added to the Syncfusion Essential JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.jpeg) + ![Required Syncfusion® Scripts and Themes added to the Syncfusion® Essential® JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.jpeg) -6. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +6. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration information for Syncfusion Essential JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) + ![Syncfusion® license registration information for Syncfusion® Essential® JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Overview.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Overview.md index 86059abc..e2d0899e 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Overview.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Overview.md @@ -1,31 +1,31 @@ --- layout: post title: ASP.NET MVC (Essential JS 2) Extension | Extension | Syncfusion -description: Syncfusion ASP.NET MVC (Essential JS2) Extensions create or configure the Syncfusion ASP.NET MVC projects along with Essential JS2 components. +description: Syncfusion ASP.NET MVC (Essential JS2) Extensions create or configure the Syncfusion ASP.NET MVC projects along with Essential JS2 components. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# ASP.NET MVC (Essential® JS 2) Extension +# ASP.NET MVC (Essential® JS 2) Extension -The Syncfusion® ASP.NET MVC (Essential® JS 2) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio. +The Syncfusion® ASP.NET MVC (Essential® JS 2) Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio. -> Syncfusion® Extension is published in the Visual Studio Marketplace. Refer to the following link. +> Syncfusion® Extension is published in the Visual Studio Marketplace. Refer to the following link. ## IMPORTANT -The Syncfusion® ASP.NET MVC (Essential® JS 2) menu option is available from v17.1.0.32. -Syncfusion provides the following supports in Visual Studio: +The Syncfusion® ASP.NET MVC (Essential® JS 2) menu option is available from v17.1.0.32. +Syncfusion® provides the following supports in Visual Studio: -[Project Template](syncfusion-project-templates): Creates the Syncfusion® ASP.NET MVC (Essential JS 2) application by adding the required Essential® JS 2 components. +[Project Template](syncfusion-project-templates): Creates the Syncfusion® ASP.NET MVC (Essential® JS 2) application by adding the required Essential® JS 2 components. -[Convert Project](project-conversion): Converts an existing ASP.NET MVC application into a Syncfusion® ASP.NET MVC (Essential JS 2) application by adding the required Syncfusion® assemblies and resource files. +[Convert Project](project-conversion): Converts an existing ASP.NET MVC application into a Syncfusion® ASP.NET MVC (Essential® JS 2) application by adding the required Syncfusion® assemblies and resource files. -[Upgrade Project](project-migration): Upgrades the existing Syncfusion® ASP.NET MVC (Essential JS 2) application from one Essential Studio® version to another version. +[Upgrade Project](project-migration): Upgrades the existing Syncfusion® ASP.NET MVC (Essential® JS 2) application from one Essential Studio® version to another version. -[Creator Sample](sample-creator): Creates the Syncfusion® ASP.NET MVC (Essential JS2) application with the sample code of required controls and features. +[Creator Sample](sample-creator): Creates the Syncfusion® ASP.NET MVC (Essential® JS2) application with the sample code of required controls and features. ### No project selected in Visual Studio @@ -35,8 +35,8 @@ Syncfusion provides the following supports in Visual Studio: ![selected microsoft aspmvc](images/selected-microsoft-mvc-application.png) -### Selected Syncfusion® ASP.NET MVC (Essential JS2) application in Visual Studio +### Selected Syncfusion® ASP.NET MVC (Essential® JS2) application in Visual Studio -![selected syncfusion aspnetmvc](images/selected-syncfusion-mvc-application.png) +![selected syncfusion® aspnetmvc](images/selected-syncfusion-mvc-application.png) -> From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. \ No newline at end of file +> From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. \ No newline at end of file diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Conversion.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Conversion.md index 53a5cceb..0dd252a1 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Conversion.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Conversion.md @@ -1,59 +1,59 @@ --- layout: post title: Project Conversion | ASP.NET MVC (Essential JS 2) | Syncfusion -description: Project Conversion is a add-in that converts an existing ASP.NET MVC project into a Syncfusion ASP.NET MVC project by adding required Essential JS 2 components +description: Project Conversion is a add-in that converts an existing ASP.NET MVC project into a Syncfusion ASP.NET MVC project by adding required Essential JS 2 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Conversion +# Syncfusion® Project Conversion -Syncfusion ASP.NET MVC conversion is a Visual Studio add-in that converts an existing ASP.NET MVC application into a Syncfusion® ASP.NET MVC (Essential JS 2) Web application by adding the required assemblies and resource files. +Syncfusion® ASP.NET MVC conversion is a Visual Studio add-in that converts an existing ASP.NET MVC application into a Syncfusion® ASP.NET MVC (Essential® JS 2) Web application by adding the required assemblies and resource files. -> The Syncfusion® ASP.NET MVC (Essential® JS 2) Web Application Project conversion utility is available from v16.3.0.17. Before use, the Syncfusion® ASP.NET MVC Project Conversion, check whether the **ASP.NET MVC Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetmvc/documentation/visual-studio-integration/download-and-installation) help topic. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. +> The Syncfusion® ASP.NET MVC (Essential® JS 2) Web Application Project conversion utility is available from v16.3.0.17. Before use, the Syncfusion® ASP.NET MVC Project Conversion, check whether the **ASP.NET MVC Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetmvc/documentation/visual-studio-integration/download-and-installation) help topic. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Conversion will not be shown. -The steps below help you to convert the ASP.NET MVC application to the Syncfusion® ASP.NET MVC application via the Visual Studio 2019: +The steps below help you to convert the ASP.NET MVC application to the Syncfusion® ASP.NET MVC application via the Visual Studio 2019: 1. Open an existing Microsoft ASP.NET MVC Web Application or create a new Microsoft ASP.NET MVC Web Application. -2. To open the Syncfusion® Project Conversion Wizard, follow either one of the options below: +2. To open the Syncfusion® Project Conversion Wizard, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET MVC > Convert to Syncfusion® ASP.NET MVC Application…** in **Visual Studio Menu**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC > Convert to Syncfusion® ASP.NET MVC Application…** in **Visual Studio Menu**. ![convert-to-syncfusion](images/convert-project.png) - > From Visual Studio 2019, Syncfusion® menu is available under **Extensions** in Visual Studio menu. + > From Visual Studio 2019, Syncfusion® menu is available under **Extensions** in Visual Studio menu. **Option 2:** - Right-click the **Project** from Solution Explorer, select **Syncfusion Web**, and choose the **Convert to Syncfusion® ASP.NET MVC Application…** Refer to the following screenshot for more information. + Right-click the **Project** from Solution Explorer, select **Syncfusion® Web**, and choose the **Convert to Syncfusion® ASP.NET MVC Application…** Refer to the following screenshot for more information. ![syncfusion-aspnet mvc](images/convert-syncfusion-aspmvc-application.png) -3. The Syncfusion® ASP.NET MVC Project Conversion window will appear. You can choose the required version of Syncfusion® ASP.NET MVC, Assets from, and Themes to convert the application. +3. The Syncfusion® ASP.NET MVC Project Conversion window will appear. You can choose the required version of Syncfusion® ASP.NET MVC, Assets from, and Themes to convert the application. ![project conversion wizard](images/project-conversion-wizard.png) - > The versions are loaded from the Syncfusion® ASP.NET MVC NuGet packages which published in [NuGet.org](https://www.nuget.org/packages?q=Tags%3A%22aspnetmvc%22syncfusion) and it requires internet connectivity. + > The versions are loaded from the Syncfusion® ASP.NET MVC NuGet packages which published in [NuGet.org](https://www.nuget.org/packages?q=Tags%3A%22aspnetmvc%22syncfusion) and it requires internet connectivity. The following configurations are used in the Project conversion wizard. - **Assets From**: Load the Syncfusion® Essential® JS 2 assets to ASP.NET MVC Project, from either NuGet, CDN, or Installed Location. + **Assets From**: Load the Syncfusion® Essential® JS 2 assets to ASP.NET MVC Project, from either NuGet, CDN, or Installed Location. - > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. + > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. **Choose the Theme**: Choose the required theme. 4. Check the **“Enable a backup before converting”** checkbox if you want to take the project backup and choose the location. -5. The required Syncfusion® NuGet packages, Scripts and CSS are included in the ASP.NET MVC Web Application. Refer to the following screenshots for more information. +5. The required Syncfusion® NuGet packages, Scripts and CSS are included in the ASP.NET MVC Web Application. Refer to the following screenshots for more information. - ![syncfusion assemblies](images/syncfusion-reference.png) + ![syncfusion® assemblies](images/syncfusion-reference.png) - ![syncfusion layout](images/layout.png) + ![syncfusion® layout](images/layout.png) ![web-config](images/web-config.png) @@ -61,4 +61,4 @@ The steps below help you to convert the ASP.NET MVC application to the Syncfusio ![BackupLocation](images/BackupLocation.png) -6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file +6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Migration.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Migration.md index 76f5e261..baffab2e 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Migration.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Migration.md @@ -1,56 +1,56 @@ --- layout: post title: Project Migration | ASP.NET MVC (Essential JS 2) | Syncfusion -description: Project Migration is a add-in that allows you to migrate the existing Syncfusion ASP.NET MVC Application from one Essential Studio version to another version +description: Project Migration is a add-in that allows you to migrate the existing Syncfusion ASP.NET MVC Application from one Essential Studio version to another version platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Upgrading Syncfusion® ASP.NET MVC application to latest version +# Upgrading Syncfusion® ASP.NET MVC application to latest version -The Syncfusion® ASP.NET MVC migration add-in for Visual Studio allows you to migrate an existing Syncfusion® ASP.NET MVC application from one version of Essential Studio® version to another version. This reduces the amount of manual work required when migrating the Syncfusion® version. +The Syncfusion® ASP.NET MVC migration add-in for Visual Studio allows you to migrate an existing Syncfusion® ASP.NET MVC application from one version of Essential Studio® version to another version. This reduces the amount of manual work required when migrating the Syncfusion version. ## IMPORTANT -The Syncfusion® ASP.NET MVC (Essential JS 2) Web Application Project Migration utility is available from v16.3.0.17. +The Syncfusion® ASP.NET MVC (Essential® JS 2) Web Application Project Migration utility is available from v16.3.0.17. -> Before use, the Syncfusion® ASP.NET MVC Project Migration, check whether the **ASP.NET MVC Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetmvc/documentation/visual-studio-integration/download-and-installation) help topic. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. +> Before use, the Syncfusion® ASP.NET MVC Project Migration, check whether the **ASP.NET MVC Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetmvc/documentation/visual-studio-integration/download-and-installation) help topic. Also, check whether the corresponding Essential Studio® version build installed or not. If the Essential Studio® version is not same for both the Extension and build, then the Project Migration will not be shown. -The steps below will assist you to upgrade the Syncfusion® version in the Syncfusion® ASP.NET MVC application via Visual Studio 2019: +The steps below will assist you to upgrade the Syncfusion® version in the Syncfusion® ASP.NET MVC application via Visual Studio 2019: -1. Open the Syncfusion® ASP.NET MVC application that uses the Syncfusion® component. +1. Open the Syncfusion® ASP.NET MVC application that uses the Syncfusion® component. 2. To open the Migration Wizard, either one of the following options should be followed: - **Option 1**: Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET MVC > Migrate Project…** in **Visual Studio Menu**. + **Option 1**: Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC > Migrate Project…** in **Visual Studio Menu**. ![migrate project](images/migrate-project.png) - > From Visual Studio 2019, Syncfusion® menu is available under **Extensions** in Visual Studio menu. + > From Visual Studio 2019, Syncfusion® menu is available under **Extensions** in Visual Studio menu. **Option 2**: - Right-click the **Syncfusion ASP.NET MVC Application** from Solution Explorer and select **Syncfusion Web**. Choose **Migrate the Syncfusion® ASP.NET MVC Project to Another Version…** + Right-click the **Syncfusion® ASP.NET MVC Application** from Solution Explorer and select **Syncfusion® Web**. Choose **Migrate the Syncfusion® ASP.NET MVC Project to Another Version…** - ![migrate the essential js2](images/migrate-essentialJs2.png) + ![migrate the essential® js2](images/migrate-essentialJs2.png) -3. The Syncfusion® Project Migration window will appear. You can choose the required version of Syncfusion® ASP.NET MVC to migrate. +3. The Syncfusion® Project Migration window will appear. You can choose the required version of Syncfusion® ASP.NET MVC to migrate. ![project migration](images/project-migration.png) - > The versions are loaded from the Syncfusion® ASP.NET MVC NuGet packages which published in [NuGet.org](https://www.nuget.org/packages?q=Tags%3A%22aspnetmvc%22syncfusion) and it requires internet connectivity. + > The versions are loaded from the Syncfusion® ASP.NET MVC NuGet packages which published in [NuGet.org](https://www.nuget.org/packages?q=Tags%3A%22aspnetmvc%22syncfusion) and it requires internet connectivity. - **Assets From:** Load the Syncfusion® Essential® JS 2 assets to ASP.NET MVC Project, from either NuGet, CDN or Installed Location. + **Assets From:** Load the Syncfusion® Essential® JS 2 assets to ASP.NET MVC Project, from either NuGet, CDN or Installed Location. - > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. + > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. 4. Check the **“Enable a backup before migrating”** checkbox if you want to take the project backup and choose location. -5. The Syncfusion® Reference Assemblies, Scripts, and CSS are updated to the selected version in the project. +5. The Syncfusion® Reference Assemblies, Scripts, and CSS are updated to the selected version in the project. if you enabled project backup before migrating, the old project was saved in the specified backup path location, as shown below once the migration process completed ![BackupLocation](images/BackupLocation.png) -6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file +6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Sample-Creator.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Sample-Creator.md index 31966319..00451b16 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Sample-Creator.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Sample-Creator.md @@ -1,37 +1,37 @@ --- layout: post title: Sample Creator | ASP.NET MVC (Essential JS 2) | Syncfusion -description: Sample Creator is a utility that allows you to create the Syncfusion ASP.NET MVC (Essential JS 2) Projects with required Syncfusion controls +description: Sample Creator is a utility that allows you to create the Syncfusion ASP.NET MVC (Essential JS 2) Projects with required Syncfusion controls platform: extension control: Syncfusion Extensions documentation: ug --- -# Creating Syncfusion® ASP.NET MVC application +# Creating Syncfusion® ASP.NET MVC application -The Syncfusion® Sample Creator is a tool that lets you make Syncfusion® ASP.NET MVC (Essential JS 2) projects with sample code for required Syncfusion® component features and Syncfusion® control configuration. +The Syncfusion® Sample Creator is a tool that lets you make Syncfusion® ASP.NET MVC (Essential® JS 2) projects with sample code for required Syncfusion® component features and Syncfusion® control configuration. -> The Syncfusion® ASP.NET MVC (Essential JS 2) Sample Creator utility is available from v16.3.0.17. +> The Syncfusion® ASP.NET MVC (Essential® JS 2) Sample Creator utility is available from v16.3.0.17. -Use the following steps to create the Syncfusion® ASP.NET MVC (Essential JS 2) Application through the Sample Creator utility: +Use the following steps to create the Syncfusion® ASP.NET MVC (Essential® JS 2) Application through the Sample Creator utility: -1. Follow one of the options below to launch the ASP.NET MVC (Essential JS 2) Sample Creator application: +1. Follow one of the options below to launch the ASP.NET MVC (Essential® JS 2) Sample Creator application: - **Option 1:** Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET MVC (EJ2) > Launch Sample Creator…** in **Visual Studio**. + **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ2) > Launch Sample Creator…** in **Visual Studio**. ![launch sample creator](images/launch-sample-creator.png) **Option 2:** - Launch the Syncfusion® ASP.NET MVC (Essential JS 2) Control Panel. Select the Sample Creator button to launch the ASP.NET MVC (Essential JS 2) Sample Creator application. Refer to the following screenshot for more information. + Launch the Syncfusion® ASP.NET MVC (Essential® JS 2) Control Panel. Select the Sample Creator button to launch the ASP.NET MVC (Essential® JS 2) Sample Creator application. Refer to the following screenshot for more information. ![sample creator application](images/sample-creator-application.png) -2. Syncfusion® controls and features are listed in the ASP.NET MVC (Essential JS 2) Sample Creator. +2. Syncfusion® controls and features are listed in the ASP.NET MVC (Essential® JS 2) Sample Creator. ![sample creator lists](images/sample-creator-list.png) - **Controls Selection**: Choose the required controls. The controls are grouped with Syncfusion® products. + **Controls Selection**: Choose the required controls. The controls are grouped with Syncfusion® products. ![control selection](images/control-selection.png) @@ -47,17 +47,17 @@ Use the following steps to create the Syncfusion® * **VS Version**: Choose the Visual Studio version and Framework. - * **View Engine**: By default, Syncfusion® supports only Razor view engine for ASP.NET MVC projects. + * **View Engine**: By default, Syncfusion® supports only Razor view engine for ASP.NET MVC projects. - * **Assets From**: Choose the Syncfusion® Essential® JS 2 assets to ASP.NET MVC Project, either NuGet, CDN or Installed Location. + * **Assets From**: Choose the Syncfusion® Essential® JS 2 assets to ASP.NET MVC Project, either NuGet, CDN or Installed Location. - > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. + > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. - * **Name**: Name your Syncfusion® ASP.NET MVC (Essential JS 2) Application. + * **Name**: Name your Syncfusion® ASP.NET MVC (Essential® JS 2) Application. * **Location**: Choose the target location of your project. - * **Theme Selection**: Choose the required theme. This section shows the controls preview before creating the Syncfusion® project. + * **Theme Selection**: Choose the required theme. This section shows the controls preview before creating the Syncfusion® project. ![sample creator theme selection](images/aspnet-mvc-samplecreator.png) @@ -65,16 +65,16 @@ Use the following steps to create the Syncfusion® ![create](images/sample-creator-create.png) -3. The new Syncfusion® ASP.NET MVC (Essential JS 2) project is created with the resources. +3. The new Syncfusion® ASP.NET MVC (Essential® JS 2) project is created with the resources. * Added the required Controllers and View files in the project. ![required controllers](images/required-controllers.png) - * Included the required Syncfusion® ASP.NET MVC (Essential JS 2) scripts and theme files. + * Included the required Syncfusion® ASP.NET MVC (Essential® JS 2) scripts and theme files. ![script-theme references](images/scripts-theme.png) - * The required Syncfusion® assemblies are added for selected controls under Project Reference. + * The required Syncfusion® assemblies are added for selected controls under Project Reference. - ![syncfusion assemblies](images/syncfusion-assemblies.png) + ![syncfusion® assemblies](images/syncfusion-assemblies.png) diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Scaffolding.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Scaffolding.md index 05f74485..8d12d83e 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Scaffolding.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Scaffolding.md @@ -1,52 +1,52 @@ --- layout: post title: Scaffolding | ASP.NET MVC (Essential JS 2) | Syncfusion -description: Code-generation Framework for Syncfusion ASP.NET MVC platform to quickly create the Controller and Views in a short time. +description: Code-generation Framework for Syncfusion ASP.NET MVC platform to quickly create the Controller and Views in a short time. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # ASP.NET MVC Scaffolding -Syncfusion provides **Visual Studio Scaffolding**for Syncfusion® ASP.NET MVC platform to quickly add code that interacts with data models and reduce the amount of time to develop with data operation in your project. Scaffolding provides an easier way to create Views and Controller action methods for Syncfusion® ASP.NET MVC DataGrid, Charts, and Scheduler controls. +Syncfusion® provides **Visual Studio Scaffolding**for Syncfusion® ASP.NET MVC platform to quickly add code that interacts with data models and reduce the amount of time to develop with data operation in your project. Scaffolding provides an easier way to create Views and Controller action methods for Syncfusion® ASP.NET MVC DataGrid, Charts, and Scheduler controls. -> The Syncfusion® ASP.NET MVC UI Scaffolder is available from v16.4.0.40. +> The Syncfusion® ASP.NET MVC UI Scaffolder is available from v16.4.0.40. The following steps explain you how to add a scaffolded item to your ASP.NET MVC Web application. -> Before use, the Syncfusion® ASP.NET MVC Scaffolding, check whether the **ASP.NET MVC Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetmvc/documentation/visual-studio-integration/VS2019-Extensions/download-and-installation/) help topic. +> Before use, the Syncfusion® ASP.NET MVC Scaffolding, check whether the **ASP.NET MVC Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetmvc/documentation/visual-studio-integration/VS2019-Extensions/download-and-installation/) help topic. 1. Right-click the **Controllers** folder in the Solution Explorer, click **Add**, and then select **New Scaffolded Item**. ![scaffolding item](images/scaffold-item.png) -2. In the **Add Scaffold** dialog, select **Syncfusion ASP.NET MVC UI Scaffolder**, and then click **‘Add’**. +2. In the **Add Scaffold** dialog, select **Syncfusion® ASP.NET MVC UI Scaffolder**, and then click **‘Add’**. - ![syncfusion aspnetmvc ui scaffolder](images/mvc-ui-scaffolder.png) + ![syncfusion® aspnetmvc ui scaffolder](images/mvc-ui-scaffolder.png) -3. In the Syncfusion® UI Scaffolding dialog, select the desired control to perform scaffolding, and then click **Next**. +3. In the Syncfusion® UI Scaffolding dialog, select the desired control to perform scaffolding, and then click **Next**. - ![syncfusion ui scaffolding](images/syncfusion-ui-scaffolding.png) + ![syncfusion® ui scaffolding](images/syncfusion-ui-scaffolding.png) -4. Selected control model dialogue will be launched in the Syncfusion® UI Scaffolder. Enter the **Controller Name** and **View Name** as application requirements, and then select the required **Model Class** of the active project and its relevant **Data Context Class**, and then click **Next**. +4. Selected control model dialogue will be launched in the Syncfusion® UI Scaffolder. Enter the **Controller Name** and **View Name** as application requirements, and then select the required **Model Class** of the active project and its relevant **Data Context Class**, and then click **Next**. - ![syncfusion ui scaffolding for datagrid](images/ui-scaffolding-datagrid.png) + ![syncfusion® ui scaffolding for datagrid](images/ui-scaffolding-datagrid.png) -5. Selected control feature dialogue will be launched in the Syncfusion® UI Scaffolder. Select the required features, update the required data field, and then click **Add**. +5. Selected control feature dialogue will be launched in the Syncfusion® UI Scaffolder. Select the required features, update the required data field, and then click **Add**. - ![syncfusion scaffolding add button](images/scaffolding-add-button.png) + ![syncfusion® scaffolding add button](images/scaffolding-add-button.png) -6. The **Controller** and the corresponding **View** files are now generated with the selected features of Syncfusion® control code snippet. +6. The **Controller** and the corresponding **View** files are now generated with the selected features of Syncfusion® control code snippet. ![controllers](images/controllers-view.png) -7. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. +7. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. > Ensure that at least one Entity Framework model exists, and the application has been compiled once. If no Entity Framework model exist in your application, refer to this [documentation](https://docs.microsoft.com/en-us/aspnet/mvc/overview/getting-started/database-first-development/creating-the-web-application#generate-the-models) to generate the Entity Framework model. After the model file has been added, ensure that the required DBContext and properties have been added. Now, build the application, and try scaffolding. If any changes have been done in the model properties, rebuild the application once before perform scaffolding. -Refer to the following UG links to render Syncfusion® control after performed scaffolding. +Refer to the following UG links to render Syncfusion® control after performed scaffolding. -MVC4: [Configure Essential JS 2 using Syncfusion.EJ2.MVC4 package](https://ej2.syncfusion.com/aspnetmvc/documentation/getting-started/visual-studio-2017/#configure-essential-js-2-in-the-application-1) +MVC4: [Configure Essential® JS 2 using Syncfusion.EJ2.MVC4 package](https://ej2.syncfusion.com/aspnetmvc/documentation/getting-started/visual-studio-2017/#configure-essential-js-2-in-the-application-1) -MVC5: [Configure Essential JS 2 using Syncfusion.EJ2.MVC5 package](https://ej2.syncfusion.com/aspnetmvc/documentation/getting-started/visual-studio-2017/#configure-essential-js-2-in-the-application) +MVC5: [Configure Essential® JS 2 using Syncfusion.EJ2.MVC5 package](https://ej2.syncfusion.com/aspnetmvc/documentation/getting-started/visual-studio-2017/#configure-essential-js-2-in-the-application) diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Notifications.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Notifications.md index aba42085..3b2c6e88 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Notifications.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Notifications.md @@ -1,49 +1,49 @@ --- layout: post title: Notifications | ASP.NET MVC (Essential JS2) | Syncfusion -description: For displaying the notifications about trial and newer version update information for Syncfusion applications. +description: For displaying the notifications about trial and newer version update information for Syncfusion applications. platform: extension control: Visual Studio Extensions documentation: ug --- -# Syncfusion® Notifications +# Syncfusion® Notifications -Syncfusion enhances the user experience in ASP.NET MVC applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. +Syncfusion® enhances the user experience in ASP.NET MVC applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. -N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. +N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. ## Notification Configuration -The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. +The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. -It can be accessed by clicking **Tools -> Options -> Syncfusion® -> ASP.NET MVC** +It can be accessed by clicking **Tools -> Options -> Syncfusion® -> ASP.NET MVC** ![Option Page](images/mvc-optionPage.png) ## Notification Types -**1. Syncfusion® Trial Application Notification** +**1. Syncfusion® Trial Application Notification** -When you utilize Syncfusion® trial assemblies in your ASP.NET MVC application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion. +When you utilize Syncfusion® trial assemblies in your ASP.NET MVC application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion®. ![Trial Notification](images/mvc-trial.png) -**2. Newer Syncfusion® NuGet Package Notification** +**2. Newer Syncfusion® NuGet Package Notification** -If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. +If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. ![NuGet Notification](images/mvc-nuget.png) -**3. Newer Essential Studio® Build Notification** +**3. Newer Essential Studio® Build Notification** -If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio ASP.NET MVC - EJ2,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your ASP.NET MVC development projects. +If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® ASP.NET MVC - EJ2,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your ASP.NET MVC development projects. ![Build Notification](images/mvc-build.png) **4. Invalid License Key Notification** -If you have mistakenly used an incorrect license key or used a license from another version or platform in your ASP.NET MVC application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. +If you have mistakenly used an incorrect license key or used a license from another version or platform in your ASP.NET MVC application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. ![Invalid Notification](images/mvc-invalid.png) diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md index 0fc9b261..9361dc85 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md @@ -1,43 +1,43 @@ --- layout: post title: Project Templates | ASP.NET MVC (Essential JS 2) | Syncfusion -description: Syncfusion provides Visual Studio Project Templates for ASP.NET MVC platform to create the Syncfusion ASP.NET MVC Application using Essential JS 2 components +description: Syncfusion provides Visual Studio Project Templates for ASP.NET MVC platform to create the Syncfusion ASP.NET MVC Application using Essential JS 2 components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Templates +# Syncfusion® Project Templates -Syncfusion provides the **Visual Studio Project Templates** for the Syncfusion® ASP.NET MVC platform to create the Syncfusion® ASP.NET MVC Web Application with the Essential JS 2 components. +Syncfusion® provides the **Visual Studio Project Templates** for the Syncfusion® ASP.NET MVC platform to create the Syncfusion® ASP.NET MVC Web Application with the Essential® JS 2 components. -> The Syncfusion® ASP.NET MVC (Essential JS 2) project templates are available from v16.2.0.41. +> The Syncfusion® ASP.NET MVC (Essential® JS 2) project templates are available from v16.2.0.41. -Use the following steps to create the **Syncfusion ASP.NET MVC (Essential JS 2) Web Application** through the **Visual Studio Project Template.** +Use the following steps to create the **Syncfusion® ASP.NET MVC (Essential® JS 2) Web Application** through the **Visual Studio Project Template.** -> Before use the Syncfusion® ASP.NET MVC Project Template, check whether the **ASP.NET MVC Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetmvc/documentation/visual-studio-integration/download-and-installation) help topic. +> Before use the Syncfusion® ASP.NET MVC Project Template, check whether the **ASP.NET MVC Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://ej2.syncfusion.com/aspnetmvc/documentation/visual-studio-integration/download-and-installation) help topic. -1. To create the Syncfusion® ASP.NET MVC (Essential JS 2) project, follow either one of the options below: +1. To create the Syncfusion® ASP.NET MVC (Essential® JS 2) project, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for ASP.NET MVC (EJ2) > Create New Syncfusion® Project…** in **Visual Studio 2019 earlier**. + Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ2) > Create New Syncfusion® Project…** in **Visual Studio 2019 earlier**. - ![create new syncfusion project](images/new-syncfusion-project.png) + ![create new syncfusion® project](images/new-syncfusion-project.png) - > From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. + > From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. ![SyncfusionMenu](images/SyncfusionMenu.png) **Option 2:** - Choose **File > New > Project** and navigate to **Syncfusion > Web > Syncfusion® ASP.NET MVC (Essential JS 2) Application** in **Visual Studio 2019 earlier**. + Choose **File > New > Project** and navigate to **Syncfusion® > Web > Syncfusion® ASP.NET MVC (Essential® JS 2) Application** in **Visual Studio 2019 earlier**. - ![syncfusion asp.net mvc](images/syncfusion-aspmvc-application.png) + ![syncfusion® asp.net mvc](images/syncfusion-aspmvc-application.png) - > In Visual Studio 2019, Syncfusion® ASP.NET MVC will be shown like below in solution explores. + > In Visual Studio 2019, Syncfusion® ASP.NET MVC will be shown like below in solution explores. - ![Syncfusion MVC Project Wizard](images/SyncfusionMvcProjectWizard.png) + ![Syncfusion® MVC Project Wizard](images/SyncfusionMvcProjectWizard.png) 2. Name the **Project**, choose the destination location, and set the .NET Framework of the project, and then click **OK**. The Project Configuration Wizard appears. @@ -47,24 +47,24 @@ Use the following steps to create the **Syncfusion ASP.NET MVC (Essential JS 2) **Target MVC Version**: Select the version of ASP.NET MVC Project, either MVC5 or MVC4. - **Theme Selection**: Choose the required Theme. The Theme Preview section shows the controls preview with selected theme before creating the Syncfusion® project. + **Theme Selection**: Choose the required Theme. The Theme Preview section shows the controls preview with selected theme before creating the Syncfusion® project. ![theme selection](images/theme-selection.png) - **Assets From**: : Load the Syncfusion® Essential® JS 2 assets to ASP.NET MVC Project, either NuGet, CDN, or Installed Location. + **Assets From**: : Load the Syncfusion® Essential® JS 2 assets to ASP.NET MVC Project, either NuGet, CDN, or Installed Location. - > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. + > Installed location option will be available only when the Syncfusion® Essential® JavaScript 2 setup has been installed. -3. Click **Create**, the Syncfusion® ASP.NET MVC (Essential JS 2) Application will be created. +3. Click **Create**, the Syncfusion® ASP.NET MVC (Essential® JS 2) Application will be created. ![readme-file](images/readme-file.PNG) -4. The required Syncfusion® NuGet packages, Scripts, and CSS have been added to the project. +4. The required Syncfusion® NuGet packages, Scripts, and CSS have been added to the project. ![nuget-package](images/nuget.png) ![css-script reference](images/css-scripts-reference.png) -5. Then, the Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post to learn more about the licensing changes introduced in Essential Studio®. +5. Then, the Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post to learn more about the licensing changes introduced in Essential Studio®. - ![syncfusion license](images/syncfusion-license.png) + ![syncfusion® license](images/syncfusion-license.png) diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/check-for-updates.md b/Extension/ASPNETMVC-EssentialJS2-Extension/check-for-updates.md index cf648f9c..f3ff91bc 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/check-for-updates.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/check-for-updates.md @@ -1,28 +1,28 @@ --- layout: post title: Check for Updates | ASP.NET MVC (Essential JS2) | Syncfusion -description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. +description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. platform: extension control: Visual Studio Extensions documentation: ug --- -# Check for updates in Syncfusion® ASP.NET MVC +# Check for updates in Syncfusion® ASP.NET MVC -Syncfusion provides the check for update extensions to find latest version of essential® release was available, if it was available then provide option update most recent version of the Essential Studio® release. So that, you always get the latest features, fixes, and improvements by installing the latest version. +Syncfusion® provides the check for update extensions to find latest version of essential® release was available, if it was available then provide option update most recent version of the Essential Studio® release. So that, you always get the latest features, fixes, and improvements by installing the latest version. -> The Syncfusion® Check for updates is available from v17.1.0.32. +> The Syncfusion® Check for updates is available from v17.1.0.32. You can check updates availability in Visual Studio, and then install the update version if required. -1. Choose **Syncfusion -> Check for updates…** in the Visual Studio menu. +1. Choose **Syncfusion® -> Check for updates…** in the Visual Studio menu. ![check for updates](images/check-for-updates.png) - > From Visual Studio 2019, Choose Extensions -> Syncfusion® -> Check for updates… in the Visual Studio menu. + > From Visual Studio 2019, Choose Extensions -> Syncfusion® -> Check for updates… in the Visual Studio menu. 2. When there is an update, **Update** dialog box opens. ![update dialog](images/update-dialog.png) -3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. \ No newline at end of file +3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. \ No newline at end of file diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/download-and-installation.md b/Extension/ASPNETMVC-EssentialJS2-Extension/download-and-installation.md index b29790be..3a1148fb 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/download-and-installation.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/download-and-installation.md @@ -3,24 +3,24 @@ layout: post title: Download and Installation | ASP.NET MVC (Essential JS2) | Syncfusion description: How to download and install the Syncfusion ASP.NET MVC (Essential JS2) Visual Studio Extensions from Visual Studio Market Place platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -Syncfusion publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETMVCExtensions). You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. +Syncfusion® publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETMVCExtensions). You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. ## Prerequisites -The following software prerequisites must be installed to install the Syncfusion® ASP.NET MVC extension, as well as to creating, adding snippet, converting, and upgrading Syncfusion® ASP.NET MVC applications. +The following software prerequisites must be installed to install the Syncfusion® ASP.NET MVC extension, as well as to creating, adding snippet, converting, and upgrading Syncfusion® ASP.NET MVC applications. * [Visual Studio 2013 or later](https://visualstudio.microsoft.com/downloads). ## Install through the Visual Studio Manage Extensions -The steps below assist you to how to install the Syncfusion® ASP.NET MVC extensions from **Visual Studio Manage Extensions**. +The steps below assist you to how to install the Syncfusion® ASP.NET MVC extensions from **Visual Studio Manage Extensions**. 1. Open the Visual Studio 2019. @@ -28,11 +28,11 @@ The steps below assist you to how to install the Syncfusion® extensions from the Visual Studio. +8. Now, under the menu **Extensions**, you can use the Syncfusion® extensions from the Visual Studio. ![SyncfusionMenu](images/SyncfusionMenu.png) ## Install from the Visual Studio Marketplace -The steps below illustrate how to download and install the Syncfusion® ASP.NET MVC extension from the Visual Studio Marketplace. +The steps below illustrate how to download and install the Syncfusion® ASP.NET MVC extension from the Visual Studio Marketplace. -1. Download the [Syncfusion ASP.NET MVC Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETMVCExtensions) from the Visual Studio Marketplace. +1. Download the [Syncfusion® ASP.NET MVC Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.ASPNETMVCExtensions) from the Visual Studio Marketplace. 2. Close all Visual Studio instances running, if any. @@ -60,6 +60,6 @@ The steps below illustrate how to download and install the Syncfusion® extensions from the Visual Studio under the **Extensions** menu. +5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the **Extensions** menu. ![SyncfusionMenu](images/SyncfusionMenu.png) \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md b/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md index ecfa4fdf..3790909a 100644 --- a/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md +++ b/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md @@ -1,65 +1,65 @@ --- layout: post title: Code Snippet | Blazor | Syncfusion -description: Code snippet adding a Syncfusion Blazor component with various features in the Razor code editor file of the Blazor Application. +description: Code snippet adding a Syncfusion Blazor component with various features in the Razor code editor file of the Blazor Application. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Add Syncfusion® Blazor component in the Blazor application +# Add Syncfusion® Blazor component in the Blazor application -The Syncfusion® Blazor code snippet utility for Visual Studio Code includes snippets for inserting a Syncfusion® Blazor component with various features into the Blazor Application's Razor code editor. +The Syncfusion® Blazor code snippet utility for Visual Studio Code includes snippets for inserting a Syncfusion® Blazor component with various features into the Blazor Application's Razor code editor. - > The Syncfusion® Blazor code snippet is available from Essential Studio® 2021 Volume 1 (`v19.1.0.54`). + > The Syncfusion® Blazor code snippet is available from Essential Studio® 2021 Volume 1 (`v19.1.0.54`). -## Add a Syncfusion® Blazor component +## Add a Syncfusion® Blazor component -The instructions below guide you the process of using the Syncfusion® Blazor code snippet in your Blazor application. +The instructions below guide you the process of using the Syncfusion® Blazor code snippet in your Blazor application. 1. In Visual Studio Code, open an existing Blazor Application or create a new Blazor Application. -2. Open the razor file that you need and place the cursor in required place where you want to add Syncfusion® component. +2. Open the razor file that you need and place the cursor in required place where you want to add Syncfusion® component. -3. You can find the Syncfusion® Blazor component with the various features by typing the **sf** word in the format shown below. +3. You can find the Syncfusion® Blazor component with the various features by typing the **sf** word in the format shown below. ```bash - sf- + sf- For Example, sfgrid-grouping ``` -4. Choose the Syncfusion® component and click the **Enter** or **Tab** key, the Syncfusion® Blazor component will be added in the razor file. +4. Choose the Syncfusion® component and click the **Enter** or **Tab** key, the Syncfusion® Blazor component will be added in the razor file. ![Code Snippet](images/codesnippet.gif) -5. After adding the Syncfusion® Blazor component to the razor file, use the tab key to fill in the required values to render the component with data. You can find the comment section in the code snippet to see what values are required. +5. After adding the Syncfusion® Blazor component to the razor file, use the tab key to fill in the required values to render the component with data. You can find the comment section in the code snippet to see what values are required. ![Comment](images/Comment.png) -6. You can also find the Syncfusion® help link at the top of the added snippet to learn more about the new Syncfusion® Blazor component feature. +6. You can also find the Syncfusion® help link at the top of the added snippet to learn more about the new Syncfusion® Blazor component feature. ![Help](images/Help.png) -## Configure Blazor application with Syncfusion +## Configure Blazor application with Syncfusion® -The Syncfusion® Blazor snippet simply inserts the code into the razor file. You must configure the Blazor application with Syncfusion® by installing the Syncfusion® Blazor NuGet package, namespace, themes, and registering the Syncfusion® Blazor Service. To configure, follow the steps below: +The Syncfusion® Blazor snippet simply inserts the code into the razor file. You must configure the Blazor application with Syncfusion® by installing the Syncfusion® Blazor NuGet package, namespace, themes, and registering the Syncfusion® Blazor Service. To configure, follow the steps below: -1. Open the Blazor application file and manually add the required Syncfusion® Blazor individual NuGet package(s) for the Syncfusion® Blazor components as a package reference. Refer to [this section](https://blazor.syncfusion.com/documentation/nuget-packages/#benefits-of-using-individual-nuget-packages) to learn about the advantages of the individual NuGet packages. This NuGet package will be automatically restored when building the application. +1. Open the Blazor application file and manually add the required Syncfusion® Blazor individual NuGet package(s) for the Syncfusion® Blazor components as a package reference. Refer to [this section](https://blazor.Syncfusion.com/documentation/nuget-packages/#benefits-of-using-individual-nuget-packages) to learn about the advantages of the individual NuGet packages. This NuGet package will be automatically restored when building the application. ![NuGet Package](images/NuGet-Snippet.png) - > Starting with Volume 4, 2020 (v18.4.0.30) release, Syncfusion® provides [individual NuGet packages](https://blazor.syncfusion.com/documentation/nuget-packages/) for our Syncfusion® Blazor components. We highly recommend this new standard for your Blazor production applications. + > Starting with Volume 4, 2020 (v18.4.0.30) release, Syncfusion® provides [individual NuGet packages](https://blazor.Syncfusion.com/documentation/nuget-packages/) for our Syncfusion® Blazor components. We highly recommend this new standard for your Blazor production applications. -2. To render the Syncfusion® components in your application, open the **~/_Imports.razor** file and add the required Syncfusion® Blazor namespace entries. +2. To render the Syncfusion® components in your application, open the **~/_Imports.razor** file and add the required Syncfusion® Blazor namespace entries. ![Namespace](images/Namespace-Snippet.png) -3. Add the Syncfusion® Blazor [theme](https://blazor.syncfusion.com/documentation/appearance/themes/) in the `` element of the **~/Pages/_Host.html** page for server application and **~/wwwroot/index.html** page for a client application. +3. Add the Syncfusion® Blazor [theme](https://blazor.Syncfusion.com/documentation/appearance/themes/) in the `` element of the **~/Pages/_Host.html** page for server application and **~/wwwroot/index.html** page for a client application. ![Themes](images/Themes-Snippet.png) -4. Open the **~/Startup.cs** file for server application and the **~/Program.cs** file for client application then register the Syncfusion® Blazor Service. +4. Open the **~/Startup.cs** file for server application and the **~/Program.cs** file for client application then register the Syncfusion® Blazor Service. - ![Syncfusion Configuration](images/Configuration-Snippet.png) + ![Syncfusion® Configuration](images/Configuration-Snippet.png) -5. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. \ No newline at end of file +5. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio-Code/convert-project.md b/Extension/Blazor-Extension/Visual-Studio-Code/convert-project.md index 20d3d55f..774fd5e0 100644 --- a/Extension/Blazor-Extension/Visual-Studio-Code/convert-project.md +++ b/Extension/Blazor-Extension/Visual-Studio-Code/convert-project.md @@ -1,23 +1,23 @@ --- layout: post title: Project Conversion | Blazor | Syncfusion -description: Project Conversion is a add-in that converts Blazor application into a Syncfusion Blazor application by adding required Syncfusion components +description: Project Conversion is a add-in that converts Blazor application into a Syncfusion Blazor application by adding required Syncfusion components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Blazor Conversion +# Syncfusion® Blazor Conversion -The Syncfusion® Blazor conversion is an add-in for Visual Studio Code that converts an existing Blazor application into a Syncfusion® Blazor Web Application by adding the required NuGet packages and themes. +The Syncfusion® Blazor conversion is an add-in for Visual Studio Code that converts an existing Blazor application into a Syncfusion® Blazor Web Application by adding the required NuGet packages and themes. - > The Syncfusion® Blazor Web Application Project Conversion utility is available from `v17.4.0.39`. + > The Syncfusion® Blazor Web Application Project Conversion utility is available from `v17.4.0.39`. -The steps below assist you to using the Syncfusion® Project conversion in your existing Blazor Web Application: +The steps below assist you to using the Syncfusion® Project conversion in your existing Blazor Web Application: 1. Open an existing Blazor Web Application or create a new Microsoft Blazor Web Application in Visual Studio Code. -2. Select **Convert to Syncfusion® Blazor Application...** from the context menu when you right-click on the **Project file** from Explorer (Workspace). Refer the screenshot below. +2. Select **Convert to Syncfusion® Blazor Application...** from the context menu when you right-click on the **Project file** from Explorer (Workspace). Refer the screenshot below. ![Conversion Add-in](images/Conversion.PNG) @@ -29,19 +29,19 @@ The steps below assist you to using the Syncfusion&re ![Select Themes](images/ChooseThemes.PNG) -5. The application configured with Syncfusion® Blazor required NuGet packages and themes. +5. The application configured with Syncfusion® Blazor required NuGet packages and themes. -6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. +6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. ## NuGet Packages Based on the application type, the following NuGet packages are added as NuGet references. -| Syncfusion® Blazor NuGet packages | Application type | +| Syncfusion® Blazor NuGet packages | Application type | |---|---| -| `Syncfusion.Blazor` | Syncfusion® Blazor Server App
Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)| -| `Syncfusion.Blazor.PdfViewerServer.Windows` | Syncfusion® Blazor Server App | -| `Syncfusion.Blazor.WordProcessor` | Syncfusion® Blazor Server App
Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)| +| `Syncfusion.Blazor` | Syncfusion® Blazor Server App
Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)| +| `Syncfusion.Blazor.PdfViewerServer.Windows` | Syncfusion® Blazor Server App | +| `Syncfusion.Blazor.WordProcessor` | Syncfusion® Blazor Server App
Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)| The NuGet packages added to the application file as follows. @@ -49,12 +49,12 @@ The NuGet packages added to the application file as follows. ## Theme links -While converting the application, the selected Syncfusion® Blazor theme is added in the following location of a Blazor type application. +While converting the application, the selected Syncfusion® Blazor theme is added in the following location of a Blazor type application. | Application type | File location | |---|---| -| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | -| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)| {Client Project location}\wwwroot\index.html | -| Syncfusion® Blazor WebAssembly App | {Project location}\wwwroot\index.html| +| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | +| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)| {Client Project location}\wwwroot\index.html | +| Syncfusion® Blazor WebAssembly App | {Project location}\wwwroot\index.html| ![CDNLink](images/CDNLink.png) \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio-Code/create-project.md b/Extension/Blazor-Extension/Visual-Studio-Code/create-project.md index 06a728d6..e30f948c 100644 --- a/Extension/Blazor-Extension/Visual-Studio-Code/create-project.md +++ b/Extension/Blazor-Extension/Visual-Studio-Code/create-project.md @@ -1,39 +1,39 @@ --- layout: post title: Project Templates | Blazor | Syncfusion -description: Syncfusion provides Visual Studio Code Project Templates for Blazor platform to create the Syncfusion Blazor Application using Syncfusion components +description: Syncfusion provides Visual Studio Code Project Templates for Blazor platform to create the Syncfusion Blazor Application using Syncfusion components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Create Project with Syncfusion® Blazor Template Studio +# Create Project with Syncfusion® Blazor Template Studio -Syncfusion provides **Visual Studio Code project templates** for creating Syncfusion® Blazor application. Syncfusion® Blazor generates application that include the necessary Syncfusion® NuGet packages, namespaces, and component render code for the Calendar, Button, and DataGrid components, as well as the style for making Syncfusion® component development easier. +Syncfusion® provides **Visual Studio Code project templates** for creating Syncfusion® Blazor application. Syncfusion® Blazor generates application that include the necessary Syncfusion® NuGet packages, namespaces, and component render code for the Calendar, Button, and DataGrid components, as well as the style for making Syncfusion® component development easier. -> Blazor project templates from `v17.4.0.39` are supported by the Syncfusion® Visual Studio Code project template. +> Blazor project templates from `v17.4.0.39` are supported by the Syncfusion® Visual Studio Code project template. -The instructions below assist you in creating **Syncfusion Blazor Applications** using **Visual Studio Code**: +The instructions below assist you in creating **Syncfusion® Blazor Applications** using **Visual Studio Code**: -1. To create a Syncfusion® Blazor application in Visual Studio Code, open the command palette by pressing **Ctrl+Shift+P**. Search for the word **Syncfusion** in the Visual Studio Code palette to get the templates provided by Syncfusion. +1. To create a Syncfusion® Blazor application in Visual Studio Code, open the command palette by pressing **Ctrl+Shift+P**. Search for the word **Syncfusion®** in the Visual Studio Code palette to get the templates provided by Syncfusion®. ![CreateProjectPalette](images/CreateBlazorProjectPalette.png) -2. Select **Syncfusion Blazor Template Studio: Launch**, then press **Enter** key. The Template Studio wizard for configuring the Syncfusion® Blazor app will be launched. Provide the Project Name and Project Path. +2. Select **Syncfusion® Blazor Template Studio: Launch**, then press **Enter** key. The Template Studio wizard for configuring the Syncfusion® Blazor app will be launched. Provide the Project Name and Project Path. ![TemplateStudioWizard](images/ProjectLocationName.png) -N> Refer to the .NET SDK support for Syncfusion® Blazor Components [here](https://blazor.syncfusion.com/documentation/system-requirements#net-sdk). +N> Refer to the .NET SDK support for Syncfusion® Blazor Components [here](https://blazor.Syncfusion.com/documentation/system-requirements#net-sdk). -3. Select either **Next** or the **Project Type** tab. Syncfusion® Blazor project types will be displayed. Choose one of the following Syncfusion® Blazor project types based on the version of the .NET SDK you are using. +3. Select either **Next** or the **Project Type** tab. Syncfusion® Blazor project types will be displayed. Choose one of the following Syncfusion® Blazor project types based on the version of the .NET SDK you are using. - | .NET SDK version | Supported Syncfusion® Blazor Application Type | + | .NET SDK version | Supported Syncfusion® Blazor Application Type | | ------------- | ------------- | - | [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) | Syncfusion® Blazor Web App | - | [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0), [.NET 7.0](https://dotnet.microsoft.com/en-us/download/dotnet/7.0), [.NET 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) | Syncfusion® Blazor WebAssembly App | - | [.NET 7.0](https://dotnet.microsoft.com/en-us/download/dotnet/7.0), [.NET 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) | Syncfusion® Blazor Server App | + | [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) | Syncfusion® Blazor Web App | + | [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0), [.NET 7.0](https://dotnet.microsoft.com/en-us/download/dotnet/7.0), [.NET 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) | Syncfusion® Blazor WebAssembly App | + | [.NET 7.0](https://dotnet.microsoft.com/en-us/download/dotnet/7.0), [.NET 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) | Syncfusion® Blazor Server App | - In the **Syncfusion Blazor Web App** application type, you can configure the following options: + In the **Syncfusion® Blazor Web App** application type, you can configure the following options: @@ -58,7 +58,7 @@ N> Refer to the .NET SDK support for Syncfusion®< ![WebAppTemplate](images/WebAppType.png) - In the **Syncfusion Blazor WebAssembly App** application type, you can choose ASP.NET Core hosted, Progressive Web Application, or both. + In the **Syncfusion® Blazor WebAssembly App** application type, you can choose ASP.NET Core hosted, Progressive Web Application, or both. ![ProjectType](images/ProjectTypeDetails.png) @@ -68,17 +68,17 @@ N> Refer to the .NET SDK support for Syncfusion®< > ASP.NET Core hosted and Progressive Web Application options are only visible if Blazor Web Assembly App project type is selected. -5. Click the **Create** button. The Syncfusion® Blazor application has been created. The created Syncfusion® Blazor app has the Syncfusion® NuGet packages, styles, and the component render code for the Syncfusion® component added to the Index, Counter, and FetchData pages. +5. Click the **Create** button. The Syncfusion® Blazor application has been created. The created Syncfusion® Blazor app has the Syncfusion® NuGet packages, styles, and the component render code for the Syncfusion® component added to the Index, Counter, and FetchData pages. -6. You can run the application to see the Syncfusion® components. Click **F5** or go to **Run>Start Debugging**. +6. You can run the application to see the Syncfusion® components. Click **F5** or go to **Run>Start Debugging**. ![Debug](images/Debug.png) -7. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. +7. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. -## Syncfusion® integration +## Syncfusion® integration -The Syncfusion® Blazor application configures with latest Syncfusion® Blazor NuGet packages, styles, namespaces, and component render code for Syncfusion® components are added in the created application. +The Syncfusion® Blazor application configures with latest Syncfusion® Blazor NuGet packages, styles, namespaces, and component render code for Syncfusion® components are added in the created application. ### NuGet Packages @@ -88,25 +88,25 @@ The `Syncfusion.Blazor` NuGet package will be added as NuGet references for all ### Style -The selected theme is added from Syncfusion® NuGet and its reference at these applications locations in Blazor. +The selected theme is added from Syncfusion® NuGet and its reference at these applications locations in Blazor. | Application type | File location | |---|---| -| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | -| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application) | {Client Project location}\wwwroot\index.html | -| Syncfusion® Blazor WebAssembly App | {Project location}\wwwroot\index.html| +| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | +| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application) | {Client Project location}\wwwroot\index.html | +| Syncfusion® Blazor WebAssembly App | {Project location}\wwwroot\index.html| ![CDNLink](images/CDNLink.png) ### Namespaces -The Syncfusion® Blazor namespaces are added in the **`_imports.razor`** file. +The Syncfusion® Blazor namespaces are added in the **`_imports.razor`** file. ![NameSpace](images/NameSpace.png) ### Component render code -The Syncfusion® Blazor Calendar, Button, and DataGrid component render code is in the Razor files in the pages folder. The render code is updated in these Razor files. +The Syncfusion® Blazor Calendar, Button, and DataGrid component render code is in the Razor files in the pages folder. The render code is updated in these Razor files. | File name | Code snippet added | |---|---| diff --git a/Extension/Blazor-Extension/Visual-Studio-Code/download-and-installation.md b/Extension/Blazor-Extension/Visual-Studio-Code/download-and-installation.md index c99f4385..a628bbb2 100644 --- a/Extension/Blazor-Extension/Visual-Studio-Code/download-and-installation.md +++ b/Extension/Blazor-Extension/Visual-Studio-Code/download-and-installation.md @@ -1,19 +1,19 @@ --- layout: post title: Download and Installation | Blazor | Syncfusion -description: How to download and install the Syncfusion Blazor Visual Studio Extensions from Visual Studio Market Place +description: How to download and install the Syncfusion Blazor Visual Studio Extensions from Visual Studio Market Place platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -Syncfusion® publishes the Visual Studio Code extension in the [Visual Studio Code marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-VSCode-Extensions). You can either install it directly from Visual Studio Code or download and install it from the Visual Studio Code marketplace. +Syncfusion® publishes the Visual Studio Code extension in the [Visual Studio Code marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-VSCode-Extensions). You can either install it directly from Visual Studio Code or download and install it from the Visual Studio Code marketplace. ## Prerequisites -The following software prerequisites must be installed to install the Syncfusion® Blazor extension, as well as to creating, adding component code, converting, and upgrading Syncfusion® Blazor applications. +The following software prerequisites must be installed to install the Syncfusion® Blazor extension, as well as to creating, adding component code, converting, and upgrading Syncfusion® Blazor applications. * [Visual Studio Code 1.29.0 or later](https://code.visualstudio.com/download) @@ -25,40 +25,40 @@ The following software prerequisites must be installed to install the Syncfusion ## Install through the Visual Studio Code Extensions -The instructions below describe the process of installing the Syncfusion® Blazor extensions from Visual Studio Code Extensions. +The instructions below describe the process of installing the Syncfusion® Blazor extensions from Visual Studio Code Extensions. 1. Open Visual Studio Code. 2. Navigate to **View > Extensions**, and the Manage Extensions option will appear on the left side of the window. -3. By entering the keyword **"Syncfusion Blazor"** in the search box, you can find the Syncfusion® Blazor Visual Studio Code extension in the Visual Studio Code Marketplace. +3. By entering the keyword **"Syncfusion® Blazor"** in the search box, you can find the Syncfusion® Blazor Visual Studio Code extension in the Visual Studio Code Marketplace. ![Extension](images/Extension.png) -4. Install the **"Blazor VSCode Extensions - Syncfusion"** extension by clicking the **Install** button. +4. Install the **"Blazor VSCode Extensions - Syncfusion®"** extension by clicking the **Install** button. 5. Reload Visual Studio Code after installation by using the **Reload Window** command in the Visual Studio Code palette. You can open the command palette by pressing **Ctrl+Shift+P** and find the Reload Window from Visual Studio Code commands. ![Reload-Window](images/Reload-Window.png) -6. Now, you can create a new Syncfusion® Blazor application by using the Syncfusion® Blazor extensions from the Visual Studio Code Palette Find the **Syncfusion Blazor Template Studio: Launch** from Visual Studio Code commands to open the Syncfusion® Blazor Template Studio wizard. +6. Now, you can create a new Syncfusion® Blazor application by using the Syncfusion® Blazor extensions from the Visual Studio Code Palette Find the **Syncfusion® Blazor Template Studio: Launch** from Visual Studio Code commands to open the Syncfusion® Blazor Template Studio wizard. ![CreateProjectPalette](images/CreateProjectPalette.png) ## Install from the Visual Studio Code Marketplace -The instructions below describe the process of downloading and installing Syncfusion® Blazor applications from the Visual Studio Code Marketplace. +The instructions below describe the process of downloading and installing Syncfusion® Blazor applications from the Visual Studio Code Marketplace. -1. Open [Syncfusion Blazor Code Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-VSCode-Extensions) in Visual Studio Code Marketplace. +1. Open [Syncfusion® Blazor Code Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-VSCode-Extensions) in Visual Studio Code Marketplace. -2. Click Install from Visual Studio Code Marketplace. The browser displays a popup window with information such as **"Open Visual Studio Code"**. When you click Open Visual Studio Code, the [Syncfusion Blazor Extension](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-VSCode-Extensions) will launch in Visual Studio Code. +2. Click Install from Visual Studio Code Marketplace. The browser displays a popup window with information such as **"Open Visual Studio Code"**. When you click Open Visual Studio Code, the [Syncfusion® Blazor Extension](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-VSCode-Extensions) will launch in Visual Studio Code. -3. Install the **"Blazor VSCode Extensions - Syncfusion"** extension by clicking the **Install** button. +3. Install the **"Blazor VSCode Extensions - Syncfusion®"** extension by clicking the **Install** button. 4. Reload Visual Studio Code after installation by using the **Reload Window** command in the Visual Studio Code palette. You can open the command palette by pressing **Ctrl+Shift+P** and find the Reload Window from Visual Studio Code commands. ![Reload-Window](images/Reload-Window.png) -5. Now, you can create a new Syncfusion® Blazor application by using the Syncfusion® Blazor extensions from the Visual Studio Code Palette Find the **Syncfusion Blazor Template Studio: Launch** from Visual Studio Code commands to open the Syncfusion® Blazor Template Studio wizard. +5. Now, you can create a new Syncfusion® Blazor application by using the Syncfusion® Blazor extensions from the Visual Studio Code Palette Find the **Syncfusion® Blazor Template Studio: Launch** from Visual Studio Code commands to open the Syncfusion® Blazor Template Studio wizard. ![CreateProjectPalette](images/CreateProjectPalette.png) \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio-Code/overview.md b/Extension/Blazor-Extension/Visual-Studio-Code/overview.md index e909b70f..f40eb3e7 100644 --- a/Extension/Blazor-Extension/Visual-Studio-Code/overview.md +++ b/Extension/Blazor-Extension/Visual-Studio-Code/overview.md @@ -1,22 +1,22 @@ --- layout: post title: Blazor VSCode Extension | Extension | Syncfusion -description: An Extension provides you with quick access so that you can create or configure the Syncfusion Blazor projects along with Syncfusion components +description: An Extension provides you with quick access so that you can create or configure the Syncfusion Blazor projects along with Syncfusion components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Blazor Extension for Visual Studio Code -The Syncfusion® Essential Studio® Blazor extension for Visual Studio Code simplifies the use of the Syncfusion® Blazor components by configuring the Syncfusion® Blazor NuGet packages and themes. +The Syncfusion® Essential Studio® Blazor extension for Visual Studio Code simplifies the use of the Syncfusion® Blazor components by configuring the Syncfusion® Blazor NuGet packages and themes. -The Syncfusion® Blazor provides the following support in Visual Studio Code: +The Syncfusion® Blazor provides the following support in Visual Studio Code: -[Project-Template](./create-project): Creates Syncfusion® Blazor applications with required configuration for development with Syncfusion® Blazor component. +[Project-Template](./create-project): Creates Syncfusion® Blazor applications with required configuration for development with Syncfusion® Blazor component. -[Code Snippet](./code-snippet): Adds a Syncfusion® Blazor component with various features to the Blazor Application's Razor code editor. +[Code Snippet](./code-snippet): Adds a Syncfusion® Blazor component with various features to the Blazor Application's Razor code editor. -[Convert project](./convert-project): Converts an existing Blazor Web Application to a Syncfusion® Blazor Web Application by importing the necessary Syncfusion® NuGet packages. +[Convert project](./convert-project): Converts an existing Blazor Web Application to a Syncfusion® Blazor Web Application by importing the necessary Syncfusion® NuGet packages. -[Upgrade project](./upgrade-project): Upgrades the existing Syncfusion® Blazor Web Application from one Essential Studio® version to another version. \ No newline at end of file +[Upgrade project](./upgrade-project): Upgrades the existing Syncfusion® Blazor Web Application from one Essential Studio® version to another version. \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio-Code/upgrade-project.md b/Extension/Blazor-Extension/Visual-Studio-Code/upgrade-project.md index 523c204b..bcfdc8a8 100644 --- a/Extension/Blazor-Extension/Visual-Studio-Code/upgrade-project.md +++ b/Extension/Blazor-Extension/Visual-Studio-Code/upgrade-project.md @@ -1,36 +1,36 @@ --- layout: post title: Project Migration | Blazor | Syncfusion -description: Project Migration is a add-in that helps migrate existing Syncfusion Blazor project from one Syncfusion version to another version +description: Project Migration is a add-in that helps migrate existing Syncfusion Blazor project from one Syncfusion version to another version platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Upgrading Syncfusion® Blazor application to latest version +# Upgrading Syncfusion® Blazor application to latest version -The Syncfusion® Blazor Migration is an add-in for Visual Studio Code allows you to migrate an existing Syncfusion® Blazor Web Application from one Essential Studio® version to another. +The Syncfusion® Blazor Migration is an add-in for Visual Studio Code allows you to migrate an existing Syncfusion® Blazor Web Application from one Essential Studio® version to another. - > The Syncfusion® Blazor Web Application Project Migration utility is available from `v17.4.0.39`. + > The Syncfusion® Blazor Web Application Project Migration utility is available from `v17.4.0.39`. -The steps below assist you to migrating existing Syncfusion® Blazor Web Application. +The steps below assist you to migrating existing Syncfusion® Blazor Web Application. -1. Open an existing Syncfusion® Blazor Web Application or create a new Syncfusion® Blazor Web Application in Visual Studio Code. +1. Open an existing Syncfusion® Blazor Web Application or create a new Syncfusion® Blazor Web Application in Visual Studio Code. -2. Select **Migrate Syncfusion® Blazor Application to another version...** from the context menu when you right-click on the **Project file** from Explorer (Workspace). Refer to the screenshot below. +2. Select **Migrate Syncfusion® Blazor Application to another version...** from the context menu when you right-click on the **Project file** from Explorer (Workspace). Refer to the screenshot below. ![Migration add-in](images/Migration.PNG) - > If you have a Syncfusion® Blazor reference in your application, the Migration option will be enabled. + > If you have a Syncfusion® Blazor reference in your application, the Migration option will be enabled. 3. **Select Blazor Version** (which published in `nuget.org`) from the palette appears. ![Select Blazor Version](images/VersionSelection.PNG) -4. The Syncfusion® NuGet packages references and themes are updated to the selected version in the application. +4. The Syncfusion® NuGet packages references and themes are updated to the selected version in the application. ![NuGetPackage](images/NuGetPackage.png) ![CDNLink](images/CDNLink.png) -5. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. \ No newline at end of file +5. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio/Syncfusion-Notifications.md b/Extension/Blazor-Extension/Visual-Studio/Syncfusion-Notifications.md index a3cc7d62..11a1d1ef 100644 --- a/Extension/Blazor-Extension/Visual-Studio/Syncfusion-Notifications.md +++ b/Extension/Blazor-Extension/Visual-Studio/Syncfusion-Notifications.md @@ -1,49 +1,49 @@ --- layout: post title: Notifications | Blazor | Syncfusion -description: For displaying the notifications about trial and newer version update information for Syncfusion applications. +description: For displaying the notifications about trial and newer version update information for Syncfusion applications. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Notifications +# Syncfusion® Notifications -Syncfusion enhances the user experience in Blazor applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. +Syncfusion® enhances the user experience in Blazor applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. -N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. +N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. ## Notification Configuration -The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. +The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. -It can be accessed by clicking **Tools -> Options -> Syncfusion® -> Blazor** +It can be accessed by clicking **Tools -> Options -> Syncfusion® -> Blazor** ![Option Page](images/blazor-optionPage.png) ## Notification Types -**1. Syncfusion® Trial Application Notification** +**1. Syncfusion® Trial Application Notification** -When you utilize Syncfusion® trial assemblies in your Blazor application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion. +When you utilize Syncfusion® trial assemblies in your Blazor application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion®. ![Trial Notification](images/blazor-trial.png) -**2. Newer Syncfusion® NuGet Package Notification** +**2. Newer Syncfusion® NuGet Package Notification** -If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. +If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. ![NuGet Notification](images/blazor-nuget.png) -**3. Newer Essential Studio® Build Notification** +**3. Newer Essential Studio® Build Notification** -If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio Blazor,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your Blazor development projects. +If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® Blazor,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your Blazor development projects. ![Build Notification](images/blazor-build.png) **4. Invalid License Key Notification** -If you have mistakenly used an incorrect license key or used a license from another version or platform in your Blazor application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. +If you have mistakenly used an incorrect license key or used a license from another version or platform in your Blazor application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. ![Invalid Notification](images/blazor-invalid.png) diff --git a/Extension/Blazor-Extension/Visual-Studio/code-generator.md b/Extension/Blazor-Extension/Visual-Studio/code-generator.md index d882b05d..e835f266 100644 --- a/Extension/Blazor-Extension/Visual-Studio/code-generator.md +++ b/Extension/Blazor-Extension/Visual-Studio/code-generator.md @@ -1,38 +1,38 @@ --- layout: post title: Code Generator | Blazor | Syncfusion -description: Syncfusion provides the Code Genearator for Blazor platform to add a Syncfusion Blazor component code in the Blazor application +description: Syncfusion provides the Code Genearator for Blazor platform to add a Syncfusion Blazor component code in the Blazor application platform: extension control: Syncfusion Extensions documentation: ug --- -# Add Syncfusion® Blazor component code +# Add Syncfusion® Blazor component code -Syncfusion provides the component Code Generator for the Blazor platform, which allows you to quickly add component code to the application at the required place in the razor file. The Syncfusion® extension adds the required Syncfusion® component to render the code with namespaces, styles, and NuGet references. The Code Generator is a simple wizard that interacts with data models and adds Syncfusion® components with the required features to your application. +Syncfusion® provides the component Code Generator for the Blazor platform, which allows you to quickly add component code to the application at the required place in the razor file. The Syncfusion® extension adds the required Syncfusion® component to render the code with namespaces, styles, and NuGet references. The Code Generator is a simple wizard that interacts with data models and adds Syncfusion® components with the required features to your application. -The steps below will assist you to add the Syncfusion® components code in your Blazor application through **Visual Studio 2019**: +The steps below will assist you to add the Syncfusion® components code in your Blazor application through **Visual Studio 2019**: -> Before using the Syncfusion® Blazor Code Generator, check whether the Syncfusion® Blazor Extension is installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://blazor.syncfusion.com/documentation/visual-studio-integration/visual-studio-extensions/download-and-installation/) help topic. +> Before using the Syncfusion® Blazor Code Generator, check whether the Syncfusion® Blazor Extension is installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://blazor.Syncfusion.com/documentation/visual-studio-integration/visual-studio-extensions/download-and-installation/) help topic. 1. Open your existing Blazor application or create a new Blazor application. -2. To open the Syncfusion® Blazor Code Generator Wizard, select one of the options below in the Razor file, and then add Syncfusion® components: +2. To open the Syncfusion® Blazor Code Generator Wizard, select one of the options below in the Razor file, and then add Syncfusion® components: **Option 1:** - To generate a specific component code, right-click on the editor of the Razor file at the required line and Select the **Syncfusion Blazor Code Generator...** + To generate a specific component code, right-click on the editor of the Razor file at the required line and Select the **Syncfusion® Blazor Code Generator...** ![CodeGeneratorCommand](images/Code-Generator-Command.PNG) **Option 2:** - Open the .razor file and choose **Extension -> Syncfusion® -> Essential Studio® for Blazor -> Syncfusion® Blazor Code Generator...** from the **Visual Studio 2019 menu**. + Open the .razor file and choose **Extension -> Syncfusion® -> Essential Studio® for Blazor -> Syncfusion® Blazor Code Generator...** from the **Visual Studio 2019 menu**. ![CodeGeneratorMenu](images/Code-Generator-Menu.PNG) -3. The wizard for the Syncfusion® Blazor Code Generator will appear. Choose a required control. +3. The wizard for the Syncfusion® Blazor Code Generator will appear. Choose a required control. ![CodeGeneratorWizard](images/Code-Generator-MainWizard.png) @@ -46,33 +46,33 @@ The steps below will assist you to add the Syncfusion ![ComponentRenderCode](images/Code-Generator-ComponentRenderCode.PNG) -4. In the Output window, select the **Syncfusion Blazor Code Generator** from the **“Show output from”** drop-down to see the changes made to your application. +4. In the Output window, select the **Syncfusion® Blazor Code Generator** from the **“Show output from”** drop-down to see the changes made to your application. ![OutputWindow](images/Code-Generator-OutputWindow.PNG) -5. If you have installed the trial setup or NuGet packages from nuget.org, you must register the Syncfusion® license key to your application as Syncfusion® has introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post to know more about the licensing changes introduced in Essential Studio. +5. If you have installed the trial setup or NuGet packages from nuget.org, you must register the Syncfusion® license key to your application as Syncfusion® has introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post to know more about the licensing changes introduced in Essential Studio®. -## Syncfusion® integration +## Syncfusion® integration -The created Syncfusion® Blazor application have the most recent Syncfusion® Blazor NuGet packages, styles, namespaces, and component render code for Syncfusion® components. +The created Syncfusion® Blazor application have the most recent Syncfusion® Blazor NuGet packages, styles, namespaces, and component render code for Syncfusion® components. ### NuGet Packages -Based on the selected Syncfusion® Blazor controls, the individual NuGet packages can be added as NuGet references. Refer [this topic](https://blazor.syncfusion.com/staging/documentation/nuget-packages/) to know about the individual Blazor NuGet packages. +Based on the selected Syncfusion® Blazor controls, the individual NuGet packages can be added as NuGet references. Refer [this topic](https://blazor.Syncfusion.com/staging/documentation/nuget-packages/) to know about the individual Blazor NuGet packages. -> The latest Syncfusion® Essential Studio® version of a NuGet package will be added as reference entry from nuget.org if there is no internet connection. You should restore the NuGet packages when internet becomes available. +> The latest Syncfusion® Essential Studio® version of a NuGet package will be added as reference entry from nuget.org if there is no internet connection. You should restore the NuGet packages when internet becomes available. ![NuGetPackage](images/Code-Generator-NuGetPackage.PNG) ### Style -The selected Syncfusion® Blazor theme is added from Syncfusion® NuGet and this theme reference will be added at these applications locations in Blazor. +The selected Syncfusion® Blazor theme is added from Syncfusion® NuGet and this theme reference will be added at these applications locations in Blazor. | Application type | File location | |---|---| -| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | -| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application) | {Client Project location}\wwwroot\index.html | -| Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (Progressive Web Application) | {Project location}\wwwroot\index.html| +| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | +| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application) | {Client Project location}\wwwroot\index.html | +| Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (Progressive Web Application) | {Project location}\wwwroot\index.html| ![StyleReference](images/Code-Generator-CDNLink.PNG) diff --git a/Extension/Blazor-Extension/Visual-Studio/convert-project.md b/Extension/Blazor-Extension/Visual-Studio/convert-project.md index 36efed98..cc6429e5 100644 --- a/Extension/Blazor-Extension/Visual-Studio/convert-project.md +++ b/Extension/Blazor-Extension/Visual-Studio/convert-project.md @@ -1,41 +1,41 @@ --- layout: post title: Project Conversion | Blazor | Syncfusion -description: Project Conversion is a add-in that converts Blazor application into a Syncfusion Blazor application by adding required Syncfusion components +description: Project Conversion is a add-in that converts Blazor application into a Syncfusion Blazor application by adding required Syncfusion® components platform: extension -control: Syncfusion Extensions +control: Syncfusion® Extensions documentation: ug --- -# Converting Blazor application to Syncfusion® Blazor application +# Converting Blazor application to Syncfusion® Blazor application -Syncfusion Blazor conversion is a Visual Studio add-in that converts an existing Blazor application to the Syncfusion® Blazor application by adding the required assemblies and theme files. +Syncfusion® Blazor conversion is a Visual Studio add-in that converts an existing Blazor application to the Syncfusion® Blazor application by adding the required assemblies and theme files. -The steps below help you to convert the **Blazor application** to the **Syncfusion Blazor application** via the **Visual Studio 2019**: +The steps below help you to convert the **Blazor application** to the **Syncfusion® Blazor application** via the **Visual Studio 2019**: -> Before use the Syncfusion® Blazor Project Conversion, check whether the Syncfusion® Blazor Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://blazor.syncfusion.com/documentation/visual-studio-integration/visual-studio-extensions/download-and-installation/) help topic. +> Before use the Syncfusion® Blazor Project Conversion, check whether the Syncfusion® Blazor Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://blazor.Syncfusion.com/documentation/visual-studio-integration/visual-studio-extensions/download-and-installation/) help topic. 1. Open your existing Blazor application or create a new Blazor application -2. To open the Syncfusion® Project Conversion Wizard, follow either one of the options below: +2. To open the Syncfusion® Project Conversion Wizard, follow either one of the options below: **Option 1:** - Choose **Extensions -> Syncfusion® -> Essential Studio® for Blazor -> Convert Project...** in the Visual Studio 2019 menu. + Choose **Extensions -> Syncfusion® -> Essential Studio® for Blazor -> Convert Project...** in the Visual Studio 2019 menu. ![ConversionMenu](images/ConversionMenu.png) **Option 2:** - Right-click the application from the **Solution Explorer** and select the **Syncfusion Blazor** and choose the **Convert to Syncfusion® Blazor application...** + Right-click the application from the **Solution Explorer** and select the **Syncfusion® Blazor** and choose the **Convert to Syncfusion® Blazor application...** ![ConversionAddin](images/ConversionAddin.png) -3. The Syncfusion® Blazor Project Conversion window will appear. You can choose the required version of Syncfusion® Blazor and Themes to convert the application. +3. The Syncfusion® Blazor Project Conversion window will appear. You can choose the required version of Syncfusion® Blazor and Themes to convert the application. ![ConversionWizard](images/Conversion.png) - > The versions are loaded from the Syncfusion® Blazor NuGet packages published in [`NuGet.org`](https://www.nuget.org/packages?q=Tags%3A%22blazor%22syncfusion) and it requires internet connectivity. + > The versions are loaded from the Syncfusion® Blazor NuGet packages published in [`NuGet.org`](https://www.nuget.org/packages?q=Tags%3A%22blazor%22syncfusion) and it requires internet connectivity. 4. Check the **“Enable a backup before converting”** checkbox if you want to take the project backup and choose the location. @@ -47,17 +47,17 @@ The steps below help you to convert the **Blazor application** to the **Syncfusi ![ConversionBackupLocation](images/Backuplocation.png) -6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. +6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion®-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. ## NuGet Packages Based on the application type, the following NuGet packages are added as NuGet references. -| Syncfusion® Blazor NuGet packages | Application type | +| Syncfusion® Blazor NuGet packages | Application type | |---|---| -| `Syncfusion.Blazor` | Syncfusion® Blazor Server App
Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application)| -| `Syncfusion.Blazor.PdfViewerServer.Windows` | Syncfusion® Blazor Server App | -| `Syncfusion.Blazor.WordProcessor` | Syncfusion® Blazor Server App
Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application)| +| `Syncfusion.Blazor` | Syncfusion® Blazor Server App
Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application)| +| `Syncfusion.Blazor.PdfViewerServer.Windows` | Syncfusion® Blazor Server App | +| `Syncfusion.Blazor.WordProcessor` | Syncfusion® Blazor Server App
Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (Progressive Web Application)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application)| The NuGet packages added to the application file as follows. @@ -65,12 +65,12 @@ The NuGet packages added to the application file as follows. ## Theme link -While converting the application, the Syncfusion® Blazor theme is added in the following location of a Blazor application. +While converting the application, the Syncfusion® Blazor theme is added in the following location of a Blazor application. | Application type | File location | |---|---| -| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | -| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application) | {Client Project location}\wwwroot\index.html | -| Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (Progressive Web Application) | {Project location}\wwwroot\index.html| +| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | +| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application) | {Client Project location}\wwwroot\index.html | +| Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (Progressive Web Application) | {Project location}\wwwroot\index.html| ![CDNLink](images/CDNLink.png) \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio/download-and-installation.md b/Extension/Blazor-Extension/Visual-Studio/download-and-installation.md index cf216f9f..3ad4b840 100644 --- a/Extension/Blazor-Extension/Visual-Studio/download-and-installation.md +++ b/Extension/Blazor-Extension/Visual-Studio/download-and-installation.md @@ -1,19 +1,19 @@ --- layout: post title: Download and Installation | Blazor | Syncfusion -description: How to download and install the Syncfusion Blazor Visual Studio Extensions from Visual Studio Market Place +description: How to download and install the Syncfusion Blazor Visual Studio Extensions from Visual Studio Market Place platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -Syncfusion publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-Extension). You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. +Syncfusion® publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-Extension). You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. ## Prerequisites -The following software prerequisites must be installed to install the Syncfusion® Blazor extension, as well as to creating, adding snippet, converting, and upgrading Syncfusion® Blazor applications. +The following software prerequisites must be installed to install the Syncfusion® Blazor extension, as well as to creating, adding snippet, converting, and upgrading Syncfusion® Blazor applications. * [Visual Studio 2019 16.3 or later](https://visualstudio.microsoft.com/downloads). @@ -21,17 +21,17 @@ The following software prerequisites must be installed to install the Syncfusion ## Install through the Visual Studio Manage Extensions -The steps below assist you to how to install the Syncfusion® Blazor extensions from **Visual Studio Manage Extensions**. +The steps below assist you to how to install the Syncfusion® Blazor extensions from **Visual Studio Manage Extensions**. 1. Open the Visual Studio 2019. 2. Navigate to **Extension ->Manage Extensions** and open the Manage Extensions. -3. On the left, click the **Online** tab and type **"Syncfusion Blazor"** in the **search box**. +3. On the left, click the **Online** tab and type **"Syncfusion® Blazor"** in the **search box**. ![Online-Manage-Extension-window](images/OnlineExtension.png) -4. Click the **Download** button in the **“Syncfusion Blazor Template Studio”** extensions. +4. Click the **Download** button in the **“Syncfusion® Blazor Template Studio”** extensions. 5. Close all Visual Studio instances after downloading the extensions to begin the installation process. You will see the following VSIX installation prompt. @@ -41,15 +41,15 @@ The steps below assist you to how to install the Syncfusion® extensions from the Visual Studio. +8. Now, under the menu **Extensions**, you can use the Syncfusion® extensions from the Visual Studio. ![SyncfusionMenu](images/SyncfusionMenu.png) ## Install from the Visual Studio Marketplace -The steps below illustrate how to download and install the Syncfusion® Blazor extension from the Visual Studio Marketplace. +The steps below illustrate how to download and install the Syncfusion® Blazor extension from the Visual Studio Marketplace. -1. Download the [Syncfusion Blazor Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-Extension) from the Visual Studio Marketplace. +1. Download the [Syncfusion® Blazor Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Blazor-Extension) from the Visual Studio Marketplace. 2. Close all Visual Studio instances running, if any. @@ -59,6 +59,6 @@ The steps below illustrate how to download and install the Syncfusion® extensions from the Visual Studio under the **Extensions** menu. +5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the **Extensions** menu. ![SyncfusionMenu](images/SyncfusionMenu.png) \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio/overview.md b/Extension/Blazor-Extension/Visual-Studio/overview.md index 5da2356f..c8043ac3 100644 --- a/Extension/Blazor-Extension/Visual-Studio/overview.md +++ b/Extension/Blazor-Extension/Visual-Studio/overview.md @@ -1,22 +1,22 @@ --- layout: post title: Blazor Extension | Extension | Syncfusion -description: An Extension provides you with quick access so that you can create or configure the Syncfusion Blazor projects along with Syncfusion components +description: An Extension provides you with quick access so that you can create or configure the Syncfusion Blazor projects along with Syncfusion components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Blazor Extension for Visual Studio -The Syncfusion® Essential Studio® Blazor extension for Visual Studio simplifies the use of the Syncfusion® Blazor components by configuring the Syncfusion® Blazor NuGet packages and themes. +The Syncfusion® Essential Studio® Blazor extension for Visual Studio simplifies the use of the Syncfusion® Blazor components by configuring the Syncfusion® Blazor NuGet packages and themes. -The Syncfusion® Blazor extensions provides the following add-ins in Visual Studio: +The Syncfusion® Blazor extensions provides the following add-ins in Visual Studio: -[Project-Template](./template-studio): Creates Syncfusion® Blazor applications with required configuration for development with Syncfusion® Blazor component. +[Project-Template](./template-studio): Creates Syncfusion® Blazor applications with required configuration for development with Syncfusion® Blazor component. -[Code Generator](./code-generator): Adds Syncfusion® Blazor component code in razor file at required place. +[Code Generator](./code-generator): Adds Syncfusion® Blazor component code in razor file at required place. -[Convert project](./convert-project): Converts an existing Blazor Web Application to a Syncfusion® Blazor Web Application by importing the necessary Syncfusion® NuGet packages. +[Convert project](./convert-project): Converts an existing Blazor Web Application to a Syncfusion® Blazor Web Application by importing the necessary Syncfusion® NuGet packages. -[Upgrade project](./upgrade-project): Upgrades the existing Syncfusion® Blazor Web Application from one Essential Studio® version to another version. \ No newline at end of file +[Upgrade project](./upgrade-project): Upgrades the existing Syncfusion® Blazor Web Application from one Essential Studio® version to another version. \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio/scaffolding.md b/Extension/Blazor-Extension/Visual-Studio/scaffolding.md index 96d75139..863232df 100644 --- a/Extension/Blazor-Extension/Visual-Studio/scaffolding.md +++ b/Extension/Blazor-Extension/Visual-Studio/scaffolding.md @@ -1,27 +1,27 @@ --- layout: post title: Scaffolding | Blazor | Syncfusion -description: Learn here about scaffolding using Syncfusion Blazor Extension for Visual Studio to quickly add code to reduce the amount of development time. +description: Learn here about scaffolding using Syncfusion Blazor Extension for Visual Studio to quickly add code to reduce the amount of development time. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Blazor Scaffolding +# Syncfusion® Blazor Scaffolding -Syncfusion provides **Visual Studio Scaffolding** for the Syncfusion® Blazor platform, that allowing you to quickly add code that interacts with data models and reduce the time it takes to develop with data operations in your application. Scaffolding simplifies the creation of Razor and Controller action methods for Syncfusion® Blazor DataGrid, Charts, Scheduler, Diagram, Tree Grid, Rich Text Editor, and Document Editor, and PDF Viewer controls. +Syncfusion® provides **Visual Studio Scaffolding** for the Syncfusion® Blazor platform, that allowing you to quickly add code that interacts with data models and reduce the time it takes to develop with data operations in your application. Scaffolding simplifies the creation of Razor and Controller action methods for Syncfusion® Blazor DataGrid, Charts, Scheduler, Diagram, Tree Grid, Rich Text Editor, and Document Editor, and PDF Viewer controls. > **Note:** Check that at least one Entity Framework model exists, and the application has been compiled once. If no Entity Framework model exists in your application, refer to this [documentation](https://www.freecodecamp.org/news/how-to-create-an-application-using-blazor-and-entity-framework-core-1c1679d87c7e/) to generate the Entity Framework model. After the model file has been added, check that the required DBContext and properties are added. Now, build the application, and try scaffolding. If any changes made in the model properties, rebuild the application once before perform scaffolding. -> **Note:** The Syncfusion® Blazor Scaffolder is available from `v17.4.0.39` for Blazor server-side application and provided the Scaffolding support to Blazor client-side application from `v18.4.0.39`. +> **Note:** The Syncfusion® Blazor Scaffolder is available from `v17.4.0.39` for Blazor server-side application and provided the Scaffolding support to Blazor client-side application from `v18.4.0.39`. ## Add a scaffolded item The steps below assist you to how to add a scaffolded item to your Blazor application. -> **Note:** Before use the Syncfusion® Blazor Scaffolding, check whether the Syncfusion® Blazor Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, install the extension by follow the steps from the [download and installation](download-and-installation) help topic. +> **Note:** Before use the Syncfusion® Blazor Scaffolding, check whether the Syncfusion® Blazor Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, install the extension by follow the steps from the [download and installation](download-and-installation) help topic. 1. If the application type is **Blazor ServerSide**, right-click the **Pages** folder in the Solution Explorer, click **Add**, and then select **New Scaffolded Item..** @@ -31,15 +31,15 @@ The steps below assist you to how to add a scaffolded item to your Blazor applic ![Scaffolded add-in from the hosted project](images/Add_scaffold_hosted.png) -2. In the **Add New Scaffolded item** dialog, select **Syncfusion Blazor Scaffolder** and then click **‘Add’**. +2. In the **Add New Scaffolded item** dialog, select **Syncfusion® Blazor Scaffolder** and then click **‘Add’**. - ![Choose Syncfusion Scaffolding from Visual Studio Add scaffold dialog](images/Syncfusion_scaffolder.png) + ![Choose Syncfusion® Scaffolding from Visual Studio Add scaffold dialog](images/Syncfusion_scaffolder.png) -3. In the Syncfusion® UI Scaffolder dialog, select the desired control to perform scaffolding, and then click **Next**. +3. In the Syncfusion® UI Scaffolder dialog, select the desired control to perform scaffolding, and then click **Next**. ![Choose required control](images/Control_Window.png) -4. The Syncfusion® UI Scaffolder dialog for the selected control will be displayed. As per the application requirements, follow these steps to set up your application. +4. The Syncfusion® UI Scaffolder dialog for the selected control will be displayed. As per the application requirements, follow these steps to set up your application. **Select Data Source Type** @@ -75,11 +75,11 @@ The steps below assist you to how to add a scaffolded item to your Blazor applic ![Choose required selected control features for the hosted project](images/Fetaure_window_hosted.png) -5. In the Syncfusion® UI Scaffolder, the dialog for the selected control feature will open. Choose the required features, update the necessary data fields, and then click **Add**. +5. In the Syncfusion® UI Scaffolder, the dialog for the selected control feature will open. Choose the required features, update the necessary data fields, and then click **Add**. ![Choose required selected control features for the hosted project](images/Fetaure_window_hosted_feature.png) -6. With the selected features of the Syncfusion® control code snippet, the **Controller/Service** file and the corresponding **Razor** files are generated. +6. With the selected features of the Syncfusion® control code snippet, the **Controller/Service** file and the corresponding **Razor** files are generated. If you select **Local Data**, the service file and razor file will be added to the application. @@ -95,25 +95,25 @@ The steps below assist you to how to add a scaffolded item to your Blazor applic 7. Then, add navigation to the created razor file based on your requirement to open on the webpage. -8. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio. +8. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. -## Syncfusion® Blazor Command-line Scaffolding +## Syncfusion® Blazor Command-line Scaffolding -**Scaffolding command-line** for Syncfusion® Blazor allows you to quickly add code that interacts with data models and reduce the amount of time it takes to develop with data operations in your application. Scaffolding simplifies the creation of view file and Controller action methods for Syncfusion® Blazor DataGrid, Charts, Scheduler, Diagram, Tree Grid, Rich Text Editor, Document Editor, and PDF Viewer controls. +**Scaffolding command-line** for Syncfusion® Blazor allows you to quickly add code that interacts with data models and reduce the amount of time it takes to develop with data operations in your application. Scaffolding simplifies the creation of view file and Controller action methods for Syncfusion® Blazor DataGrid, Charts, Scheduler, Diagram, Tree Grid, Rich Text Editor, Document Editor, and PDF Viewer controls. > **Note:** Verify that at least one Entity Framework model exists. If your application lacks an Entity Framework model, use this [documentation](https://www.freecodecamp.org/news/how-to-create-an-application-using-blazor-and-entity-framework-core-1c1679d87c7e/) to create one. After you've added the model file, double-check that the necessary DBContext and properties have been added. Now, build the application and experiment with scaffolding. If any changes made in the model properties, rebuild the application once before perform scaffolding. ## Install Command-line Scaffolding -Install **syncfusion.scaffolding** tool globally by using below command. +Install **Syncfusion®.scaffolding** tool globally by using below command. - ```dotnet tool install -g syncfusion.scaffolding``` + ```dotnet tool install -g Syncfusion®.scaffolding``` ## Update Command-line scaffolding -Update **syncfusion.scaffolding** tool globally by using below command. +Update **Syncfusion®.scaffolding** tool globally by using below command. - ```dotnet tool update -g syncfusion.scaffolding``` + ```dotnet tool update -g Syncfusion®.scaffolding``` ## Add a scaffolded item from command-line @@ -121,7 +121,7 @@ The steps below will assist you to how to add a scaffolded item from command-lin > **Note:** Before adding the scaffolded item from command-line, check whether the **dotnet-aspnet-codegenerator** tool is installed or not by **dotnet tool list -g** command in command prompt. if it is not installed, then install **dotnet-aspnet-codegenerator** tool globally by using this command **dotnet tool install -g dotnet-aspnet-codegenerator**. -1. After installed syncfusion.scaffolding tool, we can invoke syncfusion_scaffold command and it shows the available controls +1. After installed Syncfusion®.scaffolding tool, we can invoke syncfusion_scaffold command and it shows the available controls **syncfusion_scaffold** @@ -159,7 +159,7 @@ The steps below will assist you to how to add a scaffolded item from command-lin ![CommandLine Scaffold](images/commandline.png) -5. As we can see controller and view files generated successfully and also added the Syncfusion® NuGet packages and styles which is required to render Syncfusion® control. +5. As we can see controller and view files generated successfully and also added the Syncfusion® NuGet packages and styles which is required to render Syncfusion® control. ![Blazor added Files](images/blazorfile.png) @@ -167,10 +167,10 @@ The steps below will assist you to how to add a scaffolded item from command-lin -## How to render Syncfusion® control? +## How to render Syncfusion® control? -Refer to the following UG links to render Syncfusion® control after performing scaffolding: +Refer to the following UG links to render Syncfusion® control after performing scaffolding: -WebAssembly App: [Configure Blazor components using Syncfusion® Blazor Component NuGet Package](https://blazor.syncfusion.com/documentation/getting-started/blazor-webassembly-visual-studio) +WebAssembly App: [Configure Blazor components using Syncfusion® Blazor Component NuGet Package](https://blazor.Syncfusion.com/documentation/getting-started/blazor-webassembly-visual-studio) -Blazor Server App: [Configure Blazor components using Syncfusion® Blazor Component NuGet Package](https://blazor.syncfusion.com/documentation/getting-started/blazor-server-side-visual-studio) \ No newline at end of file +Blazor Server App: [Configure Blazor components using Syncfusion® Blazor Component NuGet Package](https://blazor.Syncfusion.com/documentation/getting-started/blazor-server-side-visual-studio) \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio/template-studio.md b/Extension/Blazor-Extension/Visual-Studio/template-studio.md index ab304a51..d5a51567 100644 --- a/Extension/Blazor-Extension/Visual-Studio/template-studio.md +++ b/Extension/Blazor-Extension/Visual-Studio/template-studio.md @@ -1,57 +1,57 @@ --- layout: post title: Template Studio | Blazor | Syncfusion -description: Syncfusion provides the Blazor Template Studio for Blazor platform to create the Syncfusion Blazor Application using Syncfusion components +description: Syncfusion provides the Blazor Template Studio for Blazor platform to create the Syncfusion Blazor Application using Syncfusion components platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Blazor Template Studio +# Syncfusion® Blazor Template Studio -Syncfusion provides the Blazor Template Studio, which allows you to create a Syncfusion® Blazor application with Syncfusion® components. The Syncfusion® Blazor app is created with the required component Syncfusion® NuGet references, namespaces, styles, and component render code. The Template Studio provides an easy-to-use project wizard that walks you through the process of creating an application with Syncfusion® components. +Syncfusion® provides the Blazor Template Studio, which allows you to create a Syncfusion® Blazor application with Syncfusion® components. The Syncfusion® Blazor app is created with the required component Syncfusion® NuGet references, namespaces, styles, and component render code. The Template Studio provides an easy-to-use project wizard that walks you through the process of creating an application with Syncfusion® components. -The steps below will assist you to create your **Syncfusion Blazor Application** through **Visual Studio 2022**: +The steps below will assist you to create your **Syncfusion® Blazor Application** through **Visual Studio 2022**: -> **Note:** The Syncfusion® Blazor Extensions for Visual Studio 2019 are available on Essential Studio® release "20.3.0.56" and below. +> **Note:** The Syncfusion® Blazor Extensions for Visual Studio 2019 are available on Essential Studio® release "20.3.0.56" and below. -> Before use the Syncfusion® Blazor Project Template, check whether the Syncfusion® Blazor Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://blazor.syncfusion.com/documentation/visual-studio-integration/visual-studio-extensions/download-and-installation/) help topic. +> Before use the Syncfusion® Blazor Project Template, check whether the Syncfusion® Blazor Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://blazor.Syncfusion.com/documentation/visual-studio-integration/visual-studio-extensions/download-and-installation/) help topic. 1. Open Visual Studio 2022. -2. To create a Syncfusion® Blazor application, use either one of the following options: +2. To create a Syncfusion® Blazor application, use either one of the following options: **Option 1** - Choose **Extension -> Syncfusion® -> Essential Studio® for Blazor -> Create New Syncfusion® Project...** from the **Visual Studio menu**. + Choose **Extension -> Syncfusion® -> Essential Studio® for Blazor -> Create New Syncfusion® Project...** from the **Visual Studio menu**. ![CreateMenu](images/CreateMenu.png) **Option 2** - Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Syncfusion® templates for Blazor can be found by filtering the application type for **Syncfusion** or by entering **Syncfusion** as a keyword in the search option. + Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Syncfusion® templates for Blazor can be found by filtering the application type for **Syncfusion®** or by entering **Syncfusion®** as a keyword in the search option. ![CreateNewWindow](images/CreateNewWindow.png) -3. Select the **Syncfusion Blazor Template Studio** and click **Next**. +3. Select the **Syncfusion® Blazor Template Studio** and click **Next**. ![CreateNewWizard](images/CreateNewWizard.png) -4. The Syncfusion® Blazor Template Studio wizard will be launched to configure the Syncfusion® Blazor app. +4. The Syncfusion® Blazor Template Studio wizard will be launched to configure the Syncfusion® Blazor app. - > **Note:** Refer to the .NET SDK support for Syncfusion® Blazor Components [here](https://blazor.syncfusion.com/documentation/system-requirements#net-sdk). + > **Note:** Refer to the .NET SDK support for Syncfusion® Blazor Components [here](https://blazor.Syncfusion.com/documentation/system-requirements#net-sdk). **Project type section** - Choose one of the Syncfusion® Blazor application types based on the version of the .NET SDK you are using. + Choose one of the Syncfusion® Blazor application types based on the version of the .NET SDK you are using. - | .NET SDK version | Supported Syncfusion® Blazor Application Type | + | .NET SDK version | Supported Syncfusion® Blazor Application Type | | ------------- | ------------- | - | [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) | Syncfusion® Blazor Web App | - | [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0), [.NET 7.0](https://dotnet.microsoft.com/en-us/download/dotnet/7.0), [.NET 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) | Syncfusion® Blazor WebAssembly App | - | [.NET 7.0](https://dotnet.microsoft.com/en-us/download/dotnet/7.0), [.NET 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) | Syncfusion® Blazor Server App | + | [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) | Syncfusion® Blazor Web App | + | [.NET 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0), [.NET 7.0](https://dotnet.microsoft.com/en-us/download/dotnet/7.0), [.NET 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) | Syncfusion® Blazor WebAssembly App | + | [.NET 7.0](https://dotnet.microsoft.com/en-us/download/dotnet/7.0), [.NET 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) | Syncfusion® Blazor Server App | - In the **Syncfusion Blazor Web App** application type, you can configure the following options: + In the **Syncfusion® Blazor Web App** application type, you can configure the following options:
@@ -76,13 +76,13 @@ The steps below will assist you to create your **Syncfusion Blazor Application** ![WebAppTemplate](images/WebAppTemplate.png) - In the **Syncfusion Blazor WebAssembly App** application type, you can choose ASP.NET Core hosted, Progressive Web Application, or both. + In the **Syncfusion® Blazor WebAssembly App** application type, you can choose ASP.NET Core hosted, Progressive Web Application, or both. ![WASMTemplate](images/WASMTemplate.png) > **Note:** The Progressive Web Application will be enabled if .NET 6.0 version or higher is installed. -5. Click either **Next** or the **Controls** tab. The Syncfusion® Blazor components you can add to the application are listed. +5. Click either **Next** or the **Controls** tab. The Syncfusion® Blazor components you can add to the application are listed. ![Controls Section](images/ControlsSection1.png) @@ -100,13 +100,13 @@ The steps below will assist you to create your **Syncfusion Blazor Application** 7. Click **Next** or the **Configuration** tab to load the Configuration section. You can choose the required (.NET 8.0, .NET 7.0, and .NET 6.0), themes, https configuration, localization option, authentication type, Blazor Web App, and Blazor Web Assembly application types. - Depending on your Syncfusion® Blazor Application Type, refer to the table below for supported authentication types. + Depending on your Syncfusion® Blazor Application Type, refer to the table below for supported authentication types. - | Syncfusion® Blazor Application Type | Supported Authentication Types | + | Syncfusion® Blazor Application Type | Supported Authentication Types | | ------------- | ------------- | - | Syncfusion® Blazor Web App | None and Individual Accounts | - | Syncfusion® Blazor WebAssembly App | None, Individual Accounts and Microsoft Identity Platform | - | Syncfusion® Blazor Server App | None, Individual Accounts, Microsoft Identity Platform, and Windows | + | Syncfusion® Blazor Web App | None and Individual Accounts | + | Syncfusion® Blazor WebAssembly App | None, Individual Accounts and Microsoft Identity Platform | + | Syncfusion® Blazor Server App | None, Individual Accounts, Microsoft Identity Platform, and Windows | If you choose the **Blazor Web App** application type, you can customize the Interactivity type and Interactivity location options. @@ -122,45 +122,45 @@ The steps below will assist you to create your **Syncfusion Blazor Application** ![ProjectDetails](images/ProjectDetails.png) -8. Click **Create** button. The Syncfusion® Blazor application has been created. The created Syncfusion® Blazor app has the Syncfusion® NuGet packages, styles, and the render code for the Syncfusion® component. +8. Click **Create** button. The Syncfusion® Blazor application has been created. The created Syncfusion® Blazor app has the Syncfusion® NuGet packages, styles, and the render code for the Syncfusion® component. ![Readme](images/readme.png) -9. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. +9. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. -## Syncfusion® integration +## Syncfusion® integration -The Syncfusion® Blazor application configures with most recent Syncfusion® Blazor NuGet packages version, styles, namespaces, and component render code for Syncfusion® components. +The Syncfusion® Blazor application configures with most recent Syncfusion® Blazor NuGet packages version, styles, namespaces, and component render code for Syncfusion® components. ### NuGet Packages -Based on the selected Syncfusion® Blazor controls, the individual NuGet packages can be added as NuGet references. Refer [this topic](https://blazor.syncfusion.com/staging/documentation/nuget-packages/) to know about the individual Blazor NuGet packages. +Based on the selected Syncfusion® Blazor controls, the individual NuGet packages can be added as NuGet references. Refer [this topic](https://blazor.Syncfusion.com/staging/documentation/nuget-packages/) to know about the individual Blazor NuGet packages. -> The latest Syncfusion® Essential Studio® version of a NuGet package will be added as reference entry from nuget.org if there is no internet connection. You should restore the NuGet packages when internet becomes available. +> The latest Syncfusion® Essential Studio® version of a NuGet package will be added as reference entry from nuget.org if there is no internet connection. You should restore the NuGet packages when internet becomes available. ![NuGetPackage](images/NuGetPackage.png) ### Style -The selected Syncfusion® Blazor theme is added from Syncfusion® NuGet and this theme reference will be added at these applications locations in Blazor. +The selected Syncfusion® Blazor theme is added from Syncfusion® NuGet and this theme reference will be added at these applications locations in Blazor. | Application type | File location | |---|---| -| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | -| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application) | {Client Project location}\wwwroot\index.html | -| Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (Progressive Web Application) | {Project location}\wwwroot\index.html| +| Syncfusion® Blazor Server App | {Project location}\Pages\\_Host.cshtml | +| Syncfusion® Blazor WebAssembly App (ASPNET Core hosted)
Syncfusion® Blazor WebAssembly App (ASPNET Core hosted and Progressive Web Application) | {Client Project location}\wwwroot\index.html | +| Syncfusion® Blazor WebAssembly App
Syncfusion® Blazor WebAssembly App (Progressive Web Application) | {Project location}\wwwroot\index.html| ![CDNLink](images/CDNLink.png) ### Namespaces -The Syncfusion.Blazor namespaces are added in the **`_imports.razor`** file. +The Syncfusion®.Blazor namespaces are added in the **`_imports.razor`** file. ![NameSpace](images/NameSpace.png) ### Component render code -The selected Syncfusion® Blazor components and features render code added as .razor files in the pages folder. +The selected Syncfusion® Blazor components and features render code added as .razor files in the pages folder. ![Selected control pagess added in project with selected features](images/ControlPages.png) @@ -358,7 +358,7 @@ We need to register the created application in Google Platform API Console for I ### Run application -You can run the application and see the Syncfusion® components you selected. Select a component to see component output. +You can run the application and see the Syncfusion® components you selected. Select a component to see component output. ![Blazor Template output page](images/HomePage.png) @@ -366,7 +366,7 @@ You can select a culture language in combobox at top right on the output page to ![Blazor Template output page](images/Localization.png) -> **Note:** Above culture combobox will be enabled in sample output if localization option is selected in configuration window from Syncfusion® Blazor Template Studio wizard. +> **Note:** Above culture combobox will be enabled in sample output if localization option is selected in configuration window from Syncfusion® Blazor Template Studio wizard. ### Register and Login Application @@ -378,7 +378,7 @@ You can select a culture language in combobox at top right on the output page to ##### Applying Database Migrations: -In the Blazor Web App, it's essential to apply pending migrations to the database before proceeding with user registration. Choose one of the following options: +In the Blazor Web App, it's essential® to apply pending migrations to the database before proceeding with user registration. Choose one of the following options: **Option 1: Using Visual Studio Package Manager Console** diff --git a/Extension/Blazor-Extension/Visual-Studio/upgrade-project.md b/Extension/Blazor-Extension/Visual-Studio/upgrade-project.md index 8fd961fa..d60f1a85 100644 --- a/Extension/Blazor-Extension/Visual-Studio/upgrade-project.md +++ b/Extension/Blazor-Extension/Visual-Studio/upgrade-project.md @@ -1,39 +1,39 @@ --- layout: post title: Project Migration | Blazor | Syncfusion -description: Project Migration is a add-in that helps migrate existing Syncfusion Blazor project from one Syncfusion version to another version +description: Project Migration is a add-in that helps migrate existing Syncfusion Blazor project from one Syncfusion version to another version platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Upgrading Syncfusion® Blazor application to latest version +# Upgrading Syncfusion® Blazor application to latest version -The Syncfusion® Blazor migration add-in for Visual Studio allows you to migrate an existing Syncfusion® Blazor application from one version of Essential Studio® version to another version. This reduces the amount of manual work required when migrating the Syncfusion® version. +The Syncfusion® Blazor migration add-in for Visual Studio allows you to migrate an existing Syncfusion® Blazor application from one version of Essential Studio® version to another version. This reduces the amount of manual work required when migrating the Syncfusion® version. -The steps below will assist you to upgrade the Syncfusion® version in the Syncfusion® Blazor application via Visual Studio 2019: +The steps below will assist you to upgrade the Syncfusion® version in the Syncfusion® Blazor application via Visual Studio 2019: -> Before use the Syncfusion® Blazor Project Migration, check whether the Syncfusion® Blazor Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://blazor.syncfusion.com/documentation/visual-studio-integration/visual-studio-extensions/download-and-installation/) help topic. +> Before use the Syncfusion® Blazor Project Migration, check whether the Syncfusion® Blazor Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://blazor.Syncfusion.com/documentation/visual-studio-integration/visual-studio-extensions/download-and-installation/) help topic. -1. Open the Syncfusion® Blazor application that uses the Syncfusion® component. +1. Open the Syncfusion® Blazor application that uses the Syncfusion® component. 2. To open the Migration Wizard, either one of the following options should be followed: **Option 1** - Choose **Extensions -> Syncfusion® -> Essential Studio® for Blazor -> Migrate Project…** from Visual Studio 2019 menu. + Choose **Extensions -> Syncfusion® -> Essential Studio® for Blazor -> Migrate Project…** from Visual Studio 2019 menu. ![MigrationMenu](images/MigrationMenu.PNG) **Option 2** - Right-click the application from the **Solution Explorer** and select the **Syncfusion Blazor** and choose the **Migrate Syncfusion® Blazor project from another version...** + Right-click the application from the **Solution Explorer** and select the **Syncfusion® Blazor** and choose the **Migrate Syncfusion® Blazor project from another version...** ![MigrationAddin](images/MigrationAddin.png) -3. The Syncfusion® Project Migration window will appear. You can choose the required version of Syncfusion® Blazor to migrate. +3. The Syncfusion® Project Migration window will appear. You can choose the required version of Syncfusion® Blazor to migrate. - > The versions are loaded from the Syncfusion® Blazor NuGet packages published in [`NuGet.org`](https://www.nuget.org/packages?q=Tags%3A%22blazor%22syncfusion) and it requires internet connectivity. + > The versions are loaded from the Syncfusion® Blazor NuGet packages published in [`NuGet.org`](https://www.nuget.org/packages?q=Tags%3A%22blazor%22syncfusion) and it requires internet connectivity. ![MigrationWizard](images/Migration.png) @@ -47,6 +47,6 @@ The steps below will assist you to upgrade the Syncfusion® Blazor NuGet packages are updated to the respective version in the application. +6. The Syncfusion® Blazor NuGet packages are updated to the respective version in the application. -7. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. \ No newline at end of file +7. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/Document-Viewer-Extension/Visual-Studio-Code/FAQ.md b/Extension/Document-Viewer-Extension/Visual-Studio-Code/FAQ.md index 823abcb2..64c4a7ee 100644 --- a/Extension/Document-Viewer-Extension/Visual-Studio-Code/FAQ.md +++ b/Extension/Document-Viewer-Extension/Visual-Studio-Code/FAQ.md @@ -9,10 +9,22 @@ documentation: ug # FAQ +### Can I edit files in the Syncfusion® Document Viewer? + +Yes, the Syncfusion® Document Viewer allows basic editing of Excel, CSV, and TSV files directly within VS Code. This extension focuses on essential® editing tasks to streamline your workflow. For advanced features such as applying formulas, formatting, and complex spreadsheet functions, we recommend using the [Syncfusion® Spreadsheet component](https://www.syncfusion.com/javascript-ui-controls/js-spreadsheet). + +### Is the Syncfusion® Document Viewer suitable for large datasets? + +Yes, the extension's sorting and filtering tools are designed to help you organize and analyze large datasets efficiently. + ### Can I customize the document viewer features? Yes, you can configure Read-Only mode and enable or disable sorting and filtering directly from the status bar or the VS Code settings. +### Is there a way to ensure data integrity while reviewing files? + +Yes, by using the Read-Only Mode, you can ensure that data remains unchanged while reviewing sensitive or critical files. + ### Does the Syncfusion® Document Viewer support other file formats like Word or PDF? Currently, it supports Excel, CSV, and TSV files. Future updates will include DOCX, RTF, MD, and PDF support. \ No newline at end of file diff --git a/Extension/Document-Viewer-Extension/Visual-Studio-Code/configuration-options.md b/Extension/Document-Viewer-Extension/Visual-Studio-Code/configuration-options.md index 6a2d88f9..5f5da349 100644 --- a/Extension/Document-Viewer-Extension/Visual-Studio-Code/configuration-options.md +++ b/Extension/Document-Viewer-Extension/Visual-Studio-Code/configuration-options.md @@ -11,7 +11,7 @@ documentation: ug ### Read-Only Mode -To prevent accidental changes to your files, you can enable Read-Only Mode. +To prevent accidental edits to your files, you can enable Read-Only Mode. - **Enable/Disable via Status Bar**: diff --git a/Extension/Document-Viewer-Extension/Visual-Studio-Code/getting-started.md b/Extension/Document-Viewer-Extension/Visual-Studio-Code/getting-started.md index 56ebd302..5e1b3ac1 100644 --- a/Extension/Document-Viewer-Extension/Visual-Studio-Code/getting-started.md +++ b/Extension/Document-Viewer-Extension/Visual-Studio-Code/getting-started.md @@ -9,7 +9,7 @@ documentation: ug # Getting Started with Syncfusion® Document Viewer -### Open and View Files +### Open and Edit Files **Open a File**: @@ -19,6 +19,14 @@ documentation: ug ![OpenFile](images/OpenFile.gif) +**Edit and Save**: + +- Make your changes directly in the editor. + +- Save your changes by selecting `File > Save` or using the shortcut `Ctrl+S` (Windows) / `Cmd+S` (Mac). + +> **Note:** Syncfusion® Document Viewer allows basic editing of Excel, CSV, and TSV files directly within VS Code. + --- ### Sort and Filter diff --git a/Extension/Document-Viewer-Extension/Visual-Studio-Code/overview.md b/Extension/Document-Viewer-Extension/Visual-Studio-Code/overview.md index ee086d4b..c3e171e9 100644 --- a/Extension/Document-Viewer-Extension/Visual-Studio-Code/overview.md +++ b/Extension/Document-Viewer-Extension/Visual-Studio-Code/overview.md @@ -11,12 +11,12 @@ documentation: ug ## Overview -The **Syncfusion® Document Viewer** for Visual Studio Code enables you to open and view Excel, CSV, and TSV files directly within your editor. It offers features such as sorting, filtering, and read-only mode to streamline your workflow and enhance productivity in Visual Studio Code. +The **Syncfusion® Document Viewer** extension for Visual Studio Code simplifies data handling by integrating essential® features directly into the coding environment. It allows users to view, edit, and manage Excel, CSV, and TSV files without leaving Visual Studio Code. ## Key Features -- **File Viewing**: Open and view Excel (`.xlsx`), CSV (`.csv`), and TSV (`.tsv`) files directly in Visual Studio Code, eliminating the need for external applications. +- **View and Editing**: Open, edit, and save Excel (`.xlsx`), CSV (`.csv`), and TSV (`.tsv`) files. -- **Read-Only Mode**: Enable read-only mode to prevent accidental modifications. +- **Read-Only Mode**: Protect data from accidental modifications. -- **Sorting and Filtering**: Utilize the sorting and filtering options in the column headers for improved viewing. +- **Sorting and Filtering**: Organize data efficiently using built-in tools in column headers. diff --git a/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md b/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md index 253cb79f..7ca1b55b 100644 --- a/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md +++ b/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md @@ -1,39 +1,39 @@ --- layout: post -title: Get rid of from multiple version alert in Syncfusion Toolbox -description: how to get rid of from multiple version alert message when drag and drop a Syncfusion component from Syncfusion Toolbox? +title: Get rid of from multiple version alert in Syncfusion Toolbox +description: how to get rid of from multiple version alert message when drag and drop a Syncfusion component from Syncfusion Toolbox? platform: extension control: Syncfusion Extensions documentation: ug --- -# Get rid of the Multiple Version Alert Messages in Syncfusion® Toolbox +# Get rid of the Multiple Version Alert Messages in Syncfusion® Toolbox -When dragging and dropping a Syncfusion® control from either the **Syncfusion Xamarin Toolbox or the Syncfusion® .NET MAUI Toolbox** into a project containing multiple versions of NuGet packages that are already installed, two types of alert message will be displayed based on the following scenarios: +When dragging and dropping a Syncfusion® control from either the **Syncfusion® Xamarin Toolbox or the Syncfusion® .NET MAUI Toolbox** into a project containing multiple versions of NuGet packages that are already installed, two types of alert message will be displayed based on the following scenarios: * Same NuGet with multiple versions installed. * Different NuGet with multiple versions installed. ## Same NuGet with multiple versions installed -The following alert message will be displayed if multiple versions of the same Syncfusion® NuGet package (e.g., Syncfusion.Xamarin.SfChart **v24.1.xx** and **v24.2.xx**(xamarin) / Syncfusion.MAUI.Buttons **v24.1.xx** and **24.2.xx**(Maui)) are already installed in your project. Recommend maintaining the same version NuGet reference. +The following alert message will be displayed if multiple versions of the same Syncfusion® NuGet package (e.g., Syncfusion.Xamarin.SfChart **v24.1.xx** and **v24.2.xx**(xamarin) / Syncfusion.MAUI.Buttons **v24.1.xx** and **24.2.xx**(Maui)) are already installed in your project. Recommend maintaining the same version NuGet reference. -![Syncfusion Xamarin toolbox alert message when multiple version of the same Syncfusion® Xamarin NuGet package already installed in the project](Alert-message-in-Syncfusion-Xamarin-Toolbox_images\Same-NuGet-Multiple-Version-Installed.jpg) +![Syncfusion® Xamarin toolbox alert message when multiple version of the same Syncfusion® Xamarin NuGet package already installed in the project](Alert-message-in-Syncfusion-Xamarin-Toolbox_images\Same-NuGet-Multiple-Version-Installed.jpg) To resolve this, follow these steps: -1. Uninstall the multiple versions of the same Syncfusion® NuGet package currently installed in your project. -2. Now, manually reinstall a single version of the Syncfusion® NuGet package (e.g., Syncfusion.Xamarin.SfChart **v24.2.xx**(xamarin) / Syncfusion.MAUI.Buttons **v24.2.xx** (Maui)) and add the necessary control render code sample to your project. +1. Uninstall the multiple versions of the same Syncfusion® NuGet package currently installed in your project. +2. Now, manually reinstall a single version of the Syncfusion® NuGet package (e.g., Syncfusion.Xamarin.SfChart **v24.2.xx**(xamarin) / Syncfusion.MAUI.Buttons **v24.2.xx** (Maui)) and add the necessary control render code sample to your project. ## Different NuGet with multiple versions installed -The following alert message will be displayed when different versions of Syncfusion® NuGet packages are installed in your project. Hence, you are not aware of which version of the Syncfusion® NuGet package you need to install in your project. +The following alert message will be displayed when different versions of Syncfusion® NuGet packages are installed in your project. Hence, you are not aware of which version of the Syncfusion® NuGet package you need to install in your project. -![Syncfusion Xamarin toolbox alert message when different Syncfusion® Xamarin NuGet packages are installed with multiple version in the project](Alert-message-in-Syncfusion-Xamarin-Toolbox_images\Diferent-NuGet-Multiple-Version-Installed.jpg) +![Syncfusion® Xamarin toolbox alert message when different Syncfusion® Xamarin NuGet packages are installed with multiple version in the project](Alert-message-in-Syncfusion-Xamarin-Toolbox_images\Diferent-NuGet-Multiple-Version-Installed.jpg) -To resolve this, manually install all the required versions of Syncfusion® NuGet packages in the same version of your project. Then, drag the required Syncfusion® component from the Syncfusion® Toolbox (Xamarin/.NET MAUI) and drop the render code snippet in the XAML file of your project. Please refer to the following help topics to use the Syncfusion® Toolbox: +To resolve this, manually install all the required versions of Syncfusion® NuGet packages in the same version of your project. Then, drag the required Syncfusion® component from the Syncfusion® Toolbox (Xamarin/.NET MAUI) and drop the render code snippet in the XAML file of your project. Please refer to the following help topics to use the Syncfusion® Toolbox: -1. [Xamarin ToolBox](https://help.syncfusion.com/extension/xamarin-extension/toolbox) -2. [.NET MAUI ToolBox](https://help.syncfusion.com/maui/visual-studio-integration/toolbox-control) +1. [Xamarin ToolBox](https://help.Syncfusion.com/extension/xamarin-extension/toolbox) +2. [.NET MAUI ToolBox](https://help.Syncfusion.com/maui/visual-studio-integration/toolbox-control) diff --git a/Extension/Faq/How-to-update-Syncfusion-manual-references-to-Syncfusion-NuGet-packages-in-your-application.md b/Extension/Faq/How-to-update-Syncfusion-manual-references-to-Syncfusion-NuGet-packages-in-your-application.md index 216490f5..6f653d10 100644 --- a/Extension/Faq/How-to-update-Syncfusion-manual-references-to-Syncfusion-NuGet-packages-in-your-application.md +++ b/Extension/Faq/How-to-update-Syncfusion-manual-references-to-Syncfusion-NuGet-packages-in-your-application.md @@ -1,13 +1,13 @@ --- layout: post -title: How to update Syncfusion manual references to Syncfusion NuGet packages in your application | Extension | Syncfusion -description: how to update Syncfusion manual references to Syncfusion NuGet packages in your application? +title: How to update Syncfusion manual references to Syncfusion NuGet packages in your application | Extension | Syncfusion +description: how to update Syncfusion manual references to Syncfusion NuGet packages in your application? platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# How to update Syncfusion® manual references to Syncfusion® NuGet packages in your application? +# How to update Syncfusion® manual references to Syncfusion® NuGet packages in your application? -Follow the steps provided in the given KB for update Syncfusion® manual references to Syncfusion® NuGet packages in your application. KB link: [https://www.syncfusion.com/kb/8507](https://www.syncfusion.com/kb/8507) +Follow the steps provided in the given KB for update Syncfusion® manual references to Syncfusion® NuGet packages in your application. KB link: [https://www.Syncfusion.com/kb/8507](https://www.Syncfusion.com/kb/8507) diff --git a/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md b/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md index 9040e769..ca2fab58 100644 --- a/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md +++ b/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md @@ -1,21 +1,21 @@ --- layout: post -title: Syncfusion template not shown in new project window of Visual Studio -description: The syncfusion templates do not show up in the new project window of visual studio.  how can to get them installed? +title: Syncfusion template not shown in new project window of Visual Studio +description: The Syncfusion templates do not show up in the new project window of visual studio.  how can to get them installed? platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® template not shown in new project window of Visual Studio +# Syncfusion® template not shown in new project window of Visual Studio -Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension build has been installed in the machine or not. +Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension build has been installed in the machine or not. 1. Navigate to the following either one of the location: **Before 17.1.0.32-beta version** - _{Syncfusion installed location}\Utilities\Extensions\ASP.NET MVC_ + _{Syncfusion® installed location}\Utilities\Extensions\ASP.NET MVC_ _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC._ @@ -23,68 +23,68 @@ Perform the given steps to ensure whether the Syncfusion® Project Templates - * Syncfusion® Visual Studio Extensions + * Syncfusion® Project Templates + * Syncfusion® Visual Studio Extensions - ## To Install Syncfusion® Project Templates: + ## To Install Syncfusion® Project Templates: **Before 17.1.0.32-beta version** Navigate to the following location and run the “Syncfusion.MVC.VSPackage.Web.vsix” extension. - _{Syncfusion Build installed location}\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\{Visual Studio Version}_ + _{Syncfusion® Build installed location}\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\{Visual Studio Version}_ Refer the following screenshot. _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\VS2017_ - ![Syncfusion ASP.NET MVC Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img2.png) + ![Syncfusion® ASP.NET MVC Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img2.png) **On or After 17.1.0.32-beta version** - Navigate to the following location and run the “Syncfusion Essential® JS1 AspNet MVC VSExtensions.vsix” extension. + Navigate to the following location and run the “Syncfusion® Essential JS1 AspNet MVC VSExtensions.vsix” extension. - _{Syncfusion Build installed location}\Utilities\Extensions_ + _{Syncfusion® Build installed location}\Utilities\Extensions_ Refer the following screenshot. _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\ASP.NET MVC - EJ1\18.1.0.52\Utilities\Extensions_ - ![Syncfusion ASP.NET MVC Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img4.png) + ![Syncfusion® ASP.NET MVC Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img4.png) - ## To Install Syncfusion® Visual Studio Extension: + ## To Install Syncfusion® Visual Studio Extension: **Before 17.1.0.32-beta version** - Navigate to the following Location and run the “Syncfusion Web Conversion and Migration.vsix” extension. + Navigate to the following Location and run the “Syncfusion® Web Conversion and Migration.vsix” extension. - _{Syncfusion Build installed location}\Utilities\Extensions\Project Conversion\{Visual Studio Version}_ + _{Syncfusion® Build installed location}\Utilities\Extensions\Project Conversion\{Visual Studio Version}_ Refer the following screenshot. _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\Project Conversion\VS2017_ - ![Syncfusion Web Conversion and Migration VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img3.png) + ![Syncfusion® Web Conversion and Migration VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img3.png) **On or After 17.1.0.32-beta version** - Syncfusion® Web Conversion and Migration.vsix extension has been added as a dependency VSIX package to the Syncfusion® Essential® JS1 AspNet MVC VSExtensions.vsix extension from the **v17.1.0.32- beta** and the Syncfusion® Web Conversion and Migration.vsix extension will be installed along with the Syncfusion® Essential® JS1 AspNet MVC VSExtensions.vsix extension. + Syncfusion® Web Conversion and Migration.vsix extension has been added as a dependency VSIX package to the Syncfusion® Essential JS1 AspNet MVC VSExtensions.vsix extension from the **v17.1.0.32- beta** and the Syncfusion® Web Conversion and Migration.vsix extension will be installed along with the Syncfusion® Essential JS1 AspNet MVC VSExtensions.vsix extension. -3. If the respective version of Syncfusion® MVC Extension is not installed in the machine, download the Extension setup from the following link. [http://www.syncfusion.com/downloads/extension/](http://www.syncfusion.com/downloads/extension/) +3. If the respective version of Syncfusion® MVC Extension is not installed in the machine, download the Extension setup from the following link. [http://www.Syncfusion.com/downloads/extension/](http://www.Syncfusion.com/downloads/extension/) diff --git a/Extension/Faq/While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from.md b/Extension/Faq/While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from.md index 2ba4f23e..710eefc0 100644 --- a/Extension/Faq/While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from.md +++ b/Extension/Faq/While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from.md @@ -1,22 +1,22 @@ --- layout: post -title: While creating a new Syncfusion project there are now two icons in the window to select from How to get rid of this | Extension | Syncfusion -description: while creating a new syncfusion project there are now two icons in the window to select from. how to get rid of this? +title: While creating a new Syncfusion project there are now two icons in the window to select from How to get rid of this | Extension | Syncfusion +description: while creating a new Syncfusion project there are now two icons in the window to select from. how to get rid of this? platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# While creating a new Syncfusion® project there are now two icons in the window to select from. How to get rid of this? +# While creating a new Syncfusion® project there are now two icons in the window to select from. How to get rid of this? -Navigate to Visual Studio Tools->Extensions and Updates. The Installed Syncfusion® MVC Extensions are displayed along with its version. Refer to the following screenshot for more information. +Navigate to Visual Studio Tools->Extensions and Updates. The Installed Syncfusion® MVC Extensions are displayed along with its version. Refer to the following screenshot for more information. ![Visual Studio Extension and Updates dialog](While-creating-a-new-Syncfusion-project_images/While-creating-a-new-Syncfusion-project-img1.png) 1. If Syncfusion.MVC.VsPackage.Web is present more than once, uninstall the Syncfusion.MVC.VSPackage.Web VSIX of that particular version that is no longer in use by clicking the Uninstall button. -2. Restart Visual Studio. Now you can see the Syncfusion® ASP.NET MVC project template without multiple entries. +2. Restart Visual Studio. Now you can see the Syncfusion® ASP.NET MVC project template without multiple entries. ![Visual Studio new project dialog](While-creating-a-new-Syncfusion-project_images/While-creating-a-new-Syncfusion-project-img2.png) diff --git a/Extension/Faq/how-to-render-control-after-installing-nuget-packages.md b/Extension/Faq/how-to-render-control-after-installing-nuget-packages.md index 23a935ca..4389fe7e 100644 --- a/Extension/Faq/how-to-render-control-after-installing-nuget-packages.md +++ b/Extension/Faq/how-to-render-control-after-installing-nuget-packages.md @@ -3,11 +3,11 @@ layout: post title: How to render control after installing NuGet Packages | Extension | Syncfusion description: how to render control after installing nuget packages? platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # How to render control after installing NuGet Packages? -Follow the steps provided in the given KB to render a control after installing Syncfusion® NuGet Packages. KB link: [http://www.syncfusion.com/kb/4077](http://www.syncfusion.com/kb/4077) +Follow the steps provided in the given KB to render a control after installing Syncfusion® NuGet Packages. KB link: [http://www.Syncfusion.com/kb/4077](http://www.Syncfusion.com/kb/4077) diff --git a/Extension/Frequently-Asked-Questions/How-to-render-control-after-installing-NuGet-Packages.md b/Extension/Frequently-Asked-Questions/How-to-render-control-after-installing-NuGet-Packages.md index 3b36ad4f..ac5238e6 100644 --- a/Extension/Frequently-Asked-Questions/How-to-render-control-after-installing-NuGet-Packages.md +++ b/Extension/Frequently-Asked-Questions/How-to-render-control-after-installing-NuGet-Packages.md @@ -9,5 +9,5 @@ documentation: ug # How to render control after installing NuGet Packages? -Follow the steps provided in the given KB to render a control after installing Syncfusion® NuGet Packages. KB link: [http://www.syncfusion.com/kb/4077](http://www.syncfusion.com/kb/4077) +Follow the steps provided in the given KB to render a control after installing Syncfusion® NuGet Packages. KB link: [http://www.syncfusion.com/kb/4077](http://www.syncfusion.com/kb/4077) diff --git a/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md b/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md index 7d09e988..2dd12e96 100644 --- a/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md +++ b/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md @@ -3,17 +3,17 @@ layout: post title: The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed description: the syncfusion templates do not show up in the new project window of visual studio.  how can to get them installed? platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# The Syncfusion® templates do not show up in the new project window of Visual Studio.  How can to get them installed? +# The Syncfusion® templates do not show up in the new project window of Visual Studio.  How can to get them installed? -Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension build has been installed in the machine or not. +Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension build has been installed in the machine or not. 1. Navigate to the following location: - _{Syncfusion installed location}\Utilities\Extensions\ASP.NET MVC_ + _{Syncfusion® installed location}\Utilities\Extensions\ASP.NET MVC_ _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC._ @@ -21,37 +21,37 @@ Perform the given steps to ensure whether the Syncfusion® Project Templates - * Syncfusion® Visual Studio Extensions + * Syncfusion® Project Templates + * Syncfusion® Visual Studio Extensions - ## To Install Syncfusion® Project Templates: + ## To Install Syncfusion® Project Templates: Navigate to the following location and run the “Syncfusion.MVC.VSPackage.Web.vsix” extension. - _{Syncfusion Build installed location}\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\{Visual Studio Version}_ + _{Syncfusion® Build installed location}\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\{Visual Studio Version}_ Refer the following screenshot. _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\VS2017_ - ![Syncfusion Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img2.png) + ![Syncfusion® Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img2.png) - ## To Install Syncfusion® Visual Studio Extension: - Navigate to the following Location and run the “Syncfusion Web Conversion and Migration.vsix” extension. + ## To Install Syncfusion® Visual Studio Extension: + Navigate to the following Location and run the “Syncfusion® Web Conversion and Migration.vsix” extension. - _{Syncfusion Build installed location}\Utilities\Extensions\Project Conversion\{Visual Studio Version}_ + _{Syncfusion® Build installed location}\Utilities\Extensions\Project Conversion\{Visual Studio Version}_ Refer the following screenshot. _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\Project Conversion\VS2017_ - ![Syncfusion Visual Studio extension VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img3.png) + ![Syncfusion® Visual Studio extension VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img3.png) -3. If the respective version of Syncfusion® MVC Extension is not installed in the machine, download the Extension setup from the following link. [http://www.syncfusion.com/downloads/extension/](http://www.syncfusion.com/downloads/extension/) +3. If the respective version of Syncfusion® MVC Extension is not installed in the machine, download the Extension setup from the following link. [http://www.syncfusion.com/downloads/extension/](http://www.syncfusion.com/downloads/extension/) diff --git a/Extension/Frequently-Asked-Questions/While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from-How-to-get-rid-of-this.md b/Extension/Frequently-Asked-Questions/While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from-How-to-get-rid-of-this.md index 6f96b326..18da4f19 100644 --- a/Extension/Frequently-Asked-Questions/While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from-How-to-get-rid-of-this.md +++ b/Extension/Frequently-Asked-Questions/While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from-How-to-get-rid-of-this.md @@ -3,20 +3,20 @@ layout: post title: While-creating-a-new-Syncfusion-project-there-are-now-two-icons-in-the-window-to-select-from-How-to-get-rid-of-this description: while creating a new syncfusion project there are now two icons in the window to select from. how to get rid of this? platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# While creating a new Syncfusion® project there are now two icons in the window to select from. How to get rid of this? +# While creating a new Syncfusion® project there are now two icons in the window to select from. How to get rid of this? -Navigate to Visual Studio Tools->Extensions and Updates. The Installed Syncfusion® MVC Extensions are displayed along with its version. Refer to the following screenshot for more information. +Navigate to Visual Studio Tools->Extensions and Updates. The Installed Syncfusion® MVC Extensions are displayed along with its version. Refer to the following screenshot for more information. ![Visual Studio Extension and Updates dialog](While-creating-a-new-Syncfusion-project_images/While-creating-a-new-Syncfusion-project-img1.png) 1. If Syncfusion.MVC.VsPackage.Web is present more than once, uninstall the Syncfusion.MVC.VSPackage.Web VSIX of that particular version that is no longer in use by clicking the Uninstall button. -2. Restart Visual Studio. Now you can see the Syncfusion® ASP.NET MVC project template without multiple entries. +2. Restart Visual Studio. Now you can see the Syncfusion® ASP.NET MVC project template without multiple entries. ![Visual Studio new project dialog](While-creating-a-new-Syncfusion-project_images/While-creating-a-new-Syncfusion-project-img2.png) diff --git a/Extension/Javascript-Extension/Visual-Studio-Code/code-snippet.md b/Extension/Javascript-Extension/Visual-Studio-Code/code-snippet.md index 30d00b93..d9e6d157 100644 --- a/Extension/Javascript-Extension/Visual-Studio-Code/code-snippet.md +++ b/Extension/Javascript-Extension/Visual-Studio-Code/code-snippet.md @@ -1,53 +1,53 @@ --- layout: post title: Code Snippet | Angular | Syncfusion -description: Code snippet adding a Syncfusion Angular component with various features in the HTML code editor file of the Angular Application. +description: Code snippet adding a Syncfusion Angular component with various features in the HTML code editor file of the Angular Application. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Add Syncfusion® Angular component in the Angular application +# Add Syncfusion® Angular component in the Angular application -The Syncfusion® Angular code snippet utility for Visual Studio Code provides snippets for adding a Syncfusion® Angular component with various features in the html code editor file of the Angular Application. +The Syncfusion® Angular code snippet utility for Visual Studio Code provides snippets for adding a Syncfusion® Angular component with various features in the html code editor file of the Angular Application. - > The Syncfusion® Angular code snippet is available from Essential Studio® 2021 Vol 3 (`v19.3.0.43`). + > The Syncfusion® Angular code snippet is available from Essential Studio® 2021 Vol 3 (`v19.3.0.43`). -## Add a Syncfusion® Angular component +## Add a Syncfusion® Angular component -The following steps help you to use the Syncfusion® Angular code snippet in your Angular Application. +The following steps help you to use the Syncfusion® Angular code snippet in your Angular Application. 1. In Visual Studio Code, open an existing Angular Application or create a new Angular Application. -2. Open the html file that you need and place the cursor in required place where you want to add Syncfusion® component. +2. Open the html file that you need and place the cursor in required place where you want to add Syncfusion® component. -3. You can find the Syncfusion® Angular component with the various features by typing the **ejs** word in the format shown below. +3. You can find the Syncfusion® Angular component with the various features by typing the **ejs** word in the format shown below. ```bash - ejs-- + ejs-- For Example, ejs-grid-grouping ``` -4. Choose the Syncfusion® component and click the **Enter** or **Tab** key, the Syncfusion® Angular component will be added in the html file. +4. Choose the Syncfusion® component and click the **Enter** or **Tab** key, the Syncfusion® Angular component will be added in the html file. ![Code Snippet](images/codesnippet.gif) -5. After adding the Syncfusion® Angular component to the html file, use the tab key to fill in the required values to render the component with data. You can also find the Syncfusion® help link at the top of the added snippet to learn more about the new Syncfusion® Angular component feature. +5. After adding the Syncfusion® Angular component to the html file, use the tab key to fill in the required values to render the component with data. You can also find the Syncfusion® help link at the top of the added snippet to learn more about the new Syncfusion® Angular component feature. ![Help](images/Help.png) -## Configure Angular application with Syncfusion +## Configure Angular application with Syncfusion® -The Syncfusion® Angular snippet only add the code snippet alone in the html file. You need to configure the Angular application with Syncfusion® by adding the required Syncfusion® Angular NPM, component modules, and themes by manually. To configure, refer the steps below: +The Syncfusion® Angular snippet only add the code snippet alone in the html file. You need to configure the Angular application with Syncfusion® by adding the required Syncfusion® Angular NPM, component modules, and themes by manually. To configure, refer the steps below: -1. Open the Angular package.json file and add the required Syncfusion® Angular individual NPM package(s) for the Syncfusion® Angular components manually. Then navigate to the packages.json file location in the command prompt and run the ***npm install*** command to restore all the Syncfusion® Angular NPM packages. +1. Open the Angular package.json file and add the required Syncfusion® Angular individual NPM package(s) for the Syncfusion® Angular components manually. Then navigate to the packages.json file location in the command prompt and run the ***npm install*** command to restore all the Syncfusion® Angular NPM packages. ![NPM Package](images/NPM.png) -2. Open your module file and add the required Syncfusion® Angular component(s) module entries to render the Syncfusion® components in your application. +2. Open your module file and add the required Syncfusion® Angular component(s) module entries to render the Syncfusion® components in your application. ![Module](images/Module.png) -3. Add the Syncfusion® Angular [theme](https://ej2.syncfusion.com/documentation/appearance/theme/) entry in the **style.css** file. +3. Add the Syncfusion® Angular [theme](https://ej2.Syncfusion.com/documentation/appearance/theme/) entry in the **style.css** file. ![Themes](images/Themes-Snippet.png) \ No newline at end of file diff --git a/Extension/Javascript-Extension/Visual-Studio-Code/create-project.md b/Extension/Javascript-Extension/Visual-Studio-Code/create-project.md index 617ddde8..36b6b8cb 100644 --- a/Extension/Javascript-Extension/Visual-Studio-Code/create-project.md +++ b/Extension/Javascript-Extension/Visual-Studio-Code/create-project.md @@ -1,25 +1,25 @@ --- layout: post title: Project Templates | Angular | Syncfusion -description: Syncfusion provides Visual Studio Code Project Templates for Angular platform to create the Syncfusion Angular Application using Syncfusion components +description: Syncfusion provides Visual Studio Code Project Templates for Angular platform to create the Syncfusion Angular Application using Syncfusion components platform: extension control: Syncfusion Extensions documentation: ug --- -# Create project With Syncfusion® Visual Studio Code project Templates +# Create project With Syncfusion® Visual Studio Code project Templates -Syncfusion provides **project templates** for **VisualStudio Code** to create Syncfusion® Web applications. Syncfusion® Web Project template creates applications with the selected Framework(React, Angular, and Vue), required Syncfusion® NPM packages, component render code for the Grid, Chart, Scheduler components, and the style for making development easier with Syncfusion® components. +Syncfusion® provides **project templates** for **VisualStudio Code** to create Syncfusion® Web applications. Syncfusion® Web Project template creates applications with the selected Framework(React, Angular, and Vue), required Syncfusion® NPM packages, component render code for the Grid, Chart, Scheduler components, and the style for making development easier with Syncfusion® components. - > The Syncfusion® Visual Studio Code project template provides support for Web project templates from v18.3.0.47. + > The Syncfusion® Visual Studio Code project template provides support for Web project templates from v18.3.0.47. -The following steps help you create **Syncfusion Web Applications** through the **Visual Studio Code:** +The following steps help you create **Syncfusion® Web Applications** through the **Visual Studio Code:** -1. In Visual Studio Code, open the command palette by pressing **Ctrl+Shift+P**. The Visual Studio Code palette opens, search the word **Syncfusion**, so you can get the templates provided. +1. In Visual Studio Code, open the command palette by pressing **Ctrl+Shift+P**. The Visual Studio Code palette opens, search the word **Syncfusion®**, so you can get the templates provided. ![CreateProjectPalette](images/CreateProjectPalette.png) -2. Select Syncfusion® Web Template Studio: Launch and then press Enter. The Template Studio wizard for configuring the Syncfusion® Web app will appear. Provide the require Project Name and Path to create the new Syncfusion® Web application along with any one of the Framework(React, Angular, and Vue). +2. Select Syncfusion® Web Template Studio: Launch and then press Enter. The Template Studio wizard for configuring the Syncfusion® Web app will appear. Provide the require Project Name and Path to create the new Syncfusion® Web application along with any one of the Framework(React, Angular, and Vue). ![ProjectLocation](images/ProjectLocationName.png) @@ -34,7 +34,7 @@ The following steps help you create **Syncfusion Web Applications** through the ![Themes](images/Themes.png) -5. The created Syncfusion® Web App is configured with the Syncfusion® NPM packages, styles, and the component render code for the Syncfusion® component added. +5. The created Syncfusion® Web App is configured with the Syncfusion® NPM packages, styles, and the component render code for the Syncfusion® component added. For **React** diff --git a/Extension/Javascript-Extension/Visual-Studio-Code/download-and-installation.md b/Extension/Javascript-Extension/Visual-Studio-Code/download-and-installation.md index b0333a1d..2b322446 100644 --- a/Extension/Javascript-Extension/Visual-Studio-Code/download-and-installation.md +++ b/Extension/Javascript-Extension/Visual-Studio-Code/download-and-installation.md @@ -3,21 +3,21 @@ layout: post title: Download and Installation | Javascript | Syncfusion description: How to download and install the Syncfusion Web Visual Studio Extensions from Visual Studio Market Place platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -Syncfusion publishes the Visual Studio Code extension in [Visual Studio Code marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Angular-VSCode-Extensions). You can either install it from Visual Studio Code or download and install it from the Visual Studio Code marketplace. +Syncfusion® publishes the Visual Studio Code extension in [Visual Studio Code marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Angular-VSCode-Extensions). You can either install it from Visual Studio Code or download and install it from the Visual Studio Code marketplace. ## Prerequisites -The following prerequisites software needs to be installed for the Syncfusion® Web extension installation and for creating the Syncfusion® Web applications along with any one of the Framework(React, Angular, and Vue). +The following prerequisites software needs to be installed for the Syncfusion® Web extension installation and for creating the Syncfusion® Web applications along with any one of the Framework(React, Angular, and Vue). * [Visual Studio Code](https://code.visualstudio.com/download) - > The minimum version of the Visual Studio Code is 1.38.0 to use the Syncfusion® Web Extension. + > The minimum version of the Visual Studio Code is 1.38.0 to use the Syncfusion® Web Extension. * [C# Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp) @@ -25,36 +25,36 @@ The following prerequisites software needs to be installed for the Syncfusion® Web extensions from Visual Studio Code Extensions. +The following steps explain how to install the Syncfusion® Web extensions from Visual Studio Code Extensions. 1. Open Visual Studio Code. 2. Go to **View > Extensions**, and open Manage Extensions. -3. Type **“Syncfusion Web** in the search box. +3. Type **“Syncfusion® Web** in the search box. ![Extension](images/Extension.png) -4. Click the Install button on the **"Web VSCode Extensions - Syncfusion"** extension. +4. Click the Install button on the **"Web VSCode Extensions - Syncfusion®"** extension. 5. After the installation, reload the Visual Studio Code using the **Reload Required** in Visual Studio Code palette. -6. Now, use the Syncfusion® Web extensions from the Visual Studio Code palette. +6. Now, use the Syncfusion® Web extensions from the Visual Studio Code palette. ![CreateProjectPalette](images/CreateProjectPalette.png) ## Install from the Visual Studio Code Marketplace -The following steps explain how to download Syncfusion® Web applications from the Visual Studio Code Marketplace and install them. +The following steps explain how to download Syncfusion® Web applications from the Visual Studio Code Marketplace and install them. -1. Open the [Syncfusion Web Extension](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Web-VSCode-Extensions) +1. Open the [Syncfusion® Web Extension](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Web-VSCode-Extensions) -2. Click Install from Visual Studio Code Marketplace. The browser opens the popup with the information like **“Open Visual Studio Code”**. Click Open Visual Studio Code, then [Syncfusion Web Extension](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Angular-VSCode-Extensions) will open in Visual Studio Code. +2. Click Install from Visual Studio Code Marketplace. The browser opens the popup with the information like **“Open Visual Studio Code”**. Click Open Visual Studio Code, then [Syncfusion® Web Extension](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Angular-VSCode-Extensions) will open in Visual Studio Code. -3. Click the Install button in the **"Web VSCode Extensions - Syncfusion"** extension. +3. Click the Install button in the **"Web VSCode Extensions - Syncfusion®"** extension. 4. After the installation, reload the Visual Studio Code using the Reload Required in Visual Studio Code palette. -5. Now, use the Syncfusion® Web extensions from the Visual Studio Code palette. +5. Now, use the Syncfusion® Web extensions from the Visual Studio Code palette. ![CreateProjectPalette](images/CreateProjectPalette.png) \ No newline at end of file diff --git a/Extension/Javascript-Extension/Visual-Studio-Code/overview.md b/Extension/Javascript-Extension/Visual-Studio-Code/overview.md index bbfb50ad..bbfa8f27 100644 --- a/Extension/Javascript-Extension/Visual-Studio-Code/overview.md +++ b/Extension/Javascript-Extension/Visual-Studio-Code/overview.md @@ -1,18 +1,18 @@ --- layout: post title: Web VSCode Extension | Extension | Syncfusion -description: Syncfusion Essential Studio Web extension for Visual Studio Code allows you to create a web project with any one of the Frameworks(React, Angular, and Vue). +description: Syncfusion Essential Studio Web extension for Visual Studio Code allows you to create a web project with any one of the Frameworks(React, Angular, and Vue). platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Web Extension for Visual Studio Code -The Syncfusion® Essential Studio® Web extension for Visual Studio Code allows you to use the Syncfusion® JavaScript components(React, Angular, and Vue) easily by configuring the Syncfusion® NPM packages and themes. +The Syncfusion® Essential Studio® Web extension for Visual Studio Code allows you to use the Syncfusion® JavaScript components(React, Angular, and Vue) easily by configuring the Syncfusion® NPM packages and themes. -The Syncfusion® Web Extension provides the following support in Visual Studio Code: +The Syncfusion® Web Extension provides the following support in Visual Studio Code: -[Project-Template](https://help.syncfusion.com/extension/javascript-extension/visual-studio-code/create-project): Creates Syncfusion® Web applications by adding the required Syncfusion® JavaScript components. +[Project-Template](https://help.Syncfusion.com/extension/javascript-extension/visual-studio-code/create-project): Creates Syncfusion® Web applications by adding the required Syncfusion® JavaScript components. -[Code Snippet](/extension/javascript-extension/visual-studio-code/code-snippet): Adds a Syncfusion® Angular component with various features to the Angular Application's HTML code editor. \ No newline at end of file +[Code Snippet](/extension/javascript-extension/visual-studio-code/code-snippet): Adds a Syncfusion® Angular component with various features to the Angular Application's HTML code editor. \ No newline at end of file diff --git a/Extension/NETMAUI-Extension/Visual-Studio-Code/code-snippet.md b/Extension/NETMAUI-Extension/Visual-Studio-Code/code-snippet.md index ac2c1a3a..a944e292 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio-Code/code-snippet.md +++ b/Extension/NETMAUI-Extension/Visual-Studio-Code/code-snippet.md @@ -1,53 +1,53 @@ --- layout: post title: Code Snippets - .NET MAUI Extension Visual Studio Code | Syncfusion -description: Learn here all about how to use code snippet utility of Syncfusion.NET MAUI Extension for Visual Studio Code and much more. +description: Learn here all about how to use code snippet utility of Syncfusion .NET MAUI Extension for Visual Studio Code and much more. platform: MAUI component: Common documentation: ug --- -# Add Syncfusion® .NET MAUI component in the .NET MAUI application +# Add Syncfusion® .NET MAUI component in the .NET MAUI application -The Syncfusion® .NET MAUI code sample utility for Visual Studio Code provides sample for easily inserting Syncfusion® .NET MAUI components with various features into the .NET MAUI Application's XAML code editor. +The Syncfusion® .NET MAUI code sample utility for Visual Studio Code provides sample for easily inserting Syncfusion® .NET MAUI components with various features into the .NET MAUI Application's XAML code editor. -N> The Syncfusion® .NET MAUI code sample is available from Essential Studio® 2024 Volume 1 (`v25.1.35`) onwards. +N> The Syncfusion® .NET MAUI code sample is available from Essential Studio® 2024 Volume 1 (`v25.1.35`) onwards. -## Add a Syncfusion® .NET MAUI component +## Add a Syncfusion® .NET MAUI component -The following instructions outline the process of using the Syncfusion® .NET MAUI code snippet in your .NET MAUI application. +The following instructions outline the process of using the Syncfusion® .NET MAUI code snippet in your .NET MAUI application. 1. In Visual Studio Code, either open an existing .NET MAUI application or create a new .NET MAUI Application. -2. Open the XAML file you require and position the cursor where you want to add the Syncfusion® component. +2. Open the XAML file you require and position the cursor where you want to add the Syncfusion® component. -3. To access Syncfusion® .NET MAUI components with various features, type the **sf** word in the specified format. +3. To access Syncfusion® .NET MAUI components with various features, type the **sf** word in the specified format. ``` -sf- +sf- For Example, sf-datagrid-grouping ``` -4. Select the desired Syncfusion® component and press the **Enter** or **Tab** key to add the Syncfusion® .NET MAUI component to the XAML file. +4. Select the desired Syncfusion® component and press the **Enter** or **Tab** key to add the Syncfusion® .NET MAUI component to the XAML file. ![Code Snippet](images/MAUI_CodeSnippets.gif) -5. After adding the Syncfusion® .NET MAUI component to the XAML file, We've included instructions in the **TODO** section for your reference. This will guide you in determining whether to add the the View Model file or if only add namespace and NuGet entries to run the Syncfusion® components. +5. After adding the Syncfusion® .NET MAUI component to the XAML file, We've included instructions in the **TODO** section for your reference. This will guide you in determining whether to add the the View Model file or if only add namespace and NuGet entries to run the Syncfusion® components. ![Comment](images/Comment.png) -6. You can also find a Syncfusion® help link at the top of the added sample to learn more about the new Syncfusion® .NET MAUI component feature. +6. You can also find a Syncfusion® help link at the top of the added sample to learn more about the new Syncfusion® .NET MAUI component feature. ![Help](images/Help.png) -## Configure .NET MAUI application with Syncfusion +## Configure .NET MAUI application with Syncfusion® -The Syncfusion® .NET MAUI snippet inserts code into the XAML file. However, you need to configure the .NET MAUI project with Syncfusion® by installing the Syncfusion® .NET MAUI NuGet package and adding the appropriate namespace. To configure, follow these steps: +The Syncfusion® .NET MAUI snippet inserts code into the XAML file. However, you need to configure the .NET MAUI project with Syncfusion® by installing the Syncfusion® .NET MAUI NuGet package and adding the appropriate namespace. To configure, follow these steps: -1. Open the .NET MAUI application file and manually add the necessary Syncfusion® .NET MAUI individual NuGet package(s) as a package reference for the Syncfusion® .NET MAUI components. We've included a commented code sample indicating the corresponding NuGet package entry for each component. Copy the NuGet package entry and paste it into your .NET MAUI project file. This NuGet package will be automatically restored during the build or save process of the project. +1. Open the .NET MAUI application file and manually add the necessary Syncfusion® .NET MAUI individual NuGet package(s) as a package reference for the Syncfusion® .NET MAUI components. We've included a commented code sample indicating the corresponding NuGet package entry for each component. Copy the NuGet package entry and paste it into your .NET MAUI project file. This NuGet package will be automatically restored during the build or save process of the project. ![NuGet Package](images/NuGetEntry.gif) -2. To integrate Syncfusion® components into your application, go to the XAML file and insert the necessary Syncfusion® .NET MAUI namespace entries. We've included a commented code sample indicating the corresponding namespace entry for each component. Copy the namespace entry and paste it into your XAML file. +2. To integrate Syncfusion® components into your application, go to the XAML file and insert the necessary Syncfusion® .NET MAUI namespace entries. We've included a commented code sample indicating the corresponding namespace entry for each component. Copy the namespace entry and paste it into your XAML file. ![Namespace](images/NamespaceEntry.gif) \ No newline at end of file diff --git a/Extension/NETMAUI-Extension/Visual-Studio-Code/create-project.md b/Extension/NETMAUI-Extension/Visual-Studio-Code/create-project.md index b435d768..3be04103 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio-Code/create-project.md +++ b/Extension/NETMAUI-Extension/Visual-Studio-Code/create-project.md @@ -1,29 +1,29 @@ --- layout: post title: Create Projects using Project Templates via Extensions | Syncfusion -description: Learn here about how to create syncfusion .NET MAUI application using Syncfusion .NET MAUI Extension for Visual Studio Code. +description: Learn here about how to create Syncfusion .NET MAUI application using Syncfusion .NET MAUI Extension for Visual Studio Code. platform: MAUI component: Common documentation: ug --- -# Creating a Syncfusion® .NET MAUI application +# Creating a Syncfusion® .NET MAUI application -Syncfusion offers the .NET MAUI Project Template for building .NET MAUI applications using Syncfusion® components in Visual Studio Code. This template includes all the necessary Syncfusion® components, NuGet references, namespaces, and code snippets required for developing .NET MAUI applications with Syncfusion. The **.NET MAUI Project Template** comes with a project wizard to streamline the application creation process using Syncfusion® components. +Syncfusion® offers the .NET MAUI Project Template for building .NET MAUI applications using Syncfusion® components in Visual Studio Code. This template includes all the necessary Syncfusion® components, NuGet references, namespaces, and code snippets required for developing .NET MAUI applications with Syncfusion®. The **.NET MAUI Project Template** comes with a project wizard to streamline the application creation process using Syncfusion® components. -N> Syncfusion® Visual Studio Code project templates now support .NET MAUI project templates starting from `v25.1.35`. +N> Syncfusion® Visual Studio Code project templates now support .NET MAUI project templates starting from `v25.1.35`. -The following steps below will assist you to create your **Syncfusion .NET MAUI Application** through **Visual Studio Code:** +The following steps below will assist you to create your **Syncfusion® .NET MAUI Application** through **Visual Studio Code:** -1. To create a Syncfusion® .NET MAUI application in Visual Studio Code, open the command palette by pressing **Ctrl+Shift+P**. Then, search for **Syncfusion** in the Visual Studio Code palette to access the templates provided by Syncfusion. +1. To create a Syncfusion® .NET MAUI application in Visual Studio Code, open the command palette by pressing **Ctrl+Shift+P**. Then, search for **Syncfusion®** in the Visual Studio Code palette to access the templates provided by Syncfusion®. ![CreateProjectPalette](images/CreateProjectPalette.png) -2. Select **Syncfusion .NET MAUI Template Studio: Launch** and press **Enter**. This will launch the Template Studio wizard for configuring the Syncfusion® .NET MAUI application. Enter a unique **Project Name** to identify your application, and then specify the **Project Location**, which is the directory where your project files will be saved. Ensure that the chosen location meets your project's needs. +2. Select **Syncfusion® .NET MAUI Template Studio: Launch** and press **Enter**. This will launch the Template Studio wizard for configuring the Syncfusion® .NET MAUI application. Enter a unique **Project Name** to identify your application, and then specify the **Project Location**, which is the directory where your project files will be saved. Ensure that the chosen location meets your project's needs. ![CreateProject](images/TemplateStudioWizard.png) -3. To select a component, click the **Next** button or the **Components** tab. From there, you can add the desired Syncfusion® .NET MAUI components to your application. Simply choose the necessary Syncfusion® .NET MAUI components for your project. +3. To select a component, click the **Next** button or the **Components** tab. From there, you can add the desired Syncfusion® .NET MAUI components to your application. Simply choose the necessary Syncfusion® .NET MAUI components for your project. ![SelectComponents](images/MAUIControlSelection.gif) @@ -49,15 +49,15 @@ The following steps below will assist you to create your **Syncfusion .NET MAUI ![ProjectSummary](images/MAUIProjectSummary.png) -5. Click the **Create** button to generate the Syncfusion® .NET MAUI application. The created application includes the necessary Syncfusion® NuGet packages and rendering code for the selected Syncfusion® components. +5. Click the **Create** button to generate the Syncfusion® .NET MAUI application. The created application includes the necessary Syncfusion® NuGet packages and rendering code for the selected Syncfusion® components. -6. To view the Syncfusion® components in your application, run it by pressing **F5** or selecting **Run > Start Debugging**. Then, search for **.NET MAUI** and select it to launch the application. +6. To view the Syncfusion® components in your application, run it by pressing **F5** or selecting **Run > Start Debugging**. Then, search for **.NET MAUI** and select it to launch the application. ![Debug](images/Debug.gif) N> **Note:** If the .NET MAUI extension is a preview version, the debugger will be listed as **.NET MAUI**. However, if the .NET MAUI extension is stable, this configuration will be replaced with **C#**. -7. The Syncfusion® .NET MAUI application is configured with the latest Syncfusion® .NET MAUI NuGet packages version, namespaces, and component rendering code for Syncfusion® components. +7. The Syncfusion® .NET MAUI application is configured with the latest Syncfusion® .NET MAUI NuGet packages version, namespaces, and component rendering code for Syncfusion® components. -8. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio. +8. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. diff --git a/Extension/NETMAUI-Extension/Visual-Studio-Code/download-and-installation.md b/Extension/NETMAUI-Extension/Visual-Studio-Code/download-and-installation.md index 6da04df6..ca425521 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio-Code/download-and-installation.md +++ b/Extension/NETMAUI-Extension/Visual-Studio-Code/download-and-installation.md @@ -8,10 +8,10 @@ documentation: ug --- # Download and Installation -Syncfusion publishes the Visual Studio Code extension on the [Visual Studio Code marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUI-VSCode-Extensions). You can install it directly from Visual Studio Code or download and install it from the Visual Studio Code marketplace. +Syncfusion® publishes the Visual Studio Code extension on the [Visual Studio Code marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUI-VSCode-Extensions). You can install it directly from Visual Studio Code or download and install it from the Visual Studio Code marketplace. **Prerequisites** -The following software prerequisites must be installed to install the Syncfusion® .NET MAUI extension, as well as for creating and adding snippets in Syncfusion® .NET MAUI applications. +The following software prerequisites must be installed to install the Syncfusion® .NET MAUI extension, as well as for creating and adding snippets in Syncfusion® .NET MAUI applications. * [Visual Studio Code 1.87.1 or later](https://code.visualstudio.com/download) @@ -20,44 +20,44 @@ The following software prerequisites must be installed to install the Syncfusion * [C# Dev Kit](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit) ## Install through the Visual Studio Code Extensions -The following instructions outline the process of installing the Syncfusion® .NET MAUI extensions from Visual Studio Code Extensions. +The following instructions outline the process of installing the Syncfusion® .NET MAUI extensions from Visual Studio Code Extensions. 1. Open Visual Studio Code. 2. Navigate to **View > Extensions**, and the Manage Extensions option will appear on the left side of the window. -3. By entering the keyword **Syncfusion .NET MAUI** in the search box, you can find the Syncfusion® .NET MAUI Visual Studio Code extension in the Visual Studio Code Marketplace. +3. By entering the keyword **Syncfusion® .NET MAUI** in the search box, you can find the Syncfusion® .NET MAUI Visual Studio Code extension in the Visual Studio Code Marketplace. -4. Install the **.NET MAUI VSCode Extensions - Syncfusion** extension by clicking the Install button. +4. Install the **.NET MAUI VSCode Extensions - Syncfusion®** extension by clicking the Install button. 5. After installation, reload Visual Studio Code using the **Reload Window** command in the Visual Studio Code palette. You can access the command palette by pressing **Ctrl+Shift+P** and searching for Reload Window among the Visual Studio Code commands. ![Reload-Window](images/Reload-Window.png) -6. You can now create a new Syncfusion® .NET MAUI application using the Syncfusion® .NET MAUI extensions from the Visual Studio Code Palette. Find the **Syncfusion .NET MAUI Template Studio: Launch** option among the Visual Studio Code commands to open the Syncfusion® .NET MAUI Template Studio wizard. +6. You can now create a new Syncfusion® .NET MAUI application using the Syncfusion® .NET MAUI extensions from the Visual Studio Code Palette. Find the **Syncfusion® .NET MAUI Template Studio: Launch** option among the Visual Studio Code commands to open the Syncfusion® .NET MAUI Template Studio wizard. ![CreateProjectPalette](images/CreateProjectPalette.png) ## Install from the Visual Studio Code Marketplace -The following instructions outline the process of downloading and installing Syncfusion® .NET MAUI applications from the Visual Studio Code Marketplace. +The following instructions outline the process of downloading and installing Syncfusion® .NET MAUI applications from the Visual Studio Code Marketplace. -1. Open [Syncfusion .NET MAUI Code Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUI-VSCode-Extensions) in Visual Studio Code Marketplace. +1. Open [Syncfusion® .NET MAUI Code Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUI-VSCode-Extensions) in Visual Studio Code Marketplace. -2. Select **Install** from the Visual Studio Code Marketplace. A popup window appears in your browser with information like **Open Visual Studio Code**. Clicking **Open Visual Studio Code** will launch the Syncfusion® .NET MAUI Extension in Visual Studio Code. +2. Select **Install** from the Visual Studio Code Marketplace. A popup window appears in your browser with information like **Open Visual Studio Code**. Clicking **Open Visual Studio Code** will launch the Syncfusion® .NET MAUI Extension in Visual Studio Code. -3. Install the **.NET MAUI VSCode Extensions - Syncfusion** extension by clicking the Install button. +3. Install the **.NET MAUI VSCode Extensions - Syncfusion®** extension by clicking the Install button. 4. After installation, reload Visual Studio Code by executing the **Reload Window** command from the Visual Studio Code palette. Access the command palette by pressing **Ctrl+Shift+P** and locating the Reload Window command among the Visual Studio Code commands. ![Reload-Window](images/Reload-Window.png) -5. You can now initiate the creation of a new Syncfusion® .NET MAUI application using the Syncfusion® .NET MAUI extensions from the Visual Studio Code Palette. Locate the **Syncfusion .NET MAUI Template Studio: Launch** option among the Visual Studio Code commands to open the Syncfusion® .NET MAUI Template Studio wizard. +5. You can now initiate the creation of a new Syncfusion® .NET MAUI application using the Syncfusion® .NET MAUI extensions from the Visual Studio Code Palette. Locate the **Syncfusion® .NET MAUI Template Studio: Launch** option among the Visual Studio Code commands to open the Syncfusion® .NET MAUI Template Studio wizard. ![CreateProjectPalette](images/CreateProjectPalette.png) ## Manually Installing an Extension in Visual Studio Code -The following instructions detail the manual installation process of the Syncfusion® .NET MAUI extensions in Visual Studio Code. +The following instructions detail the manual installation process of the Syncfusion® .NET MAUI extensions in Visual Studio Code. 1. To install the extension manually, download the **SyncfusionInc..NET-MAUI-VSCode-Extensions.vsix** file from the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUI-VSCode-Extensions). Then, install it from a local file within VS Code. diff --git a/Extension/NETMAUI-Extension/Visual-Studio-Code/overview.md b/Extension/NETMAUI-Extension/Visual-Studio-Code/overview.md index 1fd64abd..3c65e6bd 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio-Code/overview.md +++ b/Extension/NETMAUI-Extension/Visual-Studio-Code/overview.md @@ -1,7 +1,7 @@ --- layout: post title: Syncfusion .NET MAUI Extension for Visual Studio Code | Syncfusion -description: Learn here all about introduction on Syncfusion .NET MAUI extension for Visual Studio Code which made integration made ease. +description: Learn here all about introduction on Syncfusion .NET MAUI extension for Visual Studio Code which made integration made ease. platform: MAUI component: Common documentation: ug @@ -9,10 +9,10 @@ documentation: ug # Overview of .NET MAUI Extension for Visual Studio Code -The [Syncfusion .NET MAUI](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUI-VSCode-Extensions) Extension for Visual Studio Code simplifies the use of Syncfusion® .NET MAUI components by configuring the required Syncfusion® .NET MAUI NuGet packages. This extension streamlines development by providing developers with easy access to the powerful features and functionalities of Syncfusion® .NET MAUI components, saving time and effort. +The [Syncfusion® .NET MAUI](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUI-VSCode-Extensions) Extension for Visual Studio Code simplifies the use of Syncfusion® .NET MAUI components by configuring the required Syncfusion® .NET MAUI NuGet packages. This extension streamlines development by providing developers with easy access to the powerful features and functionalities of Syncfusion® .NET MAUI components, saving time and effort. -The Syncfusion® .NET MAUI Extension offers the following support in Visual Studio Code: +The Syncfusion® .NET MAUI Extension offers the following support in Visual Studio Code: -**Project Template:** Creates Syncfusion® .NET MAUI applications with the necessary Syncfusion® components and configurations for development. +**Project Template:** Creates Syncfusion® .NET MAUI applications with the necessary Syncfusion® components and configurations for development. -**Code Snippet:** Adds a Syncfusion® .NET MAUI component with multiple features into the .NET MAUI Application's XAML code editor. +**Code Snippet:** Adds a Syncfusion® .NET MAUI component with multiple features into the .NET MAUI Application's XAML code editor. diff --git a/Extension/NETMAUI-Extension/Visual-Studio/Syncfusion-Notifications.md b/Extension/NETMAUI-Extension/Visual-Studio/Syncfusion-Notifications.md index 9816db2f..c6919e0c 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio/Syncfusion-Notifications.md +++ b/Extension/NETMAUI-Extension/Visual-Studio/Syncfusion-Notifications.md @@ -1,49 +1,49 @@ --- layout: post title: Notifications of .NET MAUI Extension | Syncfusion -description: For displaying the notifications about trial and newer version update information for Syncfusion applications. +description: For displaying the notifications about trial and newer version update information for Syncfusion applications. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Notifications +# Syncfusion® Notifications -Syncfusion enhances the user experience in .NET MAUI applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. +Syncfusion® enhances the user experience in .NET MAUI applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. -N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. +N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. ## Notification Configuration -The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. +The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. -It can be accessed by clicking **Tools -> Options -> Syncfusion® -> .NET MAUI** +It can be accessed by clicking **Tools -> Options -> Syncfusion® -> .NET MAUI** ![Option Page](images/maui-optionPage.png) ## Notification Types -**1. Syncfusion® Trial Application Notification** +**1. Syncfusion® Trial Application Notification** -When you utilize Syncfusion® trial assemblies in your .NET MAUI application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion. +When you utilize Syncfusion® trial assemblies in your .NET MAUI application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion®. ![Trial Notification](images/maui-trial.png) -**2. Newer Syncfusion® NuGet Package Notification** +**2. Newer Syncfusion® NuGet Package Notification** -If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. +If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. ![NuGet Notification](images/maui-nuget.png) -**3. Newer Essential Studio® Build Notification** +**3. Newer Essential Studio® Build Notification** -If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® .NET MAUI,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your .NET MAUI development projects. +If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® .NET MAUI,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your .NET MAUI development projects. ![Build Notification](images/maui-build.png) **4. Invalid License Key Notification** -If you have mistakenly used an incorrect license key or used a license from another version or platform in your .NET MAUI application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. +If you have mistakenly used an incorrect license key or used a license from another version or platform in your .NET MAUI application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. ![Invalid Notification](images/maui-invalid.png) diff --git a/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md b/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md index 9ac49d16..d73b2f6a 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md +++ b/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md @@ -1,47 +1,47 @@ --- layout: post title: Toolbox Control | .NET MAUI | Syncfusion -description: Syncfusion .NET MAUI Toolbox to add the Syncfusion .NET MAUI (.NET MAUI.Forms) controls in your project without coding in the Visual Studio designer. +description: Syncfusion .NET MAUI Toolbox to add the Syncfusion .NET MAUI (.NET MAUI.Forms) controls in your project without coding in the Visual Studio designer. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Toolbox for .NET MAUI +# Syncfusion® Toolbox for .NET MAUI -The Syncfusion® Visual Studio Toolbox for the .NET MAUI platform is a valuable resource for developers seeking to seamlessly incorporate the Syncfusion® .NET MAUI components into their applications. Designed to be compatible with Visual Studio 2022, this toolbox offers a streamlined workflow, simplifying the integration and configuration process of Syncfusion® components. +The Syncfusion® Visual Studio Toolbox for the .NET MAUI platform is a valuable resource for developers seeking to seamlessly incorporate the Syncfusion® .NET MAUI components into their applications. Designed to be compatible with Visual Studio 2022, this toolbox offers a streamlined workflow, simplifying the integration and configuration process of Syncfusion® components. -I> The Syncfusion® .NET MAUI Toolbox supports Visual Studio 2022 and is available from Essential Studio® 2023 Volume 2(v22.1.34) onwards. +I> The Syncfusion® .NET MAUI Toolbox supports Visual Studio 2022 and is available from Essential Studio® 2023 Volume 2(v22.1.34) onwards. -> To check whether the **.NET MAUI Extensions - Syncfusion** extension is installed or not in Visual Studio Extension Manager by navigating to **Extension > Manage Extensions > Installed** for Visual Studio 2022. If this extension is not installed, follow the steps outlined in the [download and installation](download-and-installation) help topic to install the extension. +> To check whether the **.NET MAUI Extensions - Syncfusion®** extension is installed or not in Visual Studio Extension Manager by navigating to **Extension > Manage Extensions > Installed** for Visual Studio 2022. If this extension is not installed, follow the steps outlined in the [download and installation](download-and-installation) help topic to install the extension. -## Launching Syncfusion® .NET MAUI Toolbox from the Syncfusion® menu +## Launching Syncfusion® .NET MAUI Toolbox from the Syncfusion® menu -To launch the Syncfusion® .NET MAUI Toolbox from the Syncfusion® menu in Visual Studio 2022, follow these steps: +To launch the Syncfusion® .NET MAUI Toolbox from the Syncfusion® menu in Visual Studio 2022, follow these steps: 1. Open Visual Studio 2022. 2. Go to the **Extensions** menu at the top of the Visual Studio window. -3. Click on **Syncfusion** within the **Extensions** menu. -4. In the Syncfusion® submenu, locate and click on **Essential Studio for .NET MAUI**. -5. From the **Essential Studio for .NET MAUI** submenu, select **Launch .NET MAUI Toolbox**. -This toolbox provides a set of tools and features to easily incorporate Syncfusion® .NET MAUI components into your .NET MAUI application. +3. Click on **Syncfusion®** within the **Extensions** menu. +4. In the Syncfusion® submenu, locate and click on **Essential Studio® for .NET MAUI**. +5. From the **Essential Studio® for .NET MAUI** submenu, select **Launch .NET MAUI Toolbox**. +This toolbox provides a set of tools and features to easily incorporate Syncfusion® .NET MAUI components into your .NET MAUI application. - ![Syncfusion .NET MAUI Custom Toolbox via Syncfusion® menu](images/ToolboxSyncfusionMenu.png) + ![Syncfusion® .NET MAUI Custom Toolbox via Syncfusion® menu](images/ToolboxSyncfusionMenu.png) -## Launching Syncfusion® .NET MAUI Toolbox from the View menu +## Launching Syncfusion® .NET MAUI Toolbox from the View menu -To launch the Syncfusion® .NET MAUI Toolbox from the View menu in Visual Studio 2022, simply follow these steps: +To launch the Syncfusion® .NET MAUI Toolbox from the View menu in Visual Studio 2022, simply follow these steps: 1. Open Visual Studio 2022. 2. At the top menu, click on **View**. 3. From the drop-down menu, select **Other Windows**. -4. In the sub-menu that appears, click on **Syncfusion .NET MAUI Toolbox**. -This toolbox provides a set of tools and features to easily incorporate Syncfusion® .NET MAUI components into your .NET MAUI application. +4. In the sub-menu that appears, click on **Syncfusion® .NET MAUI Toolbox**. +This toolbox provides a set of tools and features to easily incorporate Syncfusion® .NET MAUI components into your .NET MAUI application. - ![Syncfusion .NET MAUI Custom Toolbox view menu](images/ToolboxViewMenu.png) + ![Syncfusion® .NET MAUI Custom Toolbox view menu](images/ToolboxViewMenu.png) -## Add Syncfusion® .NET MAUI Toolbox Components +## Add Syncfusion® .NET MAUI Toolbox Components -To incorporate Syncfusion® .NET MAUI components into your XAML design file, you can easily add them by dragging and dropping them from the toolbox. This intuitive approach automatically inserts the component's code sample and namespace into your XAML file, while also taking care of installing necessary NuGet packages. +To incorporate Syncfusion® .NET MAUI components into your XAML design file, you can easily add them by dragging and dropping them from the toolbox. This intuitive approach automatically inserts the component's code sample and namespace into your XAML file, while also taking care of installing necessary NuGet packages. - ![Syncfusion .NET MAUI Toolbox Wizard](images/ToolboxComponents.gif) + ![Syncfusion® .NET MAUI Toolbox Wizard](images/ToolboxComponents.gif) -Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio. \ No newline at end of file +Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/NETMAUI-Extension/Visual-Studio/download-and-installation.md b/Extension/NETMAUI-Extension/Visual-Studio/download-and-installation.md index bbcf04c1..5a942aee 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio/download-and-installation.md +++ b/Extension/NETMAUI-Extension/Visual-Studio/download-and-installation.md @@ -1,7 +1,7 @@ --- layout: post title: Download and Installation of .NET MAUI Extension | Syncfusion -description: Check out the documentation for download and installation of Syncfusion .NET MAUI Extension for Visual Studio. +description: Check out the documentation for download and installation of Syncfusion .NET MAUI Extension for Visual Studio. platform: extension control: Syncfusion Extensions documentation: ug @@ -9,14 +9,14 @@ documentation: ug # Download and Installation -Syncfusion publishes the Visual Studio extension in the below Visual Studio marketplace link. You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. +Syncfusion® publishes the Visual Studio extension in the below Visual Studio marketplace link. You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. [Visual Studio 2022](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUIVSExtension) ## Prerequisites -The following software prerequisites must be installed to install the Syncfusion® .NET MAUI extension, as well as for creating, adding snippet in Syncfusion® .NET MAUI applications. +The following software prerequisites must be installed to install the Syncfusion® .NET MAUI extension, as well as for creating, adding snippet in Syncfusion® .NET MAUI applications. * [Visual Studio 2022 17.3 or later](https://visualstudio.microsoft.com/downloads/). @@ -25,17 +25,17 @@ The following software prerequisites must be installed to install the Syncfusion ## Install through the Visual Studio Manage Extensions -The following steps will guide you on how to install the Syncfusion® .NET MAUI extensions using **Visual Studio Manage Extensions**. +The following steps will guide you on how to install the Syncfusion® .NET MAUI extensions using **Visual Studio Manage Extensions**. 1. Open Visual Studio 2022. 2. Navigate to **Extension ->Manage Extensions** and open the Manage Extensions. -3. Click on the **Online** tab located on the left and enter **"Syncfusion .NET MAUI"** into the **search box**. +3. Click on the **Online** tab located on the left and enter **"Syncfusion® .NET MAUI"** into the **search box**. ![Online-Manage-Extension-window](images/OnlineExtension.png) -4. Click on the **Download** button in the **“.NET MAUI Extensions - Syncfusion”** extensions. +4. Click on the **Download** button in the **“.NET MAUI Extensions - Syncfusion®”** extensions. 5. After downloading the extensions, close all running instances of Visual Studio to start the installation process. The following VSIX installation prompt will appear. @@ -45,15 +45,15 @@ The following steps will guide you on how to install the Syncfusion® extensions under the **Extensions** menu in Visual Studio +8. You can utilize the Syncfusion® extensions under the **Extensions** menu in Visual Studio ![SyncfusionMenu](images/MenuExtensions.png) ## Install from the Visual Studio Marketplace -The following steps illustrate how to download and install the Syncfusion® .NET MAUI extension from the Visual Studio Marketplace. +The following steps illustrate how to download and install the Syncfusion® .NET MAUI extension from the Visual Studio Marketplace. -1. Download the Syncfusion® .NET MAUI Extensions from the below Visual Studio Marketplace. +1. Download the Syncfusion® .NET MAUI Extensions from the below Visual Studio Marketplace. [Visual Studio 2022](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUIVSExtension) @@ -65,6 +65,6 @@ The following steps illustrate how to download and install the Syncfusion® extensions under the **Extensions** menu in Visual Studio +5. Launch Visual Studio after the installation is complete. You can utilize the Syncfusion® extensions under the **Extensions** menu in Visual Studio ![SyncfusionMenu](images/MenuExtensions.png) \ No newline at end of file diff --git a/Extension/NETMAUI-Extension/Visual-Studio/overview.md b/Extension/NETMAUI-Extension/Visual-Studio/overview.md index da530b88..d7029ded 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio/overview.md +++ b/Extension/NETMAUI-Extension/Visual-Studio/overview.md @@ -1,18 +1,18 @@ --- layout: post -title: Overview of Syncfusion .NET MAUI Extension for Visual Studio | Syncfusion -description: Learn here all about introduction on Syncfusion .NET MAUI extension for Visual Studio which made integration ease. +title: Overview of Syncfusion .NET MAUI Extension for Visual Studio | Syncfusion +description: Learn here all about introduction on Syncfusion .NET MAUI extension for Visual Studio which made integration ease. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Overview of .NET MAUI Extension for Visual Studio -The Syncfusion® .NET MAUI Extension for Visual Studio simplifies the utilization of Syncfusion® .NET MAUI components by configuring the required Syncfusion® .NET MAUI NuGet packages. This extension streamlines the development process by providing developers with easy access to the powerful features and functionalities of Syncfusion® .NET MAUI components, thereby saving time and effort. +The Syncfusion® .NET MAUI Extension for Visual Studio simplifies the utilization of Syncfusion® .NET MAUI components by configuring the required Syncfusion® .NET MAUI NuGet packages. This extension streamlines the development process by providing developers with easy access to the powerful features and functionalities of Syncfusion® .NET MAUI components, thereby saving time and effort. [Visual Studio 2022](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.MAUIVSExtension) -The Syncfusion® .NET MAUI extensions provide the following add-ins in Visual Studio: +The Syncfusion® .NET MAUI extensions provide the following add-ins in Visual Studio: -[Project-Template](template-studio): Creates Syncfusion® .NET MAUI applications with the required Syncfusion® components and configurations for development. +[Project-Template](template-studio): Creates Syncfusion® .NET MAUI applications with the required Syncfusion® components and configurations for development. diff --git a/Extension/NETMAUI-Extension/Visual-Studio/template-studio.md b/Extension/NETMAUI-Extension/Visual-Studio/template-studio.md index ebce8f2b..35609042 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio/template-studio.md +++ b/Extension/NETMAUI-Extension/Visual-Studio/template-studio.md @@ -7,35 +7,35 @@ control: Syncfusion Extensions documentation: ug --- -# Syncfusion® .NET MAUI Template Studio +# Syncfusion® .NET MAUI Template Studio -The .NET MAUI Template Studio is provided by Syncfusion® and is used to build the Syncfusion® .NET MAUI applications using Syncfusion® components. The required Syncfusion® components, NuGet references, namespace, and component render code are all used to develop the Syncfusion® .NET MAUI applications. The Syncfusion® .NET MAUI Template Studio providing a project wizard to simplify the process for you to create an application using Syncfusion® components. +The .NET MAUI Template Studio is provided by Syncfusion® and is used to build the Syncfusion® .NET MAUI applications using Syncfusion® components. The required Syncfusion® components, NuGet references, namespace, and component render code are all used to develop the Syncfusion® .NET MAUI applications. The Syncfusion® .NET MAUI Template Studio providing a project wizard to simplify the process for you to create an application using Syncfusion® components. -The following steps below will assist you to create your **Syncfusion .NET MAUI Application** through **Visual Studio 2022**: +The following steps below will assist you to create your **Syncfusion® .NET MAUI Application** through **Visual Studio 2022**: -N> Before use the Syncfusion® .NET MAUI Project Template, check whether the Syncfusion® .NET MAUI Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, install the extension by follow the steps from the [download and installation](download-and-installation) help topic. +N> Before use the Syncfusion® .NET MAUI Project Template, check whether the Syncfusion® .NET MAUI Template Studio Extension installed or not in Visual Studio Extension Manager by clicking on the Extensions -> Manage Extensions -> Installed. If this extension not installed, install the extension by follow the steps from the [download and installation](download-and-installation) help topic. 1. Open the Visual Studio 2022. -2. To develop the Syncfusion® .NET MAUI application, select one of the following options: +2. To develop the Syncfusion® .NET MAUI application, select one of the following options: **Option 1** - Choose **Extension -> Syncfusion® -> Essential Studio® for .NET MAUI -> Create New Syncfusion® Project...** from the **Visual Studio menu**. + Choose **Extension -> Syncfusion® -> Essential Studio® for .NET MAUI -> Create New Syncfusion® Project...** from the **Visual Studio menu**. ![CreateMenu](images/MenuProject.png) **Option 2** - Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by **Syncfusion** or typing **Syncfusion** as a keyword in the search option can help you to find the Syncfusion® templates for .NET MAUI. + Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by **Syncfusion®** or typing **Syncfusion®** as a keyword in the search option can help you to find the Syncfusion® templates for .NET MAUI. ![CreateNewWindow](images/ProjectTemplates.png) -3. Select the **Syncfusion .NET MAUI Template Studio** and click **Next**. +3. Select the **Syncfusion® .NET MAUI Template Studio** and click **Next**. ![CreateNewWizard](images/SyncfusionTemplate.png) -4. After launching the Syncfusion® .NET MAUI Template Studio, the wizard for configuring the Syncfusion® .NET MAUI application will appear. You can add the following Syncfusion® .NET MAUI components to the application. Choose the required Syncfusion® .NET MAUI components +4. After launching the Syncfusion® .NET MAUI Template Studio, the wizard for configuring the Syncfusion® .NET MAUI application will appear. You can add the following Syncfusion® .NET MAUI components to the application. Choose the required Syncfusion® .NET MAUI components ![Controls Section](images/ControlsTab.png) @@ -65,10 +65,10 @@ N> Before use the Syncfusion® .NET MAUI Pr ![Choose required Project Details](images/ProjectDetails.png) -7. Click the **Create** button to create the Syncfusion® .NET MAUI application The created Syncfusion® .NET MAUI application has the Syncfusion® NuGet packages,and the rendering code for the selected Syncfusion® components. +7. Click the **Create** button to create the Syncfusion® .NET MAUI application The created Syncfusion® .NET MAUI application has the Syncfusion® NuGet packages,and the rendering code for the selected Syncfusion® components. ![Readme](images/MauiApplication.png) -8. The Syncfusion® .NET MAUI application configures with most recent Syncfusion® .NET MAUI NuGet packages version, namespaces , and component render code for Syncfusion® components. +8. The Syncfusion® .NET MAUI application configures with most recent Syncfusion® .NET MAUI NuGet packages version, namespaces , and component render code for Syncfusion® components. -9. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio. +9. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. diff --git a/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md b/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md index c55ef4aa..13178a59 100644 --- a/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md +++ b/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md @@ -7,11 +7,11 @@ control: NuGet Packages documentation: ug --- -# Syncfusion® NuGet Packages Overview +# Syncfusion® NuGet Packages Overview -[NuGet](https://www.nuget.org/) can be used to automatically add files and references to your Visual Studio projects. You can use the Syncfusion® NuGet packages without installing the Essential Studio® or platform installation to development with the Syncfusion® controls. From v16.2.0.46 (2018 Volume 2 Service Pack 1) onwards, all the Syncfusion® components are available as NuGet packages at [nuget.org](https://www.nuget.org/profiles/SyncfusionInc). +[NuGet](https://www.nuget.org/) can be used to automatically add files and references to your Visual Studio projects. You can use the Syncfusion® NuGet packages without installing the Essential Studio® or platform installation to development with the Syncfusion® controls. From v16.2.0.46 (2018 Volume 2 Service Pack 1) onwards, all the Syncfusion® components are available as NuGet packages at [nuget.org](https://www.nuget.org/profiles/SyncfusionInc). -N> Starting from v17.1.0.32 (2018 Volume 1), Syncfusion® will no longer publish NuGet packages at [nuget.syncfusion.com](https://nuget.syncfusion.com/). +N> Starting from v17.1.0.32 (2018 Volume 1), Syncfusion® will no longer publish NuGet packages at [nuget.syncfusion.com](https://nuget.syncfusion.com/). ## Installing NuGet Packages @@ -29,15 +29,15 @@ The NuGet Package Manager can be used to search and install NuGet packages in th ![NuGet package manager dialog window](NuGet_Packages_Images/img7.png) -3. The Syncfusion® NuGet Packages are listed the available package in the source feed URL. Search and install the required packages in your application, by clicking **Install** button. +3. The Syncfusion® NuGet Packages are listed the available package in the source feed URL. Search and install the required packages in your application, by clicking **Install** button. -N> The Syncfusion® NuGet packages are published in public [NuGet.org](https://www.nuget.org/) from v16.2.0.46. So, If you need to Install earlier version of 16.2.0.46 Syncfusion® NuGet packages, [configure Syncfusion® private feed URL](https://help.syncfusion.com/extension/syncfusion-nuget-packages/nuget-packages#syncfusion-nuget-feed-url-configuration). +N> The Syncfusion® NuGet packages are published in public [NuGet.org](https://www.nuget.org/) from v16.2.0.46. So, If you need to Install earlier version of 16.2.0.46 Syncfusion® NuGet packages, [configure Syncfusion® private feed URL](https://help.syncfusion.com/extension/syncfusion-nuget-packages/nuget-packages#syncfusion-nuget-feed-url-configuration). ### Using Package Manager Console -To reference the Syncfusion® component using the Package Manager Console as NuGet packages, follow the below steps. +To reference the Syncfusion® component using the Package Manager Console as NuGet packages, follow the below steps. 1. On the **Tools** menu, select **NuGet Package Manager**, and then **Package Manager Console**. @@ -73,7 +73,7 @@ Add packages can be used to search and install NuGet packages to the Visual Stud ![Add packages dialog](NuGet_Packages_Images/img9.png) -3. The Syncfusion® NuGet Packages available in the package source location will be listed. Search and install the required packages in your application, by clicking **Add Package** button. +3. The Syncfusion® NuGet Packages available in the package source location will be listed. Search and install the required packages in your application, by clicking **Add Package** button. ## Managing NuGet package using NuGet CLI @@ -115,7 +115,7 @@ The NuGet Command Line Interface (CLI), nuget.exe, provides the full extent of N mono nuget.exe install “C:\Users\SyncfusionApplication\package.config” ~~~ -N> If you need to Install earlier version of 16.2.0.46 Syncfusion® NuGet packages, [configure Syncfusion® private feed URL](https://help.syncfusion.com/extension/syncfusion-nuget-packages/nuget-packages#syncfusion-nuget-feed-url-configuration). +N> If you need to Install earlier version of 16.2.0.46 Syncfusion® NuGet packages, [configure Syncfusion® private feed URL](https://help.syncfusion.com/extension/syncfusion-nuget-packages/nuget-packages#syncfusion-nuget-feed-url-configuration). ## Managing NuGet package using Dotnet CLI @@ -149,13 +149,13 @@ The NuGet Command Line Interface (CLI), Dotnet.exe, provides the full extent of ## Managing NuGet package for Visual Studio online application -The following steps help you to configure and restore the Syncfusion® NuGet packages in Visual Studio online application. +The following steps help you to configure and restore the Syncfusion® NuGet packages in Visual Studio online application. ### Configure NuGet feed URL 1. Create and add the NuGet.config file in your Visual Studio online application location. By default, the NuGet.org feed link can be added in the NuGet.config file. - N> If you need to Install v16.2.0.46 before Syncfusion® NuGet packages, add the required Syncfusion® platform NuGet feed links in the NuGet.config file. You can get the Syncfusion® NuGet package feed link by clicking the **Copy URL** label from the required platform provided in the following link: + N> If you need to Install v16.2.0.46 before Syncfusion® NuGet packages, add the required Syncfusion® platform NuGet feed links in the NuGet.config file. You can get the Syncfusion® NuGet package feed link by clicking the **Copy URL** label from the required platform provided in the following link: ![Sample project configuration page in Visual Studio Online Application](NuGet-VisualStudioonline_images/NuGet-VisualStudioonline-img1.png) @@ -209,7 +209,7 @@ N> To update all the projects from solution, use update option in the solution l ### Using Package Manger Console -To update the installed Syncfusion® NuGet packages using the Package Manager Console, follow the below steps. +To update the installed Syncfusion® NuGet packages using the Package Manager Console, follow the below steps. 1. On the **Tools** menu, select **NuGet Package Manager**, and then **Package Manager Console.** @@ -229,7 +229,7 @@ To update the installed Syncfusion® NuGet **For example:** ~~~ - #Update specified Syncfusion® NuGet package + #Update specified Syncfusion® NuGet package Update-Package Syncfusion.EJ.AspNet.Core #Update specified package in specified project @@ -248,7 +248,7 @@ Using the NuGet CLI, all the NuGet packages in the project can be updated to the nuget update -self ~~~ -2. Open the downloaded executable location in the command window. Run the following “update commands” to update the Syncfusion® ASP.NET Core NuGet packages. +2. Open the downloaded executable location in the command window. Run the following “update commands” to update the Syncfusion® ASP.NET Core NuGet packages. ~~~ #update all NuGet packages from config file @@ -269,21 +269,21 @@ Using the NuGet CLI, all the NuGet packages in the project can be updated to the N> Update command is not working as expected in Mono (Mac and Linux) and projects using PackageReference format. -## Syncfusion® NuGet feed URL Configuration +## Syncfusion® NuGet feed URL Configuration -### Get the Syncfusion® NuGet feed URL +### Get the Syncfusion® NuGet feed URL -You should get the private Syncfusion® NuGet feed URL to install or upgrade the Syncfusion® NuGet packages. To get the URL from Syncfusion® website use the following steps: +You should get the private Syncfusion® NuGet feed URL to install or upgrade the Syncfusion® NuGet packages. To get the URL from Syncfusion® website use the following steps: 1. Navigate to [nuget.syncfusion.com](https://nuget.syncfusion.com/), and select the required platform tab. -2. Click the Copy URL label under required platform to copy the Syncfusion® required platform NuGet feed to clipboard. +2. Click the Copy URL label under required platform to copy the Syncfusion® required platform NuGet feed to clipboard. - ![Syncfusion Essential JS 2 ASP.NET Core NuGet feed URL](NuGet_Packages_Images/img1.png) + ![Syncfusion® Essential® JS 2 ASP.NET Core NuGet feed URL](NuGet_Packages_Images/img1.png) -3. Now, use this NuGet feed URL to access the Syncfusion® NuGet Packages in Visual Studio. +3. Now, use this NuGet feed URL to access the Syncfusion® NuGet Packages in Visual Studio. -### Add the Syncfusion® NuGet feed URL +### Add the Syncfusion® NuGet feed URL #### Windows @@ -293,17 +293,17 @@ You should get the private Syncfusion® NuG 3. Expand the **NuGet Package Manager** and select **Package Sources**. -4. Click the **Add** button (green plus), and enter the ‘Package Name’ and ‘Package Source URL’ of the Syncfusion® NuGet packages. +4. Click the **Add** button (green plus), and enter the ‘Package Name’ and ‘Package Source URL’ of the Syncfusion® NuGet packages. **Name:** Name of the package source. - **Source:** Syncfusion® NuGet Feed URL. + **Source:** Syncfusion® NuGet Feed URL. - For example, Name: Syncfusion® AspNet Core Packages, Source: [https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore](https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore). + For example, Name: Syncfusion® AspNet Core Packages, Source: [https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore](https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore). 5. Click the **Update** button to add the name and source details to package sources. - ![NuGet Package Manager dialog with Syncfusion® Essential JS 2 NuGet feed URL for reference](NuGet_Packages_Images/img2.png) + ![NuGet Package Manager dialog with Syncfusion® Essential® JS 2 NuGet feed URL for reference](NuGet_Packages_Images/img2.png) #### macOS @@ -321,11 +321,11 @@ You should get the private Syncfusion® NuG **Name:** Name of the package source. - **Source:** Syncfusion® NuGet Feed URL. + **Source:** Syncfusion® NuGet Feed URL. - For example, Name: Syncfusion® ASP.NET Core Packages, Source: [https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore](https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore). + For example, Name: Syncfusion® ASP.NET Core Packages, Source: [https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore](https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore). - ![Add Package Source dialog to add Syncfusion® NuGet feed](NuGet_Packages_Images/img5.png) + ![Add Package Source dialog to add Syncfusion® NuGet feed](NuGet_Packages_Images/img5.png) 5. Now, click **Add Source** and then click **OK**. @@ -339,7 +339,7 @@ You should get the private Syncfusion® NuG nuget update -self ~~~ -2. Open the downloaded executable location in the command window, and run the following commands to configure the Syncfusion® NuGet packages: +2. Open the downloaded executable location in the command window, and run the following commands to configure the Syncfusion® NuGet packages: ~~~ #Add specified package source in NuGet.config file for Windows platform @@ -353,10 +353,10 @@ You should get the private Syncfusion® NuG ~~~ #For Windows platform - nuget.exe Sources Add –Name “Syncfusion Source” –Source “https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore” + nuget.exe Sources Add –Name “Syncfusion® Source” –Source “https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore” #For MAC/Linux platform - mono nuget.exe Sources Add –Name “Syncfusion Source” –Source “https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore” + mono nuget.exe Sources Add –Name “Syncfusion® Source” –Source “https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore” ~~~ diff --git a/Extension/Syncfusion-NuGet-Packages/NuGet-Uninstallation-process.md b/Extension/Syncfusion-NuGet-Packages/NuGet-Uninstallation-process.md index b5b3f906..2efae783 100644 --- a/Extension/Syncfusion-NuGet-Packages/NuGet-Uninstallation-process.md +++ b/Extension/Syncfusion-NuGet-Packages/NuGet-Uninstallation-process.md @@ -3,7 +3,7 @@ layout: post title: NuGet Uninstallation process | Extension | Syncfusion description: Describing the nuget uninstallation process using NuGet Package Manager dialog and Package Manager console window platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- @@ -12,33 +12,33 @@ documentation: ug ## NuGet Uninstallation by using NuGet Package Manager -You can uninstall already installed Syncfusion® NuGet packages from project using the following steps via NuGet Package Manager dialog. +You can uninstall already installed Syncfusion® NuGet packages from project using the following steps via NuGet Package Manager dialog. 1. Right-click on Project and select **Manage NuGet Packages** option. ![Installed packages details in NuGet Package Manager dialog](NuGet-Uninstallation_images/NuGet-Uninstallation-img2.png) -2. Select the **Installed** tab from NuGet Package Manager dialog and you can see the installed Syncfusion® NuGet packages list by giving the Syncfusion® keyword in search. +2. Select the **Installed** tab from NuGet Package Manager dialog and you can see the installed Syncfusion® NuGet packages list by giving the Syncfusion® keyword in search. ![Installed packages details in NuGet Package Manager dialog](NuGet-Uninstallation_images/NuGet-Uninstallation-img3.png) -3. Uninstall the Syncfusion® NuGet packages which are not required for the project. +3. Uninstall the Syncfusion® NuGet packages which are not required for the project. ![Installed packages details in NuGet Package Manager dialog](NuGet-Uninstallation_images/NuGet-Uninstallation-img1.png) N> You cannot uninstall the dependent package because of the package being referred in other NuGet Packages. It removes Project Reference and package from the project location. -4. If you don't want to uninstall the dependent NuGet packages when uninstall the Syncfusion® NuGet packages, you can select the **Ignore Dependencies** option to ignore the uninstallation for dependent packages. +4. If you don't want to uninstall the dependent NuGet packages when uninstall the Syncfusion® NuGet packages, you can select the **Ignore Dependencies** option to ignore the uninstallation for dependent packages. ![Installed packages details in NuGet Package Manager dialog](NuGet-Uninstallation_images/NuGet-Uninstallation-img4.png) ## NuGet Uninstallation by using Package Manager Console -You can uninstall already installed Syncfusion® NuGet packages from project using the following steps via Package Manager Console window. +You can uninstall already installed Syncfusion® NuGet packages from project using the following steps via Package Manager Console window. 1. Select the **Tools-> NuGet Package Manager-> Package Manager Console**. -2. Run the following command to uninstall the specified Syncfusion® NuGet Package with the package name. +2. Run the following command to uninstall the specified Syncfusion® NuGet Package with the package name. uninstall-package {package name} –RemoveDependencies diff --git a/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md b/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md index 178edac2..d589801a 100644 --- a/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md +++ b/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md @@ -1,40 +1,40 @@ --- layout: post -title: Syncfusion NuGet Package Licensing | Extension | Syncfusion -description: Syncfusion provides the license per developer licensing model. Each license is for a single named user not for any servers. +title: Syncfusion NuGet Package Licensing | Extension | Syncfusion +description: Syncfusion provides the license per developer licensing model. Each license is for a single named user not for any servers. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® NuGet Package Licensing +# Syncfusion® NuGet Package Licensing -Syncfusion provides the license per developer licensing model. Each license is for a single named user. Also, Syncfusion® doesn’t require separate license for any servers. So, if you have license for each developer it is not necessary to do license key registration to use the Syncfusion® NuGet packages. +Syncfusion® provides the license per developer licensing model. Each license is for a single named user. Also, Syncfusion® doesn’t require separate license for any servers. So, if you have license for each developer it is not necessary to do license key registration to use the Syncfusion® NuGet packages. -N> Syncfusion® removed the runtime and design time license key from v13.2.0.29 to v16.2.0.41. So, no need to register the license key either in application or system if you are using the Essential Studio® from v13.2.0.29 to v16.2.0.41 versions. +N> Syncfusion® removed the runtime and design time license key from v13.2.0.29 to v16.2.0.41. So, no need to register the license key either in application or system if you are using the Essential Studio® from v13.2.0.29 to v16.2.0.41 versions. -N> Syncfusion® removed the runtime and design time license key from v13.2.0.29 to v16.2.0.41. So, no need to register the license key either in application or system if you are using the Essential Studio® from v13.2.0.29 to v16.2.0.41 versions. +N> Syncfusion® removed the runtime and design time license key from v13.2.0.29 to v16.2.0.41. So, no need to register the license key either in application or system if you are using the Essential Studio® from v13.2.0.29 to v16.2.0.41 versions. -## How to register Syncfusion® license on or after to 16.2.0.41 version +## How to register Syncfusion® license on or after to 16.2.0.41 version -We have introduced a new licensing system starting with version 16.2.0.41 release of Essential Studio®. These changes apply to all evaluators and only to paid customers who use NuGet packages from [nuget.org](https://www.nuget.org/). Starting with v16.2.0.41, if you reference Syncfusion® assemblies from evaluation installer or from the NuGet feed, you also have to include a license key in your projects. Please note that this license key is different from the installer unlock key that you might have used in the past, and needs to be separately generated from Syncfusion® website. The following steps guide you as to how to register the Syncfusion® license. +We have introduced a new licensing system starting with version 16.2.0.41 release of Essential Studio®. These changes apply to all evaluators and only to paid customers who use NuGet packages from [nuget.org](https://www.nuget.org/). Starting with v16.2.0.41, if you reference Syncfusion® assemblies from evaluation installer or from the NuGet feed, you also have to include a license key in your projects. Please note that this license key is different from the installer unlock key that you might have used in the past, and needs to be separately generated from Syncfusion® website. The following steps guide you as to how to register the Syncfusion® license. -1. Generate the Syncfusion® License key by follow the steps from the [page](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) -2. Register the Syncfusion® license key in corresponding application by follow the steps from the [page](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-register-the-syncfusion-license-key) +1. Generate the Syncfusion® License key by follow the steps from the [page](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) +2. Register the Syncfusion® license key in corresponding application by follow the steps from the [page](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-register-the-syncfusion-license-key) - > Before register the Syncfusion® license key, ensure that all referenced Syncfusion® NuGet packages are all on the same version as license key version, because our license keys are version and platform-specific. + > Before register the Syncfusion® license key, ensure that all referenced Syncfusion® NuGet packages are all on the same version as license key version, because our license keys are version and platform-specific. -## How to register Syncfusion® license prior to 13.2.0.29 version +## How to register Syncfusion® license prior to 13.2.0.29 version -While using Syncfusion® NuGet package of version that is **prior to 13.2.0.29**, you need to register for the Syncfusion® license for development purpose. The following steps guide you as to how to register for the Syncfusion® license. +While using Syncfusion® NuGet package of version that is **prior to 13.2.0.29**, you need to register for the Syncfusion® license for development purpose. The following steps guide you as to how to register for the Syncfusion® license. -1. Download the [Syncfusion License](http://files2.syncfusion.com/Installs/Support/KB/RegisterProductkeyinBuildMachine.zip) Register tool and extract the file. +1. Download the [Syncfusion® License](http://files2.syncfusion.com/Installs/Support/KB/RegisterProductkeyinBuildMachine.zip) Register tool and extract the file. 2. Open the Command Prompt with administrator privileges. -3. Navigate to the root location of the extracted downloaded, Syncfusion® license. +3. Navigate to the root location of the extracted downloaded, Syncfusion® license. 4. Run the following command to register the Unlock key. Synckeynoui.exe “Unlock key” - N> You should provide the unlock key which is started with "@" and ended with "=" as a parameter for this Syncfusion® License tool. + N> You should provide the unlock key which is started with "@" and ended with "=" as a parameter for this Syncfusion® License tool. - ![Command for register the Syncfusion Unlock key](Register-the-Syncfusion-License-key_images/Register-the-Syncfusion-License-key-img1.png) + ![Command for register the Syncfusion® Unlock key](Register-the-Syncfusion-License-key_images/Register-the-Syncfusion-License-key-img1.png) diff --git a/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md b/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md index 000516e4..93a751d9 100644 --- a/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md +++ b/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md @@ -1,67 +1,67 @@ --- layout: post -title: Syncfusion NuGet Manager | Extension | Syncfusion -description: Syncfusion NuGet Package Manager is the utility that allows you to add, remove and update the Syncfusion NuGet sources (available platforms) to NuGet Package Manager +title: Syncfusion NuGet Manager | Extension | Syncfusion +description: Syncfusion NuGet Package Manager is the utility that allows you to add, remove and update the Syncfusion NuGet sources (available platforms) to NuGet Package Manager platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® NuGet Package Manager +# Syncfusion® NuGet Package Manager ## Overview -Syncfusion NuGet Package Manager is the utility that allows you to add, remove and update the Syncfusion® NuGet sources (available platforms) to NuGet Package Manager. Download the Syncfusion® NuGet Manager utility from [here](http://www.syncfusion.com/downloads/support/directtrac/general/ze/SyncfusionNuGetManager-2143130196). +Syncfusion® NuGet Package Manager is the utility that allows you to add, remove and update the Syncfusion® NuGet sources (available platforms) to NuGet Package Manager. Download the Syncfusion® NuGet Manager utility from [here](http://www.syncfusion.com/downloads/support/directtrac/general/ze/SyncfusionNuGetManager-2143130196). -## Add Syncfusion® NuGet Package sources +## Add Syncfusion® NuGet Package sources -The following steps directs you to add the Syncfusion® NuGet Package sources from Syncfusion® NuGet Manager. +The following steps directs you to add the Syncfusion® NuGet Package sources from Syncfusion® NuGet Manager. -1. Run the SyncfusionNuGetManager.exe from Syncfusion® NuGet Manager extracted location. +1. Run the SyncfusionNuGetManager.exe from Syncfusion® NuGet Manager extracted location. - ![Syncfusion NuGet Manager extracted location](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img1.png) + ![Syncfusion® NuGet Manager extracted location](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img1.png) -2. Syncfusion® NuGet Manager Window will be opened. +2. Syncfusion® NuGet Manager Window will be opened. - ![Syncfusion NuGet Manager main window](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img2.png) + ![Syncfusion® NuGet Manager main window](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img2.png) 3. Select the required platforms needed to be configured from “Select platforms to add” (Left side of the window) column and click Add>> button. - ![Selected platforms NuGet feed configure option in Syncfusion® NuGet Manager](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img3.png) + ![Selected platforms NuGet feed configure option in Syncfusion® NuGet Manager](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img3.png) -4. Now selected platforms will be added under “Selected platforms to remove” (Right side of the window) column. Click “Configure” button to add the required Syncfusion® Package sources to NuGet Package Manager. +4. Now selected platforms will be added under “Selected platforms to remove” (Right side of the window) column. Click “Configure” button to add the required Syncfusion® Package sources to NuGet Package Manager. - ![Selected platforms NuGet feed remove option in Syncfusion® NuGet Manager](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img4.png) + ![Selected platforms NuGet feed remove option in Syncfusion® NuGet Manager](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img4.png) -5. Once Syncfusion® NuGet Manager added the Syncfusion® NuGet sources, the changes will be reflected in package sources of your Visual Studio. +5. Once Syncfusion® NuGet Manager added the Syncfusion® NuGet sources, the changes will be reflected in package sources of your Visual Studio. - ![NuGet package manager dialog with Syncfusion® NuGet feeds](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img5.png) + ![NuGet package manager dialog with Syncfusion® NuGet feeds](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img5.png) -## Remove Syncfusion® NuGet Package sources +## Remove Syncfusion® NuGet Package sources -1. If any configured Syncfusion® NuGet Package sources are no longer required, Select the unwanted platforms from “Select platforms to remove” (Right side of the window) column and click <® NuGet Manager to remove the already configured Syncfusion® NuGet feed](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img6.png) + ![Remove option in Syncfusion® NuGet Manager to remove the already configured Syncfusion® NuGet feed](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img6.png) -2. Now selected platforms will be added under “Selected platforms to add” (Left side of the window) column. Click “Configure” button to remove the required Syncfusion® Package sources to NuGet Package Manager. +2. Now selected platforms will be added under “Selected platforms to add” (Left side of the window) column. Click “Configure” button to remove the required Syncfusion® Package sources to NuGet Package Manager. -3. Once Syncfusion® NuGet Manager removed the Syncfusion® NuGet sources, the changes will be reflected in NuGet.config file of your machine and updated the same in available package sources of your Visual Studio. +3. Once Syncfusion® NuGet Manager removed the Syncfusion® NuGet sources, the changes will be reflected in NuGet.config file of your machine and updated the same in available package sources of your Visual Studio. -## Syncfusion® NuGet Manager command line +## Syncfusion® NuGet Manager command line -The following steps directs you to use the Syncfusion® NuGet Manager from command line. +The following steps directs you to use the Syncfusion® NuGet Manager from command line. 1. Open Windows Command Prompt in Administrator Mode. -2. Navigate to SyncfusionNuGetManager.exe from Syncfusion® NuGet Manager extracted location. +2. Navigate to SyncfusionNuGetManager.exe from Syncfusion® NuGet Manager extracted location. -3. Run SyncfusionNuGetManager.exe with required platforms arguments. Refer the below table for platform as arguments to configure the Syncfusion® NuGet Packages sources. +3. Run SyncfusionNuGetManager.exe with required platforms arguments. Refer the below table for platform as arguments to configure the Syncfusion® NuGet Packages sources. - ![Command to add Syncfusion® NuGet feed](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img8.jpeg) + ![Command to add Syncfusion® NuGet feed](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img8.jpeg) **Add** -To add the Syncfusion® NuGet feed link with below command. +To add the Syncfusion® NuGet feed link with below command. SyncfusionNuGetManager.exe Add [platform key] @@ -77,7 +77,7 @@ Example:SyncfusionNuGetManager.exe Update JavaScript “D:\Syncfusion\JavaScript **Remove** -To remove the configured Syncfusion® NuGet by below command. +To remove the configured Syncfusion® NuGet by below command. SyncfusionNuGetManager.exe Remove [platform key] [local NuGet Location] @@ -150,7 +150,7 @@ Here the list of keyword for platform keys to access.
-4. Once Syncfusion® NuGet Manager removed the Syncfusion® NuGet sources, the changes will be reflected in NuGet.config file of your machine and updated the same in available package sources of your Visual Studio. +4. Once Syncfusion® NuGet Manager removed the Syncfusion® NuGet sources, the changes will be reflected in NuGet.config file of your machine and updated the same in available package sources of your Visual Studio. - ![NuGet package manager dialog with Syncfusion NuGet feeds](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img5.png) + ![NuGet package manager dialog with Syncfusion® NuGet feeds](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img5.png) diff --git a/Extension/Syncfusion-Reference-Manager/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger.md b/Extension/Syncfusion-Reference-Manager/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger.md index 8bfdfd7b..05ec8098 100644 --- a/Extension/Syncfusion-Reference-Manager/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger.md +++ b/Extension/Syncfusion-Reference-Manager/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger.md @@ -3,65 +3,65 @@ layout: post title: Add Reference Manger | Extension | Syncfusion description: Learn here all about how to add a syncfusion Essential references via reference manger in Extenion, it's elements and more. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Add a Syncfusion® References via Syncfusion® Reference Manger +# Add a Syncfusion® References via Syncfusion® Reference Manger -The Add-In launches a pop-up window that contains the list of Syncfusion® controls that are loaded, based on the platform of the project. If it is a WPF project, all the Syncfusion® WPF controls are loaded. +The Add-In launches a pop-up window that contains the list of Syncfusion® controls that are loaded, based on the platform of the project. If it is a WPF project, all the Syncfusion® WPF controls are loaded. To add the assemblies: -1. Select the Syncfusion® Reference Manager either in the WPF, Windows Forms/Console/Class Library or Silverlight Project. -2. The Syncfusion Reference Manager dialog is displayed as shown in the following screenshot. +1. Select the Syncfusion® Reference Manager either in the WPF, Windows Forms/Console/Class Library or Silverlight Project. +2. The Syncfusion® Reference Manager dialog is displayed as shown in the following screenshot. - ![Syncfusion Reference Manger Wizard](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img1.png) + ![Syncfusion® Reference Manger Wizard](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img1.png) -3. If launched the Syncfusion® Reference Manager from Console/Class Library project, Platform selection option will be appeared as option in Syncfusion® Reference Manager. Choose the required platform based on your need. +3. If launched the Syncfusion® Reference Manager from Console/Class Library project, Platform selection option will be appeared as option in Syncfusion® Reference Manager. Choose the required platform based on your need. - ![Platform selection option in Syncfusion Reference Manger](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img6.png) + ![Platform selection option in Syncfusion® Reference Manger](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img6.png) - N> Platform selection option will be appeared only if Essential Studio® for Enterprise Edition with the platforms WPF and Windows Forms has been installed or both Essential Studio® for WPF and Essential Studio® for Windows Forms has been installed. + N> Platform selection option will be appeared only if Essential Studio® for Enterprise Edition with the platforms WPF and Windows Forms has been installed or both Essential Studio® for WPF and Essential Studio® for Windows Forms has been installed. -4. If launched the Syncfusion® Reference Manager from WPF project or select the WPF platform from platform selection option, **Themes** option will be appeared as option in Syncfusion® Reference Manger. Choose the required themes based on your need. Refer the below link to know more about built in themes and its available assemblies. +4. If launched the Syncfusion® Reference Manager from WPF project or select the WPF platform from platform selection option, **Themes** option will be appeared as option in Syncfusion® Reference Manger. Choose the required themes based on your need. Refer the below link to know more about built in themes and its available assemblies. [https://help.syncfusion.com/wpf/themes/skin-manager](https://help.syncfusion.com/wpf/themes/skin-manager) - ![Themes selection option in Syncfusion Reference Manger](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img4.png) + ![Themes selection option in Syncfusion® Reference Manger](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img4.png) N> Themes option will be enabled only if selected SfSkinManager supported controls. - ![Tooltip information for Syncfusion Reference Manager themes option](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img5.png) + ![Tooltip information for Syncfusion® Reference Manager themes option](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img5.png) 5. Reference assemblies - * You can add Syncfusion® assemblies from NuGet packages, the build installed location, or by using the GAC location. This option determines the location of the assemblies that are referenced in the project. + * You can add Syncfusion® assemblies from NuGet packages, the build installed location, or by using the GAC location. This option determines the location of the assemblies that are referenced in the project. - N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® setup has been installed. + N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® setup has been installed. - ![Options for assembly location in Syncfusion Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img8.png) + ![Options for assembly location in Syncfusion® Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img8.png) N> The GAC option will not be available if you have selected a .NET 7.0 or .NET 6.0 application in Visual Studio 2022. - * Select the Syncfusion® Essential Studio® versions that were previously installed on your machine.This option determines the assembly version that is referenced in the project. + * Select the Syncfusion® Essential Studio® versions that were previously installed on your machine.This option determines the assembly version that is referenced in the project. - ![Versions for assemblies in Syncfusion Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img9.png) + ![Versions for assemblies in Syncfusion® Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img9.png) * Choose the required controls that you want include in project 6. Click Done to add the required assemblies for the selected controls into the project. The following screenshot shows the list of required assemblies for the selected controls to be added. - ![Syncfusion Reference Manager new assemblies add information dialog](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img2.png) + ![Syncfusion® Reference Manager new assemblies add information dialog](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img2.png) -7. Click OK. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion assemblies have been added successfully” in Visual Studio status bar. +7. Click OK. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar. - ![Syncfusion Reference Manager success status in Visual Studio status bar](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img3.png) + ![Syncfusion® Reference Manager success status in Visual Studio status bar](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img3.png) -8. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +8. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img7.png) + ![Syncfusion® license registration required information dialog in Syncfusion® Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img7.png) -N> We are providing Syncfusion® Reference Manager support for specific framework which is shipped (assemblies) in our Syncfusion® Essential Studio® setup. So, if we try to add Syncfusion® assemblies in project and project framework is not supported with selected Syncfusion® version assemblies, the dialog will be appeared along with **“Current build v{version} is not supported this framework v{Framework Version}”** message. +N> We are providing Syncfusion® Reference Manager support for specific framework which is shipped (assemblies) in our Syncfusion® Essential Studio® setup. So, if we try to add Syncfusion® assemblies in project and project framework is not supported with selected Syncfusion® version assemblies, the dialog will be appeared along with **“Current build v{version} is not supported this framework v{Framework Version}”** message. diff --git a/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md b/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md index e4fb51ed..d2f9d394 100644 --- a/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md +++ b/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md @@ -3,26 +3,26 @@ layout: post title: Reference Manager | Extension | Syncfusion description: configure syncfusion assemblies in visual studio project platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Configure Syncfusion® assemblies in Visual Studio project +# Configure Syncfusion® assemblies in Visual Studio project -To open Syncfusion® Reference Manager Wizard, follow either one of the options below: +To open Syncfusion® Reference Manager Wizard, follow either one of the options below: **Option 1:** -Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms/WPF > Add References…** or any other Form in **Visual Studio**. +Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms/WPF > Add References…** or any other Form in **Visual Studio**. -![Syncfusion Reference Manager via Syncfusion Menu](Configure-Syncfusion-assemblies-in-Visual-Studio-project_images/Syncfusion_Menu_AddReference.png) +![Syncfusion® Reference Manager via Syncfusion® Menu](Configure-Syncfusion-assemblies-in-Visual-Studio-project_images/Syncfusion_Menu_AddReference.png) -N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. +N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** -Right-click the selected project file from Solution Explorer, then select **Syncfusion® Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio. +Right-click the selected project file from Solution Explorer, then select **Syncfusion® Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio. -![Syncfusion Reference Manager add-in](Configure-Syncfusion-assemblies-in-Visual-Studio-project_images/Configure-Syncfusion-assemblies-in-Visual-Studio-project-img1.png) +![Syncfusion® Reference Manager add-in](Configure-Syncfusion-assemblies-in-Visual-Studio-project_images/Configure-Syncfusion-assemblies-in-Visual-Studio-project-img1.png) diff --git a/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md b/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md index 70b508f9..8631ac87 100644 --- a/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md +++ b/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md @@ -1,36 +1,36 @@ --- layout: post -title: Migrate the Syncfusion assemblies | Extension | Syncfusion -description: The Syncfusion Reference Manager can migrate the Syncfusion assemblies to selected version of Syncfusion assemblies when you want to migrate from one version to another version, the Syncfusion references in the project +title: Migrate the Syncfusion assemblies | Extension | Syncfusion +description: The Syncfusion Reference Manager can migrate the Syncfusion assemblies to selected version of Syncfusion assemblies when you want to migrate from one version to another version, the Syncfusion references in the project platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Migrate the Syncfusion® assemblies +# Migrate the Syncfusion® assemblies -The Syncfusion® Reference Manager can migrate the Syncfusion® assemblies to selected version of Syncfusion® assemblies when you want to migrate from one version to another version, the Syncfusion® references in the project. +The Syncfusion® Reference Manager can migrate the Syncfusion® assemblies to selected version of Syncfusion® assemblies when you want to migrate from one version to another version, the Syncfusion® references in the project. -To migrate the Syncfusion® assemblies, +To migrate the Syncfusion® assemblies, -1. Open the project you would like to migrate with another version of Syncfusion® assemblies. -2. Select the option Syncfusion Reference Manager in the WPF or Windows Forms or Silverlight Project. -3. The dialog Syncfusion Reference Manager is opened. Then choose the required Syncfusion® Essential Studio® version to migrate the project. Refer the following +1. Open the project you would like to migrate with another version of Syncfusion® assemblies. +2. Select the option Syncfusion® Reference Manager in the WPF or Windows Forms or Silverlight Project. +3. The dialog Syncfusion® Reference Manager is opened. Then choose the required Syncfusion® Essential Studio® version to migrate the project. Refer the following screenshots for more information. - ![Syncfusion Reference Manager version selection option](Migrate-the-Syncfusion-assemblies_images/Migrate-the-Syncfusion-assemblies-img1.png) + ![Syncfusion® Reference Manager version selection option](Migrate-the-Syncfusion-assemblies_images/Migrate-the-Syncfusion-assemblies-img1.png) 4. When you want to add controls additionally, select controls while the migration is in process. Otherwise, do not select any control. 5. Click Done. The following screenshot shows the list of assemblies to be migrated. - ![Syncfusion Reference Manager backup dialog with the migrating assembly details](Migrate-the-Syncfusion-assemblies_images/Migrate-the-Syncfusion-assemblies-img2.png) + ![Syncfusion® Reference Manager backup dialog with the migrating assembly details](Migrate-the-Syncfusion-assemblies_images/Migrate-the-Syncfusion-assemblies-img2.png) 6. The option Backup Project copies the project into the Backup folder in the same project location before migration. -7. Then click OK. The project is migrated to the selected versions of the Syncfusion® assembly reference. +7. Then click OK. The project is migrated to the selected versions of the Syncfusion® assembly reference. diff --git a/Extension/Syncfusion-Reference-Manager/Overview.md b/Extension/Syncfusion-Reference-Manager/Overview.md index 9ff13e29..065b3c64 100644 --- a/Extension/Syncfusion-Reference-Manager/Overview.md +++ b/Extension/Syncfusion-Reference-Manager/Overview.md @@ -1,17 +1,17 @@ --- layout: post -title: Syncfusion Reference Manager | Extension | Syncfusion -description: Learn here all about adding the required Syncfusion assembly to Windows project reference based on the selected control(s). +title: Syncfusion Reference Manager | Extension | Syncfusion +description: Learn here all about adding the required Syncfusion assembly to Windows project reference based on the selected control(s). platform: extension control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Reference Manager +# Syncfusion® Reference Manager -Syncfusion Reference Manager is the Visual Studio Add-In for WPF, Windows Forms and Silverlight platforms. It adds the Syncfusion® assembly reference to the project, either from the GAC location or from Essential Studio® installed location or from NuGet packages. It can also migrate the projects that contain the old versions of the Syncfusion® assembly reference to newer or specific versions of the Syncfusion® assembly reference. It supports Microsoft Visual Studio 2010 or higher. This Visual Studio extension is included from Essential Studio® 2013 Volume 3 release. +Syncfusion® Reference Manager is the Visual Studio Add-In for WPF, Windows Forms and Silverlight platforms. It adds the Syncfusion® assembly reference to the project, either from the GAC location or from Essential Studio® installed location or from NuGet packages. It can also migrate the projects that contain the old versions of the Syncfusion® assembly reference to newer or specific versions of the Syncfusion® assembly reference. It supports Microsoft Visual Studio 2010 or higher. This Visual Studio extension is included from Essential Studio® 2013 Volume 3 release. -N> This Reference Manager can be applied to a project for Syncfusion® assembly versions 10.4.0.71 and later. +N> This Reference Manager can be applied to a project for Syncfusion® assembly versions 10.4.0.71 and later. diff --git a/Extension/Syncfusion-Troubleshooter/Overview.md b/Extension/Syncfusion-Troubleshooter/Overview.md index d62a2413..029b06cc 100644 --- a/Extension/Syncfusion-Troubleshooter/Overview.md +++ b/Extension/Syncfusion-Troubleshooter/Overview.md @@ -1,15 +1,15 @@ --- layout: post -title: Syncfusion Troubleshooter | Extension | Syncfusion -description: The Syncfusion Troubleshooter is a Visual Studio extension to troubleshoot the configuration issues of Syncfusion controls in projects. If Visual Studio project has any configuration issue with in Syncfusion control like, wrong Framework Syncfusion assembly added to the project or missing any Syncfusion dependent assembly of a referred assembly, the Syncfusion Troubleshooter will investigate these type of problem and fix them +title: Syncfusion Troubleshooter | Extension | Syncfusion +description: The Syncfusion Troubleshooter is a Visual Studio extension to troubleshoot the configuration issues of Syncfusion controls in projects. If Visual Studio project has any configuration issue with in Syncfusion control like, wrong Framework Syncfusion assembly added to the project or missing any Syncfusion dependent assembly of a referred assembly, the Syncfusion Troubleshooter will investigate these type of problem and fix them platform: extension control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Troubleshooter +# Syncfusion® Troubleshooter -The Syncfusion® Troubleshooter is a Visual Studio extension to troubleshoot the configuration issues of Syncfusion® controls in projects. It supports Microsoft Visual Studio 2010 or higher. If Visual Studio project has any configuration issue with in Syncfusion® control like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly, the Syncfusion® Troubleshooter will investigate these type of problem and fix them. The Syncfusion® Troubleshooter available from Syncfusion® Essential Studio® v14.3.0.49. Currently the Syncfusion® Troubleshooter is available for the following project types. +The Syncfusion® Troubleshooter is a Visual Studio extension to troubleshoot the configuration issues of Syncfusion® controls in projects. It supports Microsoft Visual Studio 2010 or higher. If Visual Studio project has any configuration issue with in Syncfusion® control like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly, the Syncfusion® Troubleshooter will investigate these type of problem and fix them. The Syncfusion® Troubleshooter available from Syncfusion® Essential Studio® v14.3.0.49. Currently the Syncfusion® Troubleshooter is available for the following project types. * Windows Forms Application. @@ -23,18 +23,18 @@ The Syncfusion® Troubleshooter is a Visual * Universal Windows Platform Application. -The Syncfusion® Troubleshooter Visual Studio extension is installed along with the following Essential Studio® setups. +The Syncfusion® Troubleshooter Visual Studio extension is installed along with the following Essential Studio® setups. -* Essential Studio® for Windows Forms. +* Essential Studio® for Windows Forms. -* Essential Studio® for WPF. +* Essential Studio® for WPF. -* Essential Studio® for ASP.NET Web Forms. +* Essential Studio® for ASP.NET Web Forms. -* Essential Studio® for ASP.NET MVC. +* Essential Studio® for ASP.NET MVC. -* Essential Studio® for ASP.NET Core. +* Essential Studio® for ASP.NET Core. -* Essential Studio® for UWP. +* Essential Studio® for UWP. -* Essential Studio® Enterprise Edition with any platform of mentioned above. +* Essential Studio® Enterprise Edition with any platform of mentioned above. diff --git a/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md b/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md index 0e795639..6c43f35a 100644 --- a/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md +++ b/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md @@ -1,15 +1,15 @@ --- layout: post -title: Syncfusion Troubleshooter | Extension | Syncfusion -description: Syncfusion Troubleshooter is Visual Studio extension to troubleshoot the configuration issues in Syncfusion assembly reference, webconfig entries in projects. +title: Syncfusion Troubleshooter | Extension | Syncfusion +description: Syncfusion Troubleshooter is Visual Studio extension to troubleshoot the configuration issues in Syncfusion assembly reference, webconfig entries in projects. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Troubleshoot the project -The Syncfusion® Troubleshooter will be installed in Visual Studio along with Syncfusion® Essential Studio® setup installation. The Syncfusion® Troubleshooter can be done the below items, +The Syncfusion® Troubleshooter will be installed in Visual Studio along with Syncfusion® Essential Studio® setup installation. The Syncfusion® Troubleshooter can be done the below items, 1. Report the Configuration issues. @@ -17,35 +17,35 @@ The Syncfusion® Troubleshooter will be ins ## Report the Configuration issues -The following steps help you to utilize the Syncfusion® Troubleshooter by Visual Studio. +The following steps help you to utilize the Syncfusion® Troubleshooter by Visual Studio. -1. To open Syncfusion® Troubleshooter Wizard, follow either one of the options below: +1. To open Syncfusion® Troubleshooter Wizard, follow either one of the options below: **Option 1:** - Open an existing Syncfusion® Application, choose **Syncfusion menu**. Then select corresponding platform menu and click **Troubleshoot…** + Open an existing Syncfusion® Application, choose **Syncfusion® menu**. Then select corresponding platform menu and click **Troubleshoot…** - ![Syncfusion Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) + ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) - N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** - Right-click the Project file in Solution Explorer, then select the command **Syncfusion Troubleshooter…** Refer to the following screenshot for more information. + Right-click the Project file in Solution Explorer, then select the command **Syncfusion® Troubleshooter…** Refer to the following screenshot for more information. - ![Syncfusion Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.jpeg) + ![Syncfusion® Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.jpeg) -2. Now it’s analyze the project and it will report the project configuration issues of Syncfusion® controls in the Troubleshooter dialog if any issues found. If the project doesn’t have any configuration issue, the dialog box will show there is no configuration changes required in following areas, +2. Now it’s analyze the project and it will report the project configuration issues of Syncfusion® controls in the Troubleshooter dialog if any issues found. If the project doesn’t have any configuration issue, the dialog box will show there is no configuration changes required in following areas, - * Syncfusion® assembly references. + * Syncfusion® assembly references. - * Syncfusion® Web.config entries. + * Syncfusion® Web.config entries. - * Syncfusion® NuGet Packages. + * Syncfusion® NuGet Packages. ![No configuration changes required dialog box](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img2.jpeg) -I> The Syncfusion® Troubleshooter command will be visible only for Syncfusion® projects that means the project should contain Syncfusion® assemblies or Syncfusion® NuGet packages referred. +I> The Syncfusion® Troubleshooter command will be visible only for Syncfusion® projects that means the project should contain Syncfusion® assemblies or Syncfusion® NuGet packages referred. -Syncfusion Troubleshooter handles the below project configuration issues, +Syncfusion® Troubleshooter handles the below project configuration issues, 1. Assembly Reference Issues. @@ -55,25 +55,25 @@ Syncfusion Troubleshooter handles the below project configuration issues, ### Assembly Reference Issues -The Syncfusion® Troubleshooter deals with below assembly reference issues in Syncfusion® Projects. +The Syncfusion® Troubleshooter deals with below assembly reference issues in Syncfusion® Projects. 1. Dependent assemblies are missing for referred assemblies from project. - **For Instance:** If “Syncfusion.Tools.WPF” assembly referred in project and “Syncfusion.Shared.WPF” (dependent of Syncfusion.Tools.WPF) not referred in project, Syncfusion® Troubleshooter will be shown dependent assembly missing. + **For Instance:** If “Syncfusion.Tools.WPF” assembly referred in project and “Syncfusion.Shared.WPF” (dependent of Syncfusion.Tools.WPF) not referred in project, Syncfusion® Troubleshooter will be shown dependent assembly missing. ![Dependent assemblies missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img3.jpg) -2. Syncfusion® assembly version mismatched. Compare to all Syncfusion® assembly’s versions are in same project. If found any Syncfusion® assembly version inconsistency, Syncfusion® Troubleshooter will be shown Syncfusion® assemblies version mismatched. +2. Syncfusion® assembly version mismatched. Compare to all Syncfusion® assembly’s versions are in same project. If found any Syncfusion® assembly version inconsistency, Syncfusion® Troubleshooter will be shown Syncfusion® assemblies version mismatched. - **For Instance:** If “Syncfusion.Tools.WPF” assembly (v15.2450.0.43) referred in project, but other Syncfusion® assemblies referred assembly version is v15.2450.0.40. Syncfusion® Troubleshooter will be shown Syncfusion® assembly version mismatched. + **For Instance:** If “Syncfusion.Tools.WPF” assembly (v15.2450.0.43) referred in project, but other Syncfusion® assemblies referred assembly version is v15.2450.0.40. Syncfusion® Troubleshooter will be shown Syncfusion® assembly version mismatched. ![Assembly version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img4.jpg) -3. Framework version mismatching (Syncfusion Assemblies) with project’s .NET Framework version. Find the supported .NET Framework details for Syncfusion® assemblies in below link, +3. Framework version mismatching (Syncfusion® Assemblies) with project’s .NET Framework version. Find the supported .NET Framework details for Syncfusion® assemblies in below link, - **For Instance:** The.NET Framework of the application is v4.5 and “Syncfusion.Tools.WPF” assembly (v15.2400.0.43 & .NET Framework version 4.0) referred in same application. The Syncfusion® Troubleshooter will be shown Syncfusion® assembly .NET Framework version is incompatible with project’s .NET Framework version. + **For Instance:** The.NET Framework of the application is v4.5 and “Syncfusion.Tools.WPF” assembly (v15.2400.0.43 & .NET Framework version 4.0) referred in same application. The Syncfusion® Troubleshooter will be shown Syncfusion® assembly .NET Framework version is incompatible with project’s .NET Framework version. ![Target Framework version of application](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img5.jpg) @@ -81,61 +81,61 @@ The Syncfusion® Troubleshooter deals with ### Web.config Issues (for Web applications) -The Syncfusion® Troubleshooter deals with below web.config issues in Syncfusion® web projects. +The Syncfusion® Troubleshooter deals with below web.config issues in Syncfusion® web projects. -1. Syncfusion® assembly entry version mismatched. Each Syncfusion® assembly entry version/.NET Framework version will be compared with corresponding referred Syncfusion® assembly in the application. +1. Syncfusion® assembly entry version mismatched. Each Syncfusion® assembly entry version/.NET Framework version will be compared with corresponding referred Syncfusion® assembly in the application. - **For Instance:** If “Syncfusion.EJ.Export” assembly (v15.2450.0.46) referred in project, But “Syncfusion.EJ.Export” assembly entry version (v15.2450.0.33) in Web.config file. Syncfusion® Troubleshooter will be shown Syncfusion® assembly entry version mismatched. + **For Instance:** If “Syncfusion.EJ.Export” assembly (v15.2450.0.46) referred in project, But “Syncfusion.EJ.Export” assembly entry version (v15.2450.0.33) in Web.config file. Syncfusion® Troubleshooter will be shown Syncfusion® assembly entry version mismatched. - ![Syncfusion reference assembly entry version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.jpg) + ![Syncfusion® reference assembly entry version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.jpg) -2. Multiple version and Duplicate Syncfusion® assembly entry. Syncfusion® Troubleshooter will show the duplicate assembly entry when Syncfusion® assembly entry presented in Web.config which is not referred in project or multiple Syncfusion® assembly entry in Web.config for same Syncfusion® assembly. +2. Multiple version and Duplicate Syncfusion® assembly entry. Syncfusion® Troubleshooter will show the duplicate assembly entry when Syncfusion® assembly entry presented in Web.config which is not referred in project or multiple Syncfusion® assembly entry in Web.config for same Syncfusion® assembly. - **For Instance:** If project have “Syncfusion.EJ.Pivot” assembly (v15.2450.0.43) entry in Web.config file, But “Syncfusion.EJ.Pivot” assembly not referred in project. Syncfusion® Troubleshooter will be show Duplicate assembly entry. + **For Instance:** If project have “Syncfusion.EJ.Pivot” assembly (v15.2450.0.43) entry in Web.config file, But “Syncfusion.EJ.Pivot” assembly not referred in project. Syncfusion® Troubleshooter will be show Duplicate assembly entry. - ![Duplicate Syncfusion® reference assembly entry issue shown in Troubleshooter wizard ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.jpg) + ![Duplicate Syncfusion® reference assembly entry issue shown in Troubleshooter wizard ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.jpg) - **For Instance:** If project Multiple “Syncfusion.EJ” assembly (v15.2400.0.46 && v15.2460.0.46) entry with mismatched assembly version/.NET Framework version in Web.config, Syncfusion® Troubleshooter will show the Duplicate assembly entry and Multiple Syncfusion® assembly entries. + **For Instance:** If project Multiple “Syncfusion.EJ” assembly (v15.2400.0.46 && v15.2460.0.46) entry with mismatched assembly version/.NET Framework version in Web.config, Syncfusion® Troubleshooter will show the Duplicate assembly entry and Multiple Syncfusion® assembly entries. - ![Multiple version Syncfusion® reference assembly entry issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.jpg) + ![Multiple version Syncfusion® reference assembly entry issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.jpg) -3. Namespace entry missing. If any Syncfusion® namespaces are missing in Web.config that is related to referred Syncfusion® assemblies in project, Syncfusion® Troubleshooter will show namespace entry is missing. +3. Namespace entry missing. If any Syncfusion® namespaces are missing in Web.config that is related to referred Syncfusion® assemblies in project, ® Troubleshooter will show namespace entry is missing. - **For Instance:** If “Syncfusion.EJ.MVC” assembly (v15.2450.0.46) referred in project and “Syncfusion.MVC.EJ” namespace entry missing in Web.config file, Syncfusion® Troubleshooter will show Syncfusion® namespace entry missing. + **For Instance:** If “Syncfusion.EJ.MVC” assembly (v15.2450.0.46) referred in project and “Syncfusion.MVC.EJ” namespace entry missing in Web.config file, Syncfusion® Troubleshooter will show Syncfusion® namespace entry missing. ![Namespace entry missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.jpg) -4. Namespace entry version mismatched. If any Namespace entry version (assembly version) mismatched with corresponding referred assembly version in ASP.NET Web Application, Syncfusion® Troubleshooter will be shown Namespace entry version mismatched. +4. Namespace entry version mismatched. If any Namespace entry version (assembly version) mismatched with corresponding referred assembly version in ASP.NET Web Application, Syncfusion® Troubleshooter will be shown Namespace entry version mismatched. - **For Instance:** If “Syncfusion.EJ” assembly (v15.2450.0.46) referred in project and “Syncfusion.JavaScript.DataVisualization” Namespace entry version (v15.2450.0.43) in Web.config file. Syncfusion® Troubleshooter will be show Syncfusion® namespace entry version mismatched. + **For Instance:** If “Syncfusion.EJ” assembly (v15.2450.0.46) referred in project and “Syncfusion.JavaScript.DataVisualization” Namespace entry version (v15.2450.0.43) in Web.config file. Syncfusion® Troubleshooter will be show Syncfusion® namespace entry version mismatched. - ![Syncfusion namespace entry version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.jpg) + ![Syncfusion® namespace entry version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.jpg) -5. HTTP/Server handler entry mismatched. HTTP/Server handler entry version compare to corresponding referred assembly version in project. If any Syncfusion® HTTP/Server handler entry version mismatched, Syncfusion® Troubleshooter will show HTTP/Server handler entry mismatched. +5. HTTP/Server handler entry mismatched. HTTP/Server handler entry version compare to corresponding referred assembly version in project. If any Syncfusion® HTTP/Server handler entry version mismatched, Syncfusion® Troubleshooter will show HTTP/Server handler entry mismatched. - **For Instance:** If “Syncfusion.EJ.” assembly (v15.2450.0.46) referred in project, But “Syncfusion.JavaScript.ImageHandler” HTTP/Server handler entry version (v15.2450.0.43) in Web.config file. Syncfusion® Troubleshooter will be show Syncfusion® HTTP/Server handler entry version mismatched. + **For Instance:** If “Syncfusion.EJ.” assembly (v15.2450.0.46) referred in project, But “Syncfusion.JavaScript.ImageHandler” HTTP/Server handler entry version (v15.2450.0.43) in Web.config file. Syncfusion® Troubleshooter will be show Syncfusion® HTTP/Server handler entry version mismatched. - ![Syncfusion HTTP/Server handler entry mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.jpg) + ![Syncfusion® HTTP/Server handler entry mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.jpg) ### NuGet Issues -The Syncfusion® Troubleshooter deals with below NuGet package related issues in Syncfusion® projects. +The Syncfusion® Troubleshooter deals with below NuGet package related issues in Syncfusion® projects. -1. Multiple versions of Syncfusion® NuGet Packages are installed. If Syncfusion® NuGet Package version is differ from other Syncfusion® NuGet Package version, Syncfusion® Troubleshooter will be shown Syncfusion® NuGet package version is mismatched. +1. Multiple versions of Syncfusion® NuGet Packages are installed. If Syncfusion® NuGet Package version is differ from other Syncfusion® NuGet Package version, Syncfusion® Troubleshooter will be shown Syncfusion® NuGet package version is mismatched. - **For Instance:** Syncfusion.Web,Base package installed multiple version(v15.2.0.43 & v15.2.0.46), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched. + **For Instance:** Syncfusion.Web,Base package installed multiple version(v15.2.0.43 & v15.2.0.46), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched. - ![Syncfusion NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpg) + ![Syncfusion® NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpg) -2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version. +2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version. - **For Instance:** Syncfusion.Calculate.Base NuGet package version(v15.2.0.46 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, Syncfusion® Troubleshooter will be show Syncfusion® package Framework version is mismatched. + **For Instance:** Syncfusion.Calculate.Base NuGet package version(v15.2.0.46 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, Syncfusion® Troubleshooter will be show Syncfusion® package Framework version is mismatched. - ![Syncfusion NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpg) + ![Syncfusion® NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpg) -3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. +3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. - **For Instance:** If install Syncfusion.Calculate.WPF NuGet package alone in project, Syncfusion® Troubleshooter will show the Syncfusion.Calculate.Base dependent NuGet package missing. + **For Instance:** If install Syncfusion.Calculate.WPF NuGet package alone in project, Syncfusion® Troubleshooter will show the Syncfusion.Calculate.Base dependent NuGet package missing. ![Dependent NuGet package missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.jpg) @@ -143,18 +143,18 @@ I> Internet connection is required to restore the missing dependent packages. If ## Apply the solution -1. Once the Syncfusion® Troubleshooter dialog loads, check the corresponding check box of the issue which you need to resolve. Then click the "Fix Issue(s)" button. +1. Once the Syncfusion® Troubleshooter dialog loads, check the corresponding check box of the issue which you need to resolve. Then click the "Fix Issue(s)" button. - ![Syncfusion Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img16.jpeg) + ![Syncfusion® Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img16.jpeg) 2. A dialog appears, which will ask to take a backup of the project before perform the troubleshooting process. If you need to backup the project before troubleshooting click “Yes” button. - ![Syncfusion Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img17.jpeg) + ![Syncfusion® Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img17.jpeg) -3. Wait for a while, the Syncfusion® Troubleshooter is being resolve the selected issues. Once the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully.” +3. Wait for a while, the Syncfusion® Troubleshooter is being resolve the selected issues. Once the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully.” - ![Syncfusion Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img18.jpeg) + ![Syncfusion® Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img18.jpeg) -4. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post for understanding the licensing changes introduced in Essential Studio. +4. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img19.jpeg) \ No newline at end of file + ![Syncfusion® license registration required information dialog in Syncfusion® Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img19.jpeg) \ No newline at end of file diff --git a/Extension/Syncfusion-Updates/Essential-Studio.md b/Extension/Syncfusion-Updates/Essential-Studio.md index a4ea130b..c5e323a1 100644 --- a/Extension/Syncfusion-Updates/Essential-Studio.md +++ b/Extension/Syncfusion-Updates/Essential-Studio.md @@ -1,31 +1,31 @@ --- layout: post -title: Check for updates | Extension | Syncfusion -description: The Syncfusion check for updates automatically retrieves the latest Essential Studio and provide the download option. +title: Check for updates | Extension | Syncfusion +description: The Syncfusion check for updates automatically retrieves the latest Essential Studio and provide the download option. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Update Essential Studio® to the most recent release +# Update Essential Studio® to the most recent release -Syncfusion® provides the Extensions to update most recent version of the Essential Studio® release. So that, you always get the latest features, fixes, and improvements by installing the latest version. +Syncfusion® provides the Extensions to update most recent version of the Essential Studio® release. So that, you always get the latest features, fixes, and improvements by installing the latest version. -I> The Syncfusion® Check for updates extension is available from v17.1.0.32. +I> The Syncfusion® Check for updates extension is available from v17.1.0.32. You can check updates availability in Visual Studio, and then install the update version if required. -1. Choose **Syncfusion® ** **->** **Check** **for** **Updates…** in the Visual Studio menu. +1. Choose **Syncfusion®** **->** **Check** **for** **Updates…** in the Visual Studio menu. ![Check for updates menu](CheckForUpdates_Images/CheckForUpdatesMenu.png) - N> *In Visual Studio 2019, Choose **Extensions** **->** **Syncfusion® ** **->** **Check** **for** **Updates…** in the Visual Studio menu.* + N> *In Visual Studio 2019, Choose **Extensions** **->** **Syncfusion®** **->** **Check** **for** **Updates…** in the Visual Studio menu.* 2. When there is an update, **Update** dialog box opens. ![Update Available](CheckForUpdates_Images/UpdateAvailable1.png) -3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. +3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. - N> *If you are using the latest version of Syncfusion® Essential Studio, you will get the **No** **Updates** **are** **available** information.* + N> *If you are using the latest version of Syncfusion® Essential Studio®, you will get the **No** **Updates** **are** **available** information.* diff --git a/Extension/UWP-Extension/Overview.md b/Extension/UWP-Extension/Overview.md index cdd917d8..93d9c32e 100644 --- a/Extension/UWP-Extension/Overview.md +++ b/Extension/UWP-Extension/Overview.md @@ -1,9 +1,9 @@ --- layout: post title: UWP Extension | Extension | Syncfusion -description: The Syncfusion UWP Project Templates provides quick access to create Syncfusion UWP Application by adding the required assemblies +description: The Syncfusion UWP Project Templates provides quick access to create Syncfusion UWP Application by adding the required assemblies platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- @@ -11,29 +11,29 @@ documentation: ug ## Overview -The Syncfusion® UWP Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® UWP Extensions supports Microsoft Visual Studio 2017. +The Syncfusion® UWP Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® UWP Extensions supports Microsoft Visual Studio 2017. -I> The Syncfusion® UWP menu option is available from v17.1.0.32. +I> The Syncfusion® UWP menu option is available from v17.1.0.32. -The Syncfusion® provides the following extension supports in Visual Studio: +The Syncfusion® provides the following extension supports in Visual Studio: -1. [Syncfusion UWP Project Template](https://help.syncfusion.com/extension/uwp-extension/project-templates): To create the Syncfusion® UWP application by adding required Syncfusion® assemblies/NuGet based on the control chosen. -2. [Troubleshooter](https://help.syncfusion.com/extension/syncfusion-troubleshooter/syncfusion-troubleshooter): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. +1. [Syncfusion® UWP Project Template](https://help.syncfusion.com/extension/uwp-extension/project-templates): To create the Syncfusion® UWP application by adding required Syncfusion® assemblies/NuGet based on the control chosen. +2. [Troubleshooter](https://help.syncfusion.com/extension/syncfusion-troubleshooter/syncfusion-troubleshooter): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. **No project selected in Visual Studio** -![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) -**Selected Syncfusion® UWP application in Visual Studio** +**Selected Syncfusion® UWP application in Visual Studio** -![Syncfusion Menu when Selected Syncfusion® UWP application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) +![Syncfusion® Menu when Selected Syncfusion® UWP application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) -N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. +N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. -The Syncfusion® UWP Visual Studio Extensions are installed along with the following setups, +The Syncfusion® UWP Visual Studio Extensions are installed along with the following setups, -* Essential Studio® for Enterprise Edition with the platform UWP -* Essential Studio® for UWP +* Essential Studio® for Enterprise Edition with the platform UWP +* Essential Studio® for UWP -N> The Syncfusion® UWP Project Templates provide Visual Studio 2015 support from v15.3.0.26 to v16.4.0.52. +N> The Syncfusion® UWP Project Templates provide Visual Studio 2015 support from v15.3.0.26 to v16.4.0.52. diff --git a/Extension/UWP-Extension/Project-Templates.md b/Extension/UWP-Extension/Project-Templates.md index 79f01f70..70642fd6 100644 --- a/Extension/UWP-Extension/Project-Templates.md +++ b/Extension/UWP-Extension/Project-Templates.md @@ -1,41 +1,41 @@ --- layout: post -title: Syncfusion UWP Project Templates | Extension | Syncfusion -description: Syncfusion provides the Visual Studio Project Templates for the Syncfusion UWP platform to create Syncfusion UWP Applications +title: Syncfusion UWP Project Templates | Extension | Syncfusion +description: Syncfusion provides the Visual Studio Project Templates for the Syncfusion UWP platform to create Syncfusion UWP Applications platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Project Templates +# Syncfusion® Project Templates -Syncfusion provides the **Visual** **Studio** **Project** **Templates** for the Syncfusion® UWP platform to create Syncfusion® UWP Applications. +Syncfusion® provides the **Visual** **Studio** **Project** **Templates** for the Syncfusion® UWP platform to create Syncfusion® UWP Applications. -I> The Syncfusion® UWP project templates are available from v15.3.0.26. +I> The Syncfusion® UWP project templates are available from v15.3.0.26. -## Create Syncfusion® UWP Application +## Create Syncfusion® UWP Application -The following steps help you to create the **Syncfusion** **UWP** **Application** through the **Visual** **Studio** **Project** **Template**. +The following steps help you to create the **Syncfusion®** **UWP** **Application** through the **Visual** **Studio** **Project** **Template**. -> Before use the Syncfusion® UWP Project Template, check whether the **UWP Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. +> Before use the Syncfusion® UWP Project Template, check whether the **UWP Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed. -1. To create a Syncfusion UWP project, follow either one of the options below: +1. To create a Syncfusion® UWP project, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for UWP > Create New Syncfusion® Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for UWP > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion® Universal Windows Application from Visual Studio new project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion® Universal Windows Application from Visual Studio new project dialog via Syncfusion menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) - N> In Visual Studio 2019, Syncfusion® menu under Extension in Visual Studio menu. + N> In Visual Studio 2019, Syncfusion® menu under Extension in Visual Studio menu. **Option 2:** - Choose **File > New > Project** and navigate to **Syncfusion > Windows Universal> Syncfusion® Universal Windows Application** in **Visual Studio**. + Choose **File > New > Project** and navigate to **Syncfusion® > Windows Universal> Syncfusion® Universal Windows Application** in **Visual Studio**. - ![Choose Syncfusion Universal Windows Application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1.jpeg) + ![Choose Syncfusion® Universal Windows Application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1.jpeg) 2. Name the **Project** and choose the destination location if required, then click **OK**. -3. Then Project Configuration Wizard appears. Choose the options to configure the Syncfusion® Universal Windows Platform application by using the following Project Configuration dialog. +3. Then Project Configuration Wizard appears. Choose the options to configure the Syncfusion® Universal Windows Platform application by using the following Project Configuration dialog. ### Project configurations: @@ -49,22 +49,22 @@ The following steps help you to create the **Syncfusion** **UWP** **Application* **Template Type:** Select the template type of UWP Project, either Blank or Hamburger Menu or Hamburger Menu (MVVM). - **Components:** Choose the required Syncfusion® components to configure. + **Components:** Choose the required Syncfusion® components to configure. - ![Syncfusion UWP Project configuration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.jpeg) + ![Syncfusion® UWP Project configuration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.jpeg) - N> If SDK is chosen as the reference type, then all the Syncfusion® UWP controls will be added. So, you no need to select any components. + N> If SDK is chosen as the reference type, then all the Syncfusion® UWP controls will be added. So, you no need to select any components. -4. Once you click Create button, the Syncfusion® UWP Application is created. +4. Once you click Create button, the Syncfusion® UWP Application is created. -5. Once the Project Configuration Wizard is done, the Syncfusion® UWP Application is created with required SDK/references and pages. +5. Once the Project Configuration Wizard is done, the Syncfusion® UWP Application is created with required SDK/references and pages. - ![Syncfusion UWP Project created with SDK reference](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) + ![Syncfusion® UWP Project created with SDK reference](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) - ![Syncfusion UWP Project created with readme](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img7.PNG) + ![Syncfusion® UWP Project created with readme](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img7.PNG) -6. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio. +6. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion UWP Project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img6.jpeg) + ![Syncfusion® license registration required information dialog in Syncfusion® UWP Project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img6.jpeg) diff --git a/Extension/UWP-Extension/Syncfusion-Notifications.md b/Extension/UWP-Extension/Syncfusion-Notifications.md index 744930e9..c3f6c72a 100644 --- a/Extension/UWP-Extension/Syncfusion-Notifications.md +++ b/Extension/UWP-Extension/Syncfusion-Notifications.md @@ -1,49 +1,49 @@ --- layout: post title: Notifications | Extension | Syncfusion -description: For displaying the notifications about trial and newer version update information for Syncfusion applications. +description: For displaying the notifications about trial and newer version update information for Syncfusion applications. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Notifications +# Syncfusion® Notifications -Syncfusion enhances the user experience in UWP applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. +Syncfusion® enhances the user experience in UWP applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. -N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. +N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. ## Notification Configuration -The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. +The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. -It can be accessed by clicking **Tools -> Options -> Syncfusion® -> UWP** +It can be accessed by clicking **Tools -> Options -> Syncfusion® -> UWP** ![Option Page](images/uwp-optionPage.png) ## Notification Types -**1. Syncfusion® Trial Application Notification** +**1. Syncfusion® Trial Application Notification** -When you utilize Syncfusion® trial assemblies in your UWP application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion. +When you utilize Syncfusion® trial assemblies in your UWP application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion®. ![Trial Notification](images/uwp-trial.png) -**2. Newer Syncfusion® NuGet Package Notification** +**2. Newer Syncfusion® NuGet Package Notification** -If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. +If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. ![NuGet Notification](images/uwp-nuget.png) -**3. Newer Essential Studio® Build Notification** +**3. Newer Essential Studio® Build Notification** -If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® Universal Windows,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your UWP development projects. +If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® Universal Windows,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your UWP development projects. ![Build Notification](images/uwp-build.png) **4. Invalid License Key Notification** -If you have mistakenly used an incorrect license key or used a license from another version or platform in your UWP application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. +If you have mistakenly used an incorrect license key or used a license from another version or platform in your UWP application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. ![Invalid Notification](images/uwp-invalid.png) diff --git a/Extension/WPF-Extension/Add-Item.md b/Extension/WPF-Extension/Add-Item.md index 4617bb25..780ec37e 100644 --- a/Extension/WPF-Extension/Add-Item.md +++ b/Extension/WPF-Extension/Add-Item.md @@ -1,58 +1,58 @@ --- layout: post title: Syncfusion Item Template for WPF | Wpf | Syncfusion -description: Syncfusion item template extension supports to add the Syncfusion WPF Window into WPF application with add Syncfusion WPF references. +description: Syncfusion item template extension supports to add the Syncfusion WPF Window into WPF application with add Syncfusion WPF references. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Add Syncfusion® Components to the WPF Application +# Add Syncfusion® Components to the WPF Application -Syncfusion supports Visual Studio Item Templates to add Syncfusion® WPF Components to a WPF application with Syncfusion® WPF references. +Syncfusion® supports Visual Studio Item Templates to add Syncfusion® WPF Components to a WPF application with Syncfusion® WPF references. -I> The Syncfusion® WPF item templates are available from v19.1.0.54. +I> The Syncfusion® WPF item templates are available from v19.1.0.54. -The following steps will guide you to add the Syncfusion® WPF Components to your Visual Studio WPF application. +The following steps will guide you to add the Syncfusion® WPF Components to your Visual Studio WPF application. -> Check whether the **WPF Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later and Visual Studio 2017 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.syncfusion.com/wpf/visual-studio-integration/download-and-installation) help topic. +> Check whether the **WPF Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later and Visual Studio 2017 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.Syncfusion.com/wpf/visual-studio-integration/download-and-installation) help topic. -## Add Components using Syncfusion® Item Template +## Add Components using Syncfusion® Item Template 1. Open a new or existing WPF application. **Option 1:** -2. From the **Solution Explorer, right-click** on the WPF application. Choose **Add Syncfusion® Item...**. +2. From the **Solution Explorer, right-click** on the WPF application. Choose **Add Syncfusion® Item...**. - ![Choose Add Syncfusion Item option from right click project](Add-Item-images/Add-syncfusion-item.png) + ![Choose Add Syncfusion® Item option from right click project](Add-Item-images/Add-Syncfusion-item.png) **Option 2:** -3. Click **Extensions > Essential Studio® for WPF > Add Syncfusion® Item…** in Visual Studio. +3. Click **Extensions > Essential Studio® for WPF > Add Syncfusion® Item…** in Visual Studio. - ![Choose Add Syncfusion Item option from menu](Add-Item-images/Add-item.png) + ![Choose Add Syncfusion® Item option from menu](Add-Item-images/Add-item.png) -4. The Syncfusion® WPF Item Template wizard will be launched as follows. +4. The Syncfusion® WPF Item Template wizard will be launched as follows. - ![Syncfusion WPF Item template Components](Add-Item-images/Add-syncfusion-ui.png) + ![Syncfusion® WPF Item template Components](Add-Item-images/Add-Syncfusion-ui.png) -5. Select the WPF Components from the Component list within your WPF Item Template. The features associated with the selected Component will be presented. From here, choose the specific features that are essential for your project. +5. Select the WPF Components from the Component list within your WPF Item Template. The features associated with the selected Component will be presented. From here, choose the specific features that are essential® for your project. -6. Choose an assembly reference option such as GAC location, Essential Studio® installed location, or NuGet packages to specify where the required Syncfusion® assemblies are added to the project. +6. Choose an assembly reference option such as GAC location, Essential Studio® installed location, or NuGet packages to specify where the required Syncfusion® assemblies are added to the project. - N> If the Syncfusion® Essential WPF build is installed, the Installed location and GAC options will be enabled. Without installing the Syncfusion® Essential WPF setup, use the NuGet option. The GAC option will not be available when using the Syncfusion® WPF Components in a .NET Core application. The Version drop-down lists the installed WPF versions. + N> If the Syncfusion® Essential® WPF build is installed, the Installed location and GAC options will be enabled. Without installing the Syncfusion® Essential® WPF setup, use the NuGet option. The GAC option will not be available when using the Syncfusion® WPF Components in a .NET Core application. The Version drop-down lists the installed WPF versions. 7. Click **Add**, and a pop-up will appear providing information about adding Component **files** and **NuGet/Assemblies** details. - ![Syncfusion WPF Item template details](Add-Item-images/Add-syncfusion-item-3.png) + ![Syncfusion® WPF Item template details](Add-Item-images/Add-Syncfusion-item-3.png) -8. Click **OK** to incorporate the chosen Components into the WPF application, along with the necessary Syncfusion® assemblies. +8. Click **OK** to incorporate the chosen Components into the WPF application, along with the necessary Syncfusion® assemblies. - ![Syncfusion WPF Item template Gallery](Add-Item-images/Add-syncfusion-item-details.png) + ![Syncfusion® WPF Item template Gallery](Add-Item-images/Add-Syncfusion-item-details.png) -9. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/ licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +9. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion WPF Item template Gallery](Add-Item-images/LicensePage.png) \ No newline at end of file + ![Syncfusion® WPF Item template Gallery](Add-Item-images/LicensePage.png) \ No newline at end of file diff --git a/Extension/WPF-Extension/Add-References.md b/Extension/WPF-Extension/Add-References.md index 11123f48..221b5a47 100644 --- a/Extension/WPF-Extension/Add-References.md +++ b/Extension/WPF-Extension/Add-References.md @@ -1,89 +1,89 @@ --- layout: post title: Add References| Wpf | Syncfusion -description: Syncfusion Reference Manger extension is add-in to add the Syncfusion references into the WinForms application +description: Syncfusion Reference Manger extension is add-in to add the Syncfusion references into the WinForms application platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Add Reference for WPF -Syncfusion® Reference Manager is the Visual Studio Add-In for WPF platform. It adds the Syncfusion® assembly reference to the project, either from the GAC location or from Essential Studio® installed location or from NuGet packages. It can also migrate the projects that contain the old versions of the Syncfusion® assembly reference to newer or specific versions of the Syncfusion® assembly reference. It supports Microsoft Visual Studio 2013 or higher. This Visual Studio extension is included from Essential Studio® 2013 Volume 3 release. +Syncfusion® Reference Manager is the Visual Studio Add-In for WPF platform. It adds the Syncfusion® assembly reference to the project, either from the GAC location or from Essential Studio® installed location or from NuGet packages. It can also migrate the projects that contain the old versions of the Syncfusion® assembly reference to newer or specific versions of the Syncfusion® assembly reference. It supports Microsoft Visual Studio 2013 or higher. This Visual Studio extension is included from Essential Studio® 2013 Volume 3 release. -N> This Reference Manager can be applied to a project for Syncfusion® assembly versions 10.4.0.71 and later. +N> This Reference Manager can be applied to a project for Syncfusion® assembly versions 10.4.0.71 and later. -To add the Syncfusion® assembly references in Visual Studio, follow the steps below: +To add the Syncfusion® assembly references in Visual Studio, follow the steps below: -> Check whether the **WPF Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by going to **Tools -> Extensions and Updates -> Installed** for Visual Studio 2017 or lower, and **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 by going to Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](download-and-installation) help topic. +> Check whether the **WPF Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by going to **Tools -> Extensions and Updates -> Installed** for Visual Studio 2017 or lower, and **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 by going to Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](download-and-installation) help topic. 1. Open a new or existing **WPF** application. -2. To open Syncfusion® Reference Manager Wizard, follow either one of the options below: +2. To open Syncfusion® Reference Manager Wizard, follow either one of the options below: **Option 1:** - Click **Syncfusion® Menu** and choose **Essential Studio® for WPF > Add References…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for WPF > Add References…** in **Visual Studio**. - ![Syncfusion Reference Manager via Syncfusion® Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png) + ![Syncfusion® Reference Manager via Syncfusion® Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Syncfusion Reference Manager via Syncfusion® Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference_2019.png) + ![Syncfusion® Reference Manager via Syncfusion® Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference_2019.png) **Option 2:** - Right-click the selected project file from Solution Explorer, then select **Syncfusion Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio. + Right-click the selected project file from Solution Explorer, then select **Syncfusion® Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio. - ![Syncfusion Reference Manager add-in](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img1.png) + ![Syncfusion® Reference Manager add-in](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img1.png) -3. The Syncfusion® Reference Manager Wizard displays a list of loaded Syncfusion® WPF controls. +3. The Syncfusion® Reference Manager Wizard displays a list of loaded Syncfusion® WPF controls. - ![Syncfusion Reference Manger Wizard](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img2.png) + ![Syncfusion® Reference Manger Wizard](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img2.png) - **Platform Selection:** Platform selection option will appear as an option in Syncfusion® Reference Manager if opened from a Console/Class Library project. Select the appropriate platform. + **Platform Selection:** Platform selection option will appear as an option in Syncfusion® Reference Manager if opened from a Console/Class Library project. Select the appropriate platform. - ![Platform selection option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img3.png) + ![Platform selection option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img3.png) - N> The platform selection option will appear only if Essential Studio® for Enterprise Edition with the platforms WPF and Windows Forms has been installed, or if both Essential Studio® for WPF and WinForms has been installed. + N> The platform selection option will appear only if Essential Studio® for Enterprise Edition with the platforms WPF and Windows Forms has been installed, or if both Essential Studio® for WPF and WinForms has been installed. **Assembly From:** Choose the assembly location, either from NuGet packages, the build installed location, or by using the GAC location. - N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® WPF setup has been installed. + N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® WPF setup has been installed. - ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img4.png) + ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img4.png) N> The GAC option will not be available when you select the WPF (.NET 8.0, .NET 7.0, and.NET 6.0) application in Visual Studio 2022. **Version:** To add the corresponding version assemblies to the project, select the build version. - ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger1-img4.png) + ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger1-img4.png) **Themes Option:** Choose the necessary themes based on your requirements. To learn more about built-in themes and their available assembly, click the link below. - [https://help.syncfusion.com/wpf/themes/](https://help.syncfusion.com/wpf/themes/) + [https://help.Syncfusion.com/wpf/themes/](https://help.Syncfusion.com/wpf/themes/) - ![Themes selection option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img5.png) + ![Themes selection option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img5.png) N> Themes option will be enabled only if we selected theme supported controls. - ![Themes selection option notification in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img6.png) + ![Themes selection option notification in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img6.png) 4. Select the required controls you want to add in your project. Then click ****Done** to add the project's required assemblies for the specified controls. The list of required assemblies for the selected controls to be added is shown in the screenshot below. - ![Syncfusion Reference Manager new assemblies add information dialog](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img7.png) + ![Syncfusion® Reference Manager new assemblies add information dialog](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img7.png) -5. Click **OK**. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion assemblies have been added successfully” in Visual Studio status bar. +5. Click **OK**. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar. - ![Syncfusion Reference Manager success status in Visual Studio status bar](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img8.png) + ![Syncfusion® Reference Manager success status in Visual Studio status bar](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img8.png) -6. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +6. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion® Reference Manager](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img9.png) + ![Syncfusion® license registration required information dialog in Syncfusion® Reference Manager](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img9.png) -N> Reference Manager support is provided by Syncfusion® for select versions of the.NET Framework that are included (as assemblies) in the Syncfusion® Essential Studio® installation. If you try to add Syncfusion® assemblies to a project and the project framework isn't compatible with the specified Syncfusion® version assemblies, a dialogue box shows with the message "**Current build v{version} isn't compatible with this framework v{Framework} Version**". +N> Reference Manager support is provided by Syncfusion® for select versions of the.NET Framework that are included (as assemblies) in the Syncfusion® Essential Studio® installation. If you try to add Syncfusion® assemblies to a project and the project framework isn't compatible with the specified Syncfusion® version assemblies, a dialogue box shows with the message "**Current build v{version} isn't compatible with this framework v{Framework} Version**". diff --git a/Extension/WPF-Extension/Check-for-Updates.md b/Extension/WPF-Extension/Check-for-Updates.md index 2f8b7564..100e8c7c 100644 --- a/Extension/WPF-Extension/Check-for-Updates.md +++ b/Extension/WPF-Extension/Check-for-Updates.md @@ -1,30 +1,30 @@ --- layout: post title: Check for Updates | Wpf | Syncfusion -description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. +description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. platform: extension control: Visual Studio Extensions documentation: ug --- -# Check for Updates in Syncfusion® Essential WPF +# Check for Updates in Syncfusion® Essential® WPF -Syncfusion provides Extensions to update the most recent version of the Essential Studio® release. Installing the most recent version ensures that you always have the most up-to-date features, fixes, and improvements. +Syncfusion® provides Extensions to update the most recent version of the Essential Studio® release. Installing the most recent version ensures that you always have the most up-to-date features, fixes, and improvements. -I> The Syncfusion® Check for updates is available from v17.1.0.32. +I> The Syncfusion® Check for updates is available from v17.1.0.32. You can check the availability of updates in Visual Studio and then install the update version if required. -1. Choose **Syncfusion -> Check for Updates…** in the Visual Studio menu. +1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu. - ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) + ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1_2019.png) + ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1_2019.png) 2. When an update is available, the Update dialog box appears. - ![Syncfusion check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) + ![Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) -3. Syncfusion Essential Studio® can be downloaded from the Syncfusion® website by clicking the **Download** button. +3. Syncfusion® Essential Studio® can be downloaded from the Syncfusion® website by clicking the **Download** button. diff --git a/Extension/WPF-Extension/Create-Project.md b/Extension/WPF-Extension/Create-Project.md index e4cc2b78..705e5bba 100644 --- a/Extension/WPF-Extension/Create-Project.md +++ b/Extension/WPF-Extension/Create-Project.md @@ -1,7 +1,7 @@ --- layout: post title: Create Project | Wpf | Syncfusion -description: Syncfusion provides the Visual Studio Project Templates for the Syncfusion WPF platform to create Syncfusion WPF Application by addiing the required assemblies +description: Syncfusion provides the Visual Studio Project Templates for the Syncfusion WPF platform to create Syncfusion WPF Application by addiing the required assemblies platform: extension control: Syncfusion Extensions documentation: ug @@ -10,45 +10,45 @@ documentation: ug # Create WPF application -The Visual Studio Project Templates for the Syncfusion® WPF platform allow you to quickly develop a Syncfusion® WPF application by just adding the appropriate Syncfusion® assemblies and XAML. +The Visual Studio Project Templates for the Syncfusion® WPF platform allow you to quickly develop a Syncfusion® WPF application by just adding the appropriate Syncfusion® assemblies and XAML. -I> The Syncfusion® WPF templates are available from v16.1.0.24. +I> The Syncfusion® WPF templates are available from v16.1.0.24. -> WPF Project Template works seamlessly with Visual Studio 2015 or lower. For the Visual Studio 2017 or later versions, it is recommended to use a [WPF Template Studio](https://help.syncfusion.com/wpf/visual-studio-integration/template-studio). +> WPF Project Template works seamlessly with Visual Studio 2015 or lower. For the Visual Studio 2017 or later versions, it is recommended to use a [WPF Template Studio](https://help.Syncfusion.com/wpf/visual-studio-integration/template-studio). -Create the Syncfusion® WPF project using the Visual Studio Project Template by following the steps below: +Create the Syncfusion® WPF project using the Visual Studio Project Template by following the steps below: -> Check whether the **WPF Extensions - Syncfusion** are installed or not in Visual Studio 2015 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://help.syncfusion.com/wpf/visual-studio-integration/download-and-installation) help topic. +> Check whether the **WPF Extensions - Syncfusion®** are installed or not in Visual Studio 2015 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://help.Syncfusion.com/wpf/visual-studio-integration/download-and-installation) help topic. -1. To create a Syncfusion® WPF project, follow either one of the options below: +1. To create a Syncfusion® WPF project, follow either one of the options below: **Option 1:** - Click **Syncfusion** Menu and choose **Essential Studio for WPF > Create New Syncfusion® Project…** in **Visual Studio**. + Click **Syncfusion®** Menu and choose **Essential Studio® for WPF > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion WPF Application from Visual Studio new project dialog via Syncfusion menu](Project-Template-images/Syncfusion-Menu.png) + ![Choose Syncfusion® WPF Application from Visual Studio new project dialog via Syncfusion® menu](Project-Template-images/Syncfusion-Menu.png) - N> In Visual Studio 2015 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. + N> In Visual Studio 2015 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. **Option 2:** - Choose **File -> New -> Project**. Opens a new dialog to create a new project. By filtering the project type with Syncfusion® or using the Syncfusion® keyword in the search option, you can get the templates offered by Syncfusion® for WPF. + Choose **File -> New -> Project**. Opens a new dialog to create a new project. By filtering the project type with Syncfusion® or using the Syncfusion® keyword in the search option, you can get the templates offered by Syncfusion® for WPF. - ![Choose Syncfusion WPF Application from Visual Studio new project dialog](Project-Template-images/Syncfusion-Project-Template-Gallery2019-1.png) + ![Choose Syncfusion® WPF Application from Visual Studio new project dialog](Project-Template-images/Syncfusion-Project-Template-Gallery2019-1.png) - In Visual Studio 2015 or lower, Select **File > New > Project** and navigate to **Syncfusion > Windows > Syncfusion® WPF Application** in Visual Studio. + In Visual Studio 2015 or lower, Select **File > New > Project** and navigate to **Syncfusion® > Windows > Syncfusion® WPF Application** in Visual Studio. - ![Choose Syncfusion WPF Application from Visual Studio new project dialog](Project-Template-images/Syncfusion-Project-Template-Gallery-1.png) + ![Choose Syncfusion® WPF Application from Visual Studio new project dialog](Project-Template-images/Syncfusion-Project-Template-Gallery-1.png) 2. Name the **Project**, select the destination location when required, and specify the Framework of the project, then click **OK**. - N> For Syncfusion® WPF project templates, the minimum target Framework is 4.0. + N> For Syncfusion® WPF project templates, the minimum target Framework is 4.0. -3. Using the following Project Configuration Wizard, choose the options to configure the Syncfusion® WPF Application. +3. Using the following Project Configuration Wizard, choose the options to configure the Syncfusion® WPF Application. - ![Syncfusion WPF project configuration wizard](Project-Template-images/Syncfusion-Project-Template-Gallery2019-2.png) + ![Syncfusion® WPF project configuration wizard](Project-Template-images/Syncfusion-Project-Template-Gallery2019-2.png) - In Visual Studio 2015 or lower, Syncfusion® WPF Application project configuration wizard. + In Visual Studio 2015 or lower, Syncfusion® WPF Application project configuration wizard. - ![Syncfusion WPF project configuration wizard](Project-Template-images/Syncfusion-Project-Template-Gallery-2.png) + ![Syncfusion® WPF project configuration wizard](Project-Template-images/Syncfusion-Project-Template-Gallery-2.png) **Project Configurations** @@ -58,13 +58,13 @@ Create the Syncfusion® WPF project using t **Choose Theme:** Select the required theme. - **Reference From:** Choose the assembly location such as NuGet, GAC Location, or Essential Studio® installed location, from where the assembly is added to the project. + **Reference From:** Choose the assembly location such as NuGet, GAC Location, or Essential Studio® installed location, from where the assembly is added to the project. - N> The installed location and GAC options will be available only after the Syncfusion® Essential WPF setup has been installed. You can use the NuGet option instead of installing the Syncfusion® Essential WPF setup. + N> The installed location and GAC options will be available only after the Syncfusion® Essential® WPF setup has been installed. You can use the NuGet option instead of installing the Syncfusion® Essential® WPF setup. **Installed ES Build Version:** To add the appropriate version assemblies to the project, choose the build version. - N> Installed ES build version option will be available only if you install the Syncfusion® Essential WPF setup and select Installed Location or GAC as the assembly location. + N> Installed ES build version option will be available only if you install the Syncfusion® Essential® WPF setup and select Installed Location or GAC as the assembly location. **Size Mode:** Select the Size Mode either Default or Touch. @@ -72,14 +72,14 @@ Create the Syncfusion® WPF project using t N> Project create option will be enabled only if you have selected the window -4. After choosing above project configuration options in the Project Configuration Wizard, click the create button then Syncfusion® WPF project is created with the necessary XAML files and required Syncfusion® WPF assemblies/NuGet packages. +4. After choosing above project configuration options in the Project Configuration Wizard, click the create button then Syncfusion® WPF project is created with the necessary XAML files and required Syncfusion® WPF assemblies/NuGet packages. - ![Syncfusion WPF project created with required Syncfusion WPF assemblies](Project-Template-images/Syncfusion-Project-Template-Gallery-7.png) + ![Syncfusion® WPF project created with required Syncfusion® WPF assemblies](Project-Template-images/Syncfusion-Project-Template-Gallery-7.png) - ![Syncfusion WPF project created with required Syncfusion XAML files](Project-Template-images/Syncfusion-Project-Template-Gallery-8.png) + ![Syncfusion® WPF project created with required Syncfusion® XAML files](Project-Template-images/Syncfusion-Project-Template-Gallery-8.png) - ![Syncfusion WPF project created with readme](Project-Template-images/Syncfusion-Project-Template-Gallery-10.png) + ![Syncfusion® WPF project created with readme](Project-Template-images/Syncfusion-Project-Template-Gallery-10.png) -5. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. +5. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion WPF project](Project-Template-images/Syncfusion-Project-Template-Gallery-9.png) \ No newline at end of file + ![Syncfusion® license registration required information dialog in Syncfusion® WPF project](Project-Template-images/Syncfusion-Project-Template-Gallery-9.png) \ No newline at end of file diff --git a/Extension/WPF-Extension/Download-and-Installation.md b/Extension/WPF-Extension/Download-and-Installation.md index 6fdc2041..23ede8b4 100644 --- a/Extension/WPF-Extension/Download-and-Installation.md +++ b/Extension/WPF-Extension/Download-and-Installation.md @@ -1,20 +1,20 @@ --- layout: post title: Download and Installation | Wpf | Syncfusion -description: How to download and install the Syncfusion WPF Visual Studio Extensions from Visual Studio Market Place +description: How to download and install the Syncfusion WPF Visual Studio Extensions from Visual Studio Market Place platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -In [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.WPFExtension), Syncfusion® publishing the WPF Visual Studio extension. You can either use the Visual Studio to install it or go to the Visual Studio marketplace to download and install it +In [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.WPFExtension), Syncfusion® publishing the WPF Visual Studio extension. You can either use the Visual Studio to install it or go to the Visual Studio marketplace to download and install it ## Install through the Visual Studio Manage Extensions -The steps below assist you to how to install the Syncfusion® WPF extensions from Visual Studio **Manage Extensions**. +The steps below assist you to how to install the Syncfusion® WPF extensions from Visual Studio **Manage Extensions**. 1. Open the Visual Studio. 2. Navigate to **Extension -> Manage Extensions** and open the Manage Extensions. @@ -22,26 +22,26 @@ The steps below assist you to how to install the Syncfusion® extensions from Visual Studio under the Extensions menu. +8. Now, you can use the Syncfusion® extensions from Visual Studio under the Extensions menu. - ![Syncfusion WPF Menu](Download-and-Installation-images/SyncfusionWpfMenu.png) + ![Syncfusion® WPF Menu](Download-and-Installation-images/SyncfusionWpfMenu.png) ## Install from the Visual Studio Marketplace -The steps below illustrate how to download and install the Syncfusion® WPF extension from the Visual Studio Marketplace. +The steps below illustrate how to download and install the Syncfusion® WPF extension from the Visual Studio Marketplace. -1. Download the [Syncfusion WPF Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.WPFExtension) from the Visual Studio Marketplace. +1. Download the [Syncfusion® WPF Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.WPFExtension) from the Visual Studio Marketplace. 2. If any Visual Studio instances are still open, close them. 3. Double-click on the downloaded VSIX file to install. You can see the VSIX installation prompts for the Visual Studio 2019 version. If Visual Studio 2019 is not installed, it will not be possible to install the extension ![Vsix Modify Window](Download-and-Installation-images/VSIXInstall.png) 4. Click the **Install** button. -5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the Extensions menu. +5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the Extensions menu. - ![Syncfusion WPF Menu](Download-and-Installation-images/SyncfusionWpfMenu.png) \ No newline at end of file + ![Syncfusion® WPF Menu](Download-and-Installation-images/SyncfusionWpfMenu.png) \ No newline at end of file diff --git a/Extension/WPF-Extension/Overview.md b/Extension/WPF-Extension/Overview.md index 509b0535..efa0de32 100644 --- a/Extension/WPF-Extension/Overview.md +++ b/Extension/WPF-Extension/Overview.md @@ -1,43 +1,43 @@ --- layout: post title: Visual Studio Extension for WPF | Syncfusion -description: The Syncfusion WPF Visual Studio Extensions provides you with quick access to Project Templates to create or configure the WPF Application. +description: The Syncfusion WPF Visual Studio Extensions provides you with quick access to Project Templates to create or configure the WPF Application. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® WPF Extension +# Syncfusion® WPF Extension -The Syncfusion® WPF Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® WPF Extensions supports Microsoft Visual Studio 2013 or higher. +The Syncfusion® WPF Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® WPF Extensions supports Microsoft Visual Studio 2013 or higher. -N> Syncfusion® Extension is published in Visual Studio Marketplace. We provided separate Syncfusion® WPF Extension support for Visual Studio 2022 and Visual Studio 2019 or lower. Please refer below marketplace link. +N> Syncfusion® Extension is published in Visual Studio Marketplace. We provided separate Syncfusion® WPF Extension support for Visual Studio 2022 and Visual Studio 2019 or lower. Please refer below marketplace link. [Visual Studio 2022](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.WPFVSExtension) [Visual Studio 2019 or lower](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.WPFExtension) -I> The Syncfusion® WPF menu option is available from `v17.1.0.32`. +I> The Syncfusion® WPF menu option is available from `v17.1.0.32`. -The Syncfusion® provides the following extension supports in Visual Studio: +The Syncfusion® provides the following extension supports in Visual Studio: -1. [Template Studio](https://help.syncfusion.com/wpf/visual-studio-integration/template-studio): Syncfusion® WPF Template Studio simplifies application development with its components by managing references and providing pre-defined code. It streamlines the process of creating WPF applications. -2. [Create Project](https://help.syncfusion.com/wpf/visual-studio-integration/create-project): Creates the Syncfusion® WPF application by adding the required Syncfusion® assemblies and XMAL. -3. [Add Item](https://help.syncfusion.com/wpf/visual-studio-integration/add-item): Add Syncfusion® WPF Controls into the WPF application with add Syncfusion® WPF assemblies/NuGet packages -4. [Add References](https://help.syncfusion.com/wpf/visual-studio-integration/add-references): Add the required Syncfusion® assembly to WPF project reference based on the selected control(s). -5. [Toolbox Configuration](https://help.syncfusion.com/wpf/visual-studio-integration/toolbox-configuration): Configure the Syncfusion® controls into the Visual Studio .NET toolbox. -6. [Troubleshooter](https://help.syncfusion.com/wpf/visual-studio-integration/troubleshooting): Troubleshoots the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. +1. [Template Studio](https://help.Syncfusion.com/wpf/visual-studio-integration/template-studio): Syncfusion® WPF Template Studio simplifies application development with its components by managing references and providing pre-defined code. It streamlines the process of creating WPF applications. +2. [Create Project](https://help.Syncfusion.com/wpf/visual-studio-integration/create-project): Creates the Syncfusion® WPF application by adding the required Syncfusion® assemblies and XMAL. +3. [Add Item](https://help.Syncfusion.com/wpf/visual-studio-integration/add-item): Add Syncfusion® WPF Controls into the WPF application with add Syncfusion® WPF assemblies/NuGet packages +4. [Add References](https://help.Syncfusion.com/wpf/visual-studio-integration/add-references): Add the required Syncfusion® assembly to WPF project reference based on the selected control(s). +5. [Toolbox Configuration](https://help.Syncfusion.com/wpf/visual-studio-integration/toolbox-configuration): Configure the Syncfusion® controls into the Visual Studio .NET toolbox. +6. [Troubleshooter](https://help.Syncfusion.com/wpf/visual-studio-integration/troubleshooting): Troubleshoots the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. **No project selected in Visual Studio** -![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Microsoft WPF application in Visual Studio** -![Syncfusion Menu when Selected Microsoft WPF application in Visual Studio](Overview-images/WPF-1.png) +![Syncfusion® Menu when Selected Microsoft WPF application in Visual Studio](Overview-images/WPF-1.png) -**Selected Syncfusion® WPF application in Visual Studio** +**Selected Syncfusion® WPF application in Visual Studio** -![Syncfusion Menu when Selected Synfusion WPF application in Visual Studio](Overview-images/WPF-1.png) +![Syncfusion® Menu when Selected Synfusion WPF application in Visual Studio](Overview-images/WPF-1.png) -N> In Visual Studio 2017 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. +N> In Visual Studio 2017 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. diff --git a/Extension/WPF-Extension/Syncfusion-Notifications.md b/Extension/WPF-Extension/Syncfusion-Notifications.md index b9a7550d..89a825db 100644 --- a/Extension/WPF-Extension/Syncfusion-Notifications.md +++ b/Extension/WPF-Extension/Syncfusion-Notifications.md @@ -1,49 +1,49 @@ --- layout: post title: Notifications | WPF | Syncfusion -description: For displaying the notifications about trial and newer version update information for Syncfusion applications. +description: For displaying the notifications about trial and newer version update information for Syncfusion applications. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Notifications +# Syncfusion® Notifications -Syncfusion enhances the user experience in WPF applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. +Syncfusion® enhances the user experience in WPF applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. -N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. +N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. ## Notification Configuration -The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. +The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. -It can be accessed by clicking **Tools -> Options -> Syncfusion® -> WPF** +It can be accessed by clicking **Tools -> Options -> Syncfusion® -> WPF** ![Option Page](images/wpf-optionPage.png) ## Notification Types -**1. Syncfusion® Trial Application Notification** +**1. Syncfusion® Trial Application Notification** -When you utilize Syncfusion® trial assemblies in your WPF application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion. +When you utilize Syncfusion® trial assemblies in your WPF application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion®. ![Trial Notification](images/wpf-trial.png) -**2. Newer Syncfusion® NuGet Package Notification** +**2. Newer Syncfusion® NuGet Package Notification** -If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. +If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. ![NuGet Notification](images/wpf-nuget.png) -**3. Newer Essential Studio® Build Notification** +**3. Newer Essential Studio® Build Notification** -If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio WPF,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your WPF development projects. +If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® WPF,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your WPF development projects. ![Build Notification](images/wpf-build.png) **4. Invalid License Key Notification** -If you have mistakenly used an incorrect license key or used a license from another version or platform in your WPF application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. +If you have mistakenly used an incorrect license key or used a license from another version or platform in your WPF application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. ![Invalid Notification](images/wpf-invalid.png) diff --git a/Extension/WPF-Extension/Template-Studio.md b/Extension/WPF-Extension/Template-Studio.md index 15c66416..79191054 100644 --- a/Extension/WPF-Extension/Template-Studio.md +++ b/Extension/WPF-Extension/Template-Studio.md @@ -1,66 +1,66 @@ --- layout: post title: Template Studio | Wpf | Syncfusion -description: Syncfusion® provides the Visual Studio Project Templates for the Syncfusion WPF platform to create Syncfusion WPF Application by addiing the required assemblies +description: Syncfusion provides the Visual Studio Project Templates for the Syncfusion WPF platform to create Syncfusion WPF Application by addiing the required assemblies platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® WPF Template Studio +# Syncfusion® WPF Template Studio -The WPF Template Studio is a tool Syncfusion® provides specifically for building applications using their WPF components. This studio streamlines the development process by including essential Syncfusion® components, managing necessary NuGet references, providing predefined namespaces, and generating component render code. It acts as a template studio wizard, making it easier for developers to create WPF applications using Syncfusion® components. +The WPF Template Studio is a tool Syncfusion® provides specifically for building applications using their WPF components. This studio streamlines the development process by including essential® Syncfusion® components, managing necessary NuGet references, providing predefined namespaces, and generating component render code. It acts as a template studio wizard, making it easier for developers to create WPF applications using Syncfusion® components. -I> The Syncfusion® WPF Template Studio is available from v23.1.36. +I> The Syncfusion® WPF Template Studio is available from v23.1.36. -N> WPF Template Studio works seamlessly with Visual Studio 2017 or later. For the Visual Studio 2015 or lower versions, it is recommended to use a [WPF project template](https://help.syncfusion.com/wpf/visual-studio-integration/create-project). +N> WPF Template Studio works seamlessly with Visual Studio 2017 or later. For the Visual Studio 2015 or lower versions, it is recommended to use a [WPF project template](https://help.Syncfusion®.com/wpf/visual-studio-integration/create-project). -Create the Syncfusion® WPF project using the Visual Studio Project Template by following the provided steps. +Create the Syncfusion® WPF project using the Visual Studio Project Template by following the provided steps. -> Check whether the **WPF Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later, and for Visual Studio 2017 by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.syncfusion.com/wpf/visual-studio-integration/download-and-installation) help topic. +> Check whether the **WPF Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later, and for Visual Studio 2017 by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.Syncfusion.com/wpf/visual-studio-integration/download-and-installation) help topic. 1. Open the Visual Studio 2022. -2. Select one of the following options to create the Syncfusion® WPF application +2. Select one of the following options to create the Syncfusion® WPF application **Option 1:** - Choose **Extension -> Syncfusion® -> Essential Studio® for WPF -> Create New Syncfusion® Project…** from the Visual Studio menu. + Choose **Extension -> Syncfusion® -> Essential Studio® for WPF -> Create New Syncfusion® Project…** from the Visual Studio menu. - ![Choose Syncfusion WPF Application from Visual Studio new project dialog via Syncfusion® menu](Template-Studio-Images/WPF-1.png) + ![Choose Syncfusion® WPF Application from Visual Studio new project dialog via Syncfusion® menu](Template-Studio-Images/WPF-1.png) - N> In Visual Studio 2017, you can see the Syncfusion® menu directly in the Visual Studio menu. + N> In Visual Studio 2017, you can see the Syncfusion® menu directly in the Visual Studio menu. **Option 2:** - Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by Syncfusion® or typing Syncfusion® as a keyword in the search option can help you find the Syncfusion® templates for WPF. + Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by Syncfusion® or typing Syncfusion® as a keyword in the search option can help you find the Syncfusion® templates for WPF. - ![Choose Syncfusion WPF Application from Visual Studio new project dialog](Template-Studio-Images/WPF-2.png) + ![Choose Syncfusion® WPF Application from Visual Studio new project dialog](Template-Studio-Images/WPF-2.png) -3. Select the Syncfusion® WPF Template Studio and click Next. +3. Select the Syncfusion® WPF Template Studio and click Next. - ![Choose Syncfusion WPF Application from Visual Studio new project dialog](Template-Studio-Images/WPF-3.png) + ![Choose Syncfusion® WPF Application from Visual Studio new project dialog](Template-Studio-Images/WPF-3.png) -4. When you launch the **Syncfusion WPF Template Studio**, you will encounter a configuration wizard that allows you to set up your Syncfusion® WPF application. Within this wizard, you will have the option to specify your preferred .NET Core Version or .NET Framework Version, select the desired language(CSharp or Visual Basic), and choose the reference type according to your requirements. +4. When you launch the **Syncfusion® WPF Template Studio**, you will encounter a configuration wizard that allows you to set up your Syncfusion® WPF application. Within this wizard, you will have the option to specify your preferred .NET Core Version or .NET Framework Version, select the desired language(CSharp or Visual Basic), and choose the reference type according to your requirements. - ![Syncfusion WPF project configuration wizard](Template-Studio-Images/WPF-4.png) + ![Syncfusion® WPF project configuration wizard](Template-Studio-Images/WPF-4.png) - N> The installed location and GAC options will be available only after the Syncfusion® Essential WPF setup has been installed. Use the NuGet option instead of installing the Syncfusion® Essential WPF setup. Also, the GAC option will not be available when you choose .NET 6.0, .NET 7.0, and .NET 8.0 from the project type option in Visual Studio. + N> The installed location and GAC options will be available only after the Syncfusion® Essential® WPF setup has been installed. Use the NuGet option instead of installing the Syncfusion® Essential® WPF setup. Also, the GAC option will not be available when you choose .NET 6.0, .NET 7.0, and .NET 8.0 from the project type option in Visual Studio. I> Visual Basic Language support is available in WPF Template Studio starting from version 25.1.35. -5. Click **Next** or navigate to the **Type** tab, then select the desired Syncfusion® WPF application type. When selecting the type of template for your application, you have two options: +5. Click **Next** or navigate to the **Type** tab, then select the desired Syncfusion® WPF application type. When selecting the type of template for your application, you have two options: - ![Syncfusion WPF project type selection wizard](Template-Studio-Images/WPF-4.png) + ![Syncfusion® WPF project type selection wizard](Template-Studio-Images/WPF-4.png) **Predefined template:** Choose this option to select from 5 predefined templates, including Calendar, Contact, Outlook, Docking Manager, Spreadsheet, Tile view, and Word. By choosing one of these templates, you can create your application without needing to follow any further steps. - ![Syncfusion WPF Predefined template wizard](Template-Studio-Images/WPFTemplate-6.png) + ![Syncfusion® WPF Predefined template wizard](Template-Studio-Images/WPFTemplate-6.png) **Project type:** Choose this option to select from 4 project types, including Navigation Pane, Blank, Menu Bar, and Ribbon . -6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion® WPF components you can add to the application. +6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion® WPF components you can add to the application. - ![Syncfusion WPF pages selection wizard](Template-Studio-Images/WPF-6.png) + ![Syncfusion® WPF pages selection wizard](Template-Studio-Images/WPF-6.png) To unselect the added control(s), Click ‘x’ for the corresponding control in the control list from the Project Details. @@ -68,25 +68,25 @@ Create the Syncfusion® WPF project using t 7. Click **Next** or navigate to the **Control Features** tab to view the listed features for the selected controls. From here, choose the features needed. - ![Syncfusion WPF control features selection wizard](Template-Studio-Images/WPF-2.gif) + ![Syncfusion® WPF control features selection wizard](Template-Studio-Images/WPF-2.gif) 8. Click **Next** or navigate the **App Features** tab to select the desired application features. - ![Syncfusion WPF app features selection wizard](Template-Studio-Images/WPF-7.png) + ![Syncfusion® WPF app features selection wizard](Template-Studio-Images/WPF-7.png) **Project Details Section** In the **Project Details** section, you can modify configurations and project types. Additionally, you can remove one or more controls from the selected list and remove the chosen application feature. -![Syncfusion WPF project details selection and unselection wizard](Template-Studio-Images/WPF-8.png) +![Syncfusion® WPF project details selection and unselection wizard](Template-Studio-Images/WPF-8.png) -9. Click **Create** to generate the Syncfusion® WPF application. Once you've created the project, the relevant Syncfusion® NuGet packages will be automatically added to your project for the chosen components. For example, if you add an **DataGrid** control, the corresponding Syncfusion® NuGet packages required for that control will be installed. +9. Click **Create** to generate the Syncfusion® WPF application. Once you've created the project, the relevant Syncfusion® NuGet packages will be automatically added to your project for the chosen components. For example, if you add an **DataGrid** control, the corresponding Syncfusion® NuGet packages required for that control will be installed. - ![Syncfusion WPF project created with readme](Template-Studio-Images/WPF-9.png) + ![Syncfusion® WPF project created with readme](Template-Studio-Images/WPF-9.png) ![NuGetEntry](Template-Studio-Images/NuGetEntry.png) - To find out which NuGet packages are needed for other WPF controls, please refer to this [documentation link](https://help.syncfusion.com/wpf/control-dependencies) for detailed information on the required NuGet packages for each control. + To find out which NuGet packages are needed for other WPF controls, please refer to this [documentation link](https://help.Syncfusion.com/wpf/control-dependencies) for detailed information on the required NuGet packages for each control. 10. When you create a WPF project, the following Dependency Injection (DI) setup is added to the **App.xaml.cs** file. This setup registers services, view models, and views with the DI container, ensuring proper functionality for the selected components and service management within your application. Below, the **ConfigureServices** method in **App.xaml.cs** sets up Dependency Injection (DI) in a WPF project to manage the application's services, view models, and views. Here's a simple breakdown: @@ -151,6 +151,6 @@ In the **Project Details** section, you can modify configurations and project ty > > -13. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio. +13. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion WPF project](Template-Studio-Images/Syncfusion-Project-Template-Gallery-9.png) \ No newline at end of file + ![Syncfusion® license registration required information dialog in Syncfusion® WPF project](Template-Studio-Images/Syncfusion-Project-Template-Gallery-9.png) \ No newline at end of file diff --git a/Extension/WPF-Extension/Toolbox-Configuration.md b/Extension/WPF-Extension/Toolbox-Configuration.md index 30f5a7e9..291c7759 100644 --- a/Extension/WPF-Extension/Toolbox-Configuration.md +++ b/Extension/WPF-Extension/Toolbox-Configuration.md @@ -1,7 +1,7 @@ --- layout: post title: Toolbox Configuration | Wpf | Syncfusion -description: This section provides information regarding all the Syncfusion Essential Studio utilities and its usage +description: This section provides information regarding all the Syncfusion Essential Studio utilities and its usage platform: extension control: Essential Studio documentation: ug @@ -9,29 +9,29 @@ documentation: ug # Toolbox Configuration -The Syncfusion® Toolbox Installer utility incorporates the Syncfusion® WPF components into the Visual Studio .NET toolbox. +The Syncfusion® Toolbox Installer utility incorporates the Syncfusion® WPF components into the Visual Studio .NET toolbox. -N> Toolbox configuration support is not available for the Visual Studio Express Edition. However, you can manually configure the Syncfusion® controls into the Visual Studio Express Toolbox. To do so, refer the [Manual Toolbox Configuration](https://help.syncfusion.com/common/faq/how-to-configure-the-toolbox-of-visual-studio-manually). +N> Toolbox configuration support is not available for the Visual Studio Express Edition. However, you can manually configure the Syncfusion® controls into the Visual Studio Express Toolbox. To do so, refer the [Manual Toolbox Configuration](https://help.Syncfusion.com/common/faq/how-to-configure-the-toolbox-of-visual-studio-manually). -If the “Configure Syncfusion® Controls in Visual Studio” checkbox is selected from the installer UI while installing the Syncfusion® WPF installer, Syncfusion® components will be automatically configured in the Visual Studio toolbox. +If the “Configure Syncfusion® Controls in Visual Studio” checkbox is selected from the installer UI while installing the Syncfusion® WPF installer, Syncfusion® components will be automatically configured in the Visual Studio toolbox. -To add the Syncfusion® WPF components via the Syncfusion® Toolbox Installer, perform the following steps: +To add the Syncfusion® WPF components via the Syncfusion® Toolbox Installer, perform the following steps: 1. To launch Toolbox configuration utility, follow either one of the options below: **Option 1:** - Open the Syncfusion® Control Panel, click **Add On and Utilities > Toolbox Installer**. + Open the Syncfusion® Control Panel, click **Add On and Utilities > Toolbox Installer**. ![Add On and Utilities](Toolbox-Configuration_images/Toolbox-Configuration_img1.png) **Option 2:** - Click **Syncfusion menu** and choose **Essential Studio for WPF > Toolbox Configuration...** in **Visual Studio** + Click **Syncfusion® menu** and choose **Essential Studio® for WPF > Toolbox Configuration...** in **Visual Studio** - ![Toolbox Installer via Syncfusion menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) + ![Toolbox Installer via Syncfusion® menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Toolbox Installer via Syncfusion menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox_2019.png) + ![Toolbox Installer via Syncfusion® menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox_2019.png) 2. Toolbox Installer will be opened. @@ -39,17 +39,17 @@ To add the Syncfusion® WPF components via The following options are available in Toolbox Configuration: - * Install VS2005 – Configures Framework 2.0 Syncfusion® controls in VS 2005 toolbox. - * Install VS2008 – Configures Framework 3.5 Syncfusion® controls in VS 2008 toolbox. - * Install VS2010 – Configures Framework 4.0 Syncfusion® controls in VS 2010 toolbox. - * Install VS2012 – Configures Framework 4.5 Syncfusion® controls in VS 2012 toolbox. - * Install VS2013 – Configures Framework 4.5.1 Syncfusion® controls in VS 2013 toolbox. - * Install VS2015 – Configures Framework 4.6 Syncfusion® controls in VS 2015 toolbox. - * Install VS2017 – Configures Framework 4.6 Syncfusion® controls in VS 2017 toolbox. - * Install VS2019 – Configures Framework 4.6 Syncfusion® controls in VS 2019 toolbox - * Install VS2022 – Configures Framework 4.6 Syncfusion® controls in VS 2022 toolbox. + * Install VS2005 – Configures Framework 2.0 Syncfusion® controls in VS 2005 toolbox. + * Install VS2008 – Configures Framework 3.5 Syncfusion® controls in VS 2008 toolbox. + * Install VS2010 – Configures Framework 4.0 Syncfusion® controls in VS 2010 toolbox. + * Install VS2012 – Configures Framework 4.5 Syncfusion® controls in VS 2012 toolbox. + * Install VS2013 – Configures Framework 4.5.1 Syncfusion® controls in VS 2013 toolbox. + * Install VS2015 – Configures Framework 4.6 Syncfusion® controls in VS 2015 toolbox. + * Install VS2017 – Configures Framework 4.6 Syncfusion® controls in VS 2017 toolbox. + * Install VS2019 – Configures Framework 4.6 Syncfusion® controls in VS 2019 toolbox + * Install VS2022 – Configures Framework 4.6 Syncfusion® controls in VS 2022 toolbox. - N> You can also configure Syncfusion® controls from a lower version Framework assembly to higher version of Visual Studio. + N> You can also configure Syncfusion® controls from a lower version Framework assembly to higher version of Visual Studio. 3. The successful configuration of Toolbox is indicated by an Information message. Click OK. @@ -62,21 +62,21 @@ To add the Syncfusion® WPF components via ## Configuring toolbox for WPF .NET 5.0 projects -From 2021 Volume 1,Syncfusion started providing toolbox support for the WPF .NET 5.0 framework in Visual Studio. After installing the Syncfusion® WPF installer, Syncfusion® controls will be automatically configured in the Visual Studio toolbox for WPF.NET 5.0 projects. +From 2021 Volume 1,Syncfusion® started providing toolbox support for the WPF .NET 5.0 framework in Visual Studio. After installing the Syncfusion® WPF installer, Syncfusion® controls will be automatically configured in the Visual Studio toolbox for WPF.NET 5.0 projects. -N> * Syncfusion® included this toolbox support for .NET 5.0 WPF platform from 2021 Volume 1 release version v19.1.0.54 only. -* If the project was created with TargetFramework.NET Core 3.1 and then changed to.NET 5.0 after installing the WPF setup, you must restart Visual Studio to see the Syncfusion® controls in the Visual Studio Toolbox. +N> * Syncfusion® included this toolbox support for .NET 5.0 WPF platform from 2021 Volume 1 release version v19.1.0.54 only. +* If the project was created with TargetFramework.NET Core 3.1 and then changed to.NET 5.0 after installing the WPF setup, you must restart Visual Studio to see the Syncfusion® controls in the Visual Studio Toolbox. * Visual Studio 2019 16.7 Preview 2 and later is required. -### Upgrading the Syncfusion® WPF toolbox .NET 5.0 controls without installing the build +### Upgrading the Syncfusion® WPF toolbox .NET 5.0 controls without installing the build -You can upgrade the Syncfusion® WPF toolbox for .NET 5.0 control with NuGet packages downloaded from [nuget.org](https://www.nuget.org/). Download ["Syncfusion.UI.WPF.NET"](https://www.nuget.org/packages/Syncfusion.UI.WPF.NET/) package from nuget.org in your machine. +You can upgrade the Syncfusion® WPF toolbox for .NET 5.0 control with NuGet packages downloaded from [nuget.org](https://www.nuget.org/). Download ["Syncfusion.UI.WPF.NET"](https://www.nuget.org/packages/Syncfusion.UI.WPF.NET/) package from nuget.org in your machine. -Use the following steps to add the Syncfusion® WPF controls through Syncfusion® NuGet packages: +Use the following steps to add the Syncfusion® WPF controls through Syncfusion® NuGet packages: **step 1:** - Extract **"Syncfusion.UI.WPF.NET"** package by using the below commands. + Extract **"Syncfusion®.UI.WPF.NET"** package by using the below commands. Open Command prompt from nuget.exe path and run the following commands @@ -88,7 +88,7 @@ Use the following steps to add the Syncfusion®® - + {% endhighlight %} @@ -109,19 +109,19 @@ Use the following steps to add the Syncfusion®® NuGet package path in **value** attribute. + Update extracted Syncfusion® NuGet package path in **value** attribute. **Example:** ![Toolbox Installer](Toolbox-Configuration_images/NET_50_Toolbox_Package_update.png) **step 4:** - Now restart the Visual Studio 2019 to get populate the latest Syncfusion® controls in Toolbox. + Now restart the Visual Studio 2019 to get populate the latest Syncfusion® controls in Toolbox. ## Configuring toolbox for .NET Core 3.1 projects -The Syncfusion® NuGet packages must be installed in the WPF .NET Core application before the Syncfusion® toolbox can be configured. The corresponding NuGet packages Syncfusion® components will be configured in Visual Studio toolbox after installing the Syncfusion® NuGet packages in.NET Core application. +The Syncfusion® NuGet packages must be installed in the WPF .NET Core application before the Syncfusion® toolbox can be configured. The corresponding NuGet packages Syncfusion® components will be configured in Visual Studio toolbox after installing the Syncfusion® NuGet packages in.NET Core application. -Please refer the documentation [link](../../wpf/installation/install-nuget-packages), to learn more about how to use the Syncfusion® components using the Syncfusion® NuGet packages in .NET Core application. +Please refer the documentation [link](../../wpf/installation/install-nuget-packages), to learn more about how to use the Syncfusion® components using the Syncfusion® NuGet packages in .NET Core application. diff --git a/Extension/WPF-Extension/Troubleshooting.md b/Extension/WPF-Extension/Troubleshooting.md index ee9fec21..189b0d07 100644 --- a/Extension/WPF-Extension/Troubleshooting.md +++ b/Extension/WPF-Extension/Troubleshooting.md @@ -1,53 +1,53 @@ --- layout: post title: Troubleshooting | Wpf | Syncfusion -description: Syncfusion Troubleshooter is Visual Studio extension to troubleshoot the configuration issues in Syncfusion assembly reference, webconfig entries in projects. +description: Syncfusion Troubleshooter is Visual Studio extension to troubleshoot the configuration issues in Syncfusion assembly reference, webconfig entries in projects. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Troubleshoot the project -Troubleshoot the project with the Syncfusion® configuration and apply the fix, such as wrong.NET Framework version of a Syncfusion® assembly to the project or missing any Syncfusion® dependent assembly of a referred assembly. The Syncfusion® Troubleshooter can perform the following tasks: +Troubleshoot the project with the Syncfusion® configuration and apply the fix, such as wrong.NET Framework version of a Syncfusion® assembly to the project or missing any Syncfusion® dependent assembly of a referred assembly. The Syncfusion® Troubleshooter can perform the following tasks: * Report the Configuration issues. * Apply the solution ## Report the Configuration issues -The steps below will assist you in using the Syncfusion® Troubleshooter by Visual Studio. +The steps below will assist you in using the Syncfusion® Troubleshooter by Visual Studio. -> Check whether the **WPF Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by going to **Tools -> Extensions and Updates -> Installed** for Visual Studio 2017 or lower, and **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 by going to Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](download-and-installation) help topic. +> Check whether the **WPF Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by going to **Tools -> Extensions and Updates -> Installed** for Visual Studio 2017 or lower, and **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 by going to Extensions -> Manage Extensions -> Installed. If this extension not installed, please install the extension by follow the steps from the [download and installation](download-and-installation) help topic. -1. To open Syncfusion® Troubleshooter Wizard, follow either one of the options below: +1. To open Syncfusion® Troubleshooter Wizard, follow either one of the options below: **Option 1** - Open an existing Syncfusion® WPF Application, Click **Syncfusion Menu** and choose **Essential Studio for WPF > Troubleshoot…** in Visual Studio. + Open an existing Syncfusion® WPF Application, Click **Syncfusion® Menu** and choose **Essential Studio® for WPF > Troubleshoot…** in Visual Studio. - ![Syncfusion Troubleshooter via Syncfusion menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) + ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Syncfusion Troubleshooter via Syncfusion menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter_2019.png) + ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter_2019.png) **Option 2** - **Right-click the Project file in Solution Explorer**, then select the command **Syncfusion Troubleshooter…** + **Right-click the Project file in Solution Explorer**, then select the command **Syncfusion® Troubleshooter…** - ![Syncfusion Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1_2019.png) + ![Syncfusion® Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1_2019.png) -2. Analyze the project now, and if any Syncfusion® controls project configuration errors are discovered, they will be reported in the Troubleshooter dialog. If there are no configuration issues with the project, the dialog box will indicate that no modifications are required in the following areas: +2. Analyze the project now, and if any Syncfusion® controls project configuration errors are discovered, they will be reported in the Troubleshooter dialog. If there are no configuration issues with the project, the dialog box will indicate that no modifications are required in the following areas: -* Syncfusion® assembly references. -* Syncfusion® NuGet Packages. -* Syncfusion® Toolbox Configuration. +* Syncfusion® assembly references. +* Syncfusion® NuGet Packages. +* Syncfusion® Toolbox Configuration. ![No configuration changes required dialog box](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img2.png) -I> The Syncfusion® Troubleshooter options will be visible only for Syncfusion® projects which means the project should contain Syncfusion® assemblies or Syncfusion® NuGet packages referred. +I> The Syncfusion® Troubleshooter options will be visible only for Syncfusion® projects which means the project should contain Syncfusion® assemblies or Syncfusion® NuGet packages referred. -The Syncfusion® Troubleshooter handles the following project configuration issues: +The Syncfusion® Troubleshooter handles the following project configuration issues: 1. Assembly Reference Issues. @@ -57,25 +57,25 @@ The Syncfusion® Troubleshooter handles the ### Assembly Reference Issues -The Syncfusion® Troubleshooter handles the assembly reference issues listed below in Syncfusion® Projects. +The Syncfusion® Troubleshooter handles the assembly reference issues listed below in Syncfusion® Projects. 1. Dependent assemblies are missing for referred assemblies from project. - **For Instance:** : If “Syncfusion.Chart.WPF” assembly referred in project and “Syncfusion.Shared.WPF” (dependent of Syncfusion.Chart.Base) not referred in project, the Syncfusion® Troubleshooter will show dependent assembly missing. + **For Instance:** : If “Syncfusion.Chart.WPF” assembly referred in project and “Syncfusion.Shared.WPF” (dependent of Syncfusion.Chart.Base) not referred in project, the Syncfusion® Troubleshooter will show dependent assembly missing. ![Dependent assemblies missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img3.png) -2. Syncfusion® Troubleshooter compare all Syncfusion® assembly’s versions in the same project. If found any Syncfusion® assembly version inconsistency, the Syncfusion® Troubleshooter will show Syncfusion® assemblies version mismatched. +2. Syncfusion® Troubleshooter compare all Syncfusion® assembly’s versions in the same project. If found any Syncfusion® assembly version inconsistency, the Syncfusion® Troubleshooter will show Syncfusion® assemblies version mismatched. - **For Instance:** If “Syncfusion.Tools.WPF” assembly (v17.1450.0.32) referred in project, but other Syncfusion® assemblies referred assembly version is v17.1450.0.38. The Syncfusion® Troubleshooter will show Syncfusion® assembly version mismatched. + **For Instance:** If “Syncfusion®.Tools.WPF” assembly (v17.1450.0.32) referred in project, but other Syncfusion® assemblies referred assembly version is v17.1450.0.38. The Syncfusion® Troubleshooter will show Syncfusion® assembly version mismatched. ![Assembly version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img4.png) -3. Framework version mismatching (Syncfusion Assemblies) with project’s .NET Framework version. Find the supported .NET Framework details for Syncfusion® assemblies in the following link, +3. Framework version mismatching (Syncfusion® Assemblies) with project’s .NET Framework version. Find the supported .NET Framework details for Syncfusion® assemblies in the following link, - + - **For Instance:** The.NET Framework of the application is v4.5 and “Syncfusion.Tools.WPF” assembly (v17.1460.0.38 & .NET Framework version 4.6) referred in same application. The Syncfusion® Troubleshooter will show Syncfusion® assembly .NET Framework version is incompatible with project’s .NET Framework version. + **For Instance:** The.NET Framework of the application is v4.5 and “Syncfusion.Tools.WPF” assembly (v17.1460.0.38 & .NET Framework version 4.6) referred in same application. The Syncfusion® Troubleshooter will show Syncfusion® assembly .NET Framework version is incompatible with project’s .NET Framework version. ![Target Framework version of application](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img5.jpg) @@ -83,23 +83,23 @@ The Syncfusion® Troubleshooter handles the ### NuGet Issues -The Syncfusion® Troubleshooter addressed following NuGet package related issues in Syncfusion® projects. +The Syncfusion® Troubleshooter addressed following NuGet package related issues in Syncfusion® projects. -1. If the application has Syncfusion® NuGet packages in multiple versions, then Syncfusion® Troubleshooter will show Syncfusion® NuGet package version is mismatched. +1. If the application has Syncfusion® NuGet packages in multiple versions, then Syncfusion® Troubleshooter will show Syncfusion® NuGet package version is mismatched. - **For Instance:** Syncfusion® WPF platform packages installed multiple version (v16.4.0.54 & v17.1.0.38), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched. + **For Instance:** Syncfusion® WPF platform packages installed multiple version (v16.4.0.54 & v17.1.0.38), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched. - ![Syncfusion NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) + ![Syncfusion® NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) -2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version. +2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version. - **For Instance:** If “Syncfusion.SfBulletGraph.WPF40” NuGet package version(v15.4.0.17 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, the Syncfusion® Troubleshooter will show Syncfusion® package Framework version is mismatched. + **For Instance:** If “Syncfusion.SfBulletGraph.WPF40” NuGet package version(v15.4.0.17 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, the Syncfusion® Troubleshooter will show Syncfusion® package Framework version is mismatched. - ![Syncfusion NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.png) + ![Syncfusion® NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.png) -3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. +3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. - **For Instance:** If install Syncfusion.Chart.WPF NuGet package alone in project, Syncfusion® Troubleshooter will show the Syncfusion.Chart.Base and other dependent NuGet package missing. + **For Instance:** If install Syncfusion.Chart.WPF NuGet package alone in project, Syncfusion® Troubleshooter will show the Syncfusion.Chart.Base and other dependent NuGet package missing. ![Dependent NuGet package missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.png) @@ -107,34 +107,34 @@ I> Internet connection is required to restore the missing dependent packages. If ### Toolbox Configuration Issues -In Syncfusion® projects, the Syncfusion® Troubleshooter addresses the following Toolbox Configuration issues. +In Syncfusion® projects, the Syncfusion® Troubleshooter addresses the following Toolbox Configuration issues. -1. If the project .NET Framework version’s Syncfusion® Toolbox is not installed/configured, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox .NET Framework version is mismatched. +1. If the project .NET Framework version’s Syncfusion® Toolbox is not installed/configured, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox .NET Framework version is mismatched. - **For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched. + **For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched. - ![Syncfusion Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) + ![Syncfusion® Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) -2. If the configured version of Syncfusion® Toolbox differs from the latest Syncfusion® assembly reference version or NuGet package version in the same project, the Syncfusion® Troubleshooter will indicate that the Syncfusion® Toolbox version is mismatched. +2. If the configured version of Syncfusion® Toolbox differs from the latest Syncfusion® assembly reference version or NuGet package version in the same project, the Syncfusion® Troubleshooter will indicate that the Syncfusion® Toolbox version is mismatched. - **For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched. + **For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched. - ![Syncfusion Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) + ![Syncfusion® Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) ## Apply the solution -1. After loading the Syncfusion® Troubleshooter dialog, check the corresponding check box of the issue to be resolved. Then click the “Fix Issue(s)” button. +1. After loading the Syncfusion® Troubleshooter dialog, check the corresponding check box of the issue to be resolved. Then click the “Fix Issue(s)” button. - ![Syncfusion Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.png) + ![Syncfusion® Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.png) 2. A dialog appears, which will ask to take a backup of the project before performing the troubleshooting process. If you need to backup the project before troubleshooting, click “Yes” button. - ![Syncfusion Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpeg) + ![Syncfusion® Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpeg) -3. Wait for a while, the Syncfusion® Troubleshooter is resolving the selected issues. After the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully”. +3. Wait for a while, the Syncfusion® Troubleshooter is resolving the selected issues. After the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully”. - ![Syncfusion Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpeg) + ![Syncfusion® Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpeg) -4. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio. +4. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.jpeg) \ No newline at end of file + ![Syncfusion® license registration required information dialog in Syncfusion® Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.jpeg) \ No newline at end of file diff --git a/Extension/WindowsForms-Extension/Add-References.md b/Extension/WindowsForms-Extension/Add-References.md index 88269872..b07fc0c8 100644 --- a/Extension/WindowsForms-Extension/Add-References.md +++ b/Extension/WindowsForms-Extension/Add-References.md @@ -1,74 +1,74 @@ --- layout: post -title: Add a Syncfusion References| WinForms | Syncfusion -description: Syncfusion Reference Manger extension is add-in to add the Syncfusion references into the WinForms application +title: Add a Syncfusion References| WinForms | Syncfusion +description: Syncfusion Reference Manger extension is add-in to add the Syncfusion references into the WinForms application platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Add Reference for WinForms -Syncfusion Reference Manager is the Visual Studio Add-In for WinForms platform. It adds the Syncfusion® assembly reference to the project, either from the GAC location or Essential Studio® WinForms installed location. It can also migrate the projects that contain the old versions of the Syncfusion® assembly reference to newer or specific versions of the Syncfusion® assembly reference. It supports Microsoft Visual Studio 2013 or higher. This Visual Studio extension is included from Essential Studio® 2013 Volume 3 release. +Syncfusion® Reference Manager is the Visual Studio Add-In for WinForms platform. It adds the Syncfusion® assembly reference to the project, either from the GAC location or Essential Studio® WinForms installed location. It can also migrate the projects that contain the old versions of the Syncfusion® assembly reference to newer or specific versions of the Syncfusion® assembly reference. It supports Microsoft Visual Studio 2013 or higher. This Visual Studio extension is included from Essential Studio® 2013 Volume 3 release. -N> This Reference Manager can be applied to a project for Syncfusion® assembly versions 10.4.0.71 and later. +N> This Reference Manager can be applied to a project for Syncfusion® assembly versions 10.4.0.71 and later. -Follow the given steps to add the Syncfusion® references in Visual Studio: +Follow the given steps to add the Syncfusion® references in Visual Studio: -> Before use the Syncfusion® WinForms Reference Manager, check whether the **WinForms Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed.If this extension not installed, please install the extension by follow the steps from the [download and installation](https://help.syncfusion.com/windowsforms/visual-studio-integration/vs2019-extensions/download-and-installation/) help topic. +> Before use the Syncfusion® WinForms Reference Manager, check whether the **WinForms Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed.If this extension not installed, please install the extension by follow the steps from the [download and installation](https://help.Syncfusion.com/windowsforms/visual-studio-integration/vs2019-extensions/download-and-installation/) help topic. 1. Open a new or existing **WinForms** application. -2. To open Syncfusion® Reference Manager Wizard, follow either one of the options below: +2. To open Syncfusion® Reference Manager Wizard, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for WinForms > Add References…** or any other Form in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms > Add References…** or any other Form in **Visual Studio**. - ![Syncfusion Reference Manager via Syncfusion Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png) + ![Syncfusion® Reference Manager via Syncfusion® Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2:** - Right-click the selected project file from Solution Explorer, then select **Syncfusion Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio. + Right-click the selected project file from Solution Explorer, then select **Syncfusion® Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio. - ![Syncfusion Reference Manager add-in](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img1.png) + ![Syncfusion® Reference Manager add-in](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img1.png) -3. The Syncfusion® Reference Manager Wizard that contains the list of Syncfusion® WinForms controls that are loaded. +3. The Syncfusion® Reference Manager Wizard that contains the list of Syncfusion® WinForms controls that are loaded. - ![Syncfusion Reference Manger Wizard](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img2.png) + ![Syncfusion® Reference Manger Wizard](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img2.png) - **Platform Selection:** If launched the Syncfusion® Reference Manager from Console/Class Library project, Platform selection option will be appeared as option in Syncfusion® Reference Manager. Choose the required platform. + **Platform Selection:** If launched the Syncfusion® Reference Manager from Console/Class Library project, Platform selection option will be appeared as option in Syncfusion® Reference Manager. Choose the required platform. - ![Platform selection option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img3.png) + ![Platform selection option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img3.png) **Assembly From:** Choose the assembly location, either from NuGet packages, the build installed location, or by using the GAC location. - N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® Winforms setup has been installed. + N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® Winforms setup has been installed. - ![Assembly location option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img4.png) + ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img4.png) N> The GAC option will not be available if you have selected a WinForms (.NET 8.0, .NET 7.0, and .NET 6.0) application in Visual Studio 2022. **Version:** Choose the build version to add the corresponding version assemblies to the project. - ![Assembly location option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger1-img4.png) + ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger1-img4.png) 4. Choose the required controls that you want to include in the project. Then, click Done to add the required assemblies for the selected controls into the project. The following screenshot shows the list of required assemblies for the selected controls to be added. - ![Syncfusion Reference Manager new assemblies add information dialog](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img5.png) + ![Syncfusion® Reference Manager new assemblies add information dialog](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img5.png) -5. Click **OK**. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion assemblies have been added successfully” in Visual Studio status bar. +5. Click **OK**. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar. - ![Syncfusion Reference Manager success status in Visual Studio status bar](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img6.png) + ![Syncfusion® Reference Manager success status in Visual Studio status bar](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img6.png) -6. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +6. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusio.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion Reference Manager](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img7.png) + ![Syncfusion® license registration required information dialog in Syncfusion® Reference Manager](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img7.png) -N> Syncfusion® provides Reference Manager support for specific .NET Framework, which is shipped (assemblies) in Syncfusion® Essential Studio® setup. So, if you try to add Syncfusion® assemblies in the project and project framework is not supported with selected Syncfusion® version assemblies, the dialog appears along with **“Current build v{version} is not supported this framework v{Framework Version}”** message. +N> Syncfusion® provides Reference Manager support for specific .NET Framework, which is shipped (assemblies) in Syncfusion® Essential Studio® setup. So, if you try to add Syncfusion® assemblies in the project and project framework is not supported with selected Syncfusion® version assemblies, the dialog appears along with **“Current build v{version} is not supported this framework v{Framework Version}”** message. diff --git a/Extension/WindowsForms-Extension/Check-for-Updates.md b/Extension/WindowsForms-Extension/Check-for-Updates.md index c40fc283..60f98b60 100644 --- a/Extension/WindowsForms-Extension/Check-for-Updates.md +++ b/Extension/WindowsForms-Extension/Check-for-Updates.md @@ -1,28 +1,28 @@ --- layout: post title: Check for Updates | WinForms | Syncfusion -description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. +description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. platform: extension control: Visual Studio Extensions documentation: ug --- -# Check for Updates in Syncfusion® Essential® WindowsForms +# Check for Updates in Syncfusion® Essential WindowsForms -Syncfusion provides the check for update extensions to find latest version of essential release was available, if it was available then provide option update most recent version of the Essential Studio® release. So that, you always get the latest features, fixes, and improvements by installing the latest version. +Syncfusion® provides the check for update extensions to find latest version of essential release was available, if it was available then provide option update most recent version of the Essential Studio® release. So that, you always get the latest features, fixes, and improvements by installing the latest version. -I> The Syncfusion® Check for updates is available from v17.1.0.32. +I> The Syncfusion® Check for updates is available from v17.1.0.32. You can check updates availability in Visual Studio, and then install the update version if required. -1. Choose **Syncfusion -> Check for Updates…** in the Visual Studio menu +1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu - ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) + ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. 2. When there is an update, **Update** dialog box opens. - ![Syncfusion check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) + ![Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) -3. You can download the latest Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. +3. You can download the latest Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. diff --git a/Extension/WindowsForms-Extension/Overview.md b/Extension/WindowsForms-Extension/Overview.md index f594cada..548c23e3 100644 --- a/Extension/WindowsForms-Extension/Overview.md +++ b/Extension/WindowsForms-Extension/Overview.md @@ -1,49 +1,49 @@ --- layout: post title: WindowsForms Extension | Extension | Syncfusion -description: The Syncfusion Windows Extensions provides you with quick access to Project Templates to create or configure the Syncfusion Windows Forms Application +description: The Syncfusion Windows Extensions provides you with quick access to Project Templates to create or configure the Syncfusion Windows Forms Application platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Windows Forms Extension -The Syncfusion® WinForms Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® WinForms Extensions supports Microsoft Visual Studio 2010 or higher. +The Syncfusion® WinForms Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio.The Syncfusion® WinForms Extensions supports Microsoft Visual Studio 2010 or higher. -N> Syncfusion® Extension is published in the Visual Studio Marketplace. Refer to the following link. +N> Syncfusion® Extension is published in the Visual Studio Marketplace. Refer to the following link. [https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions) -I> The Syncfusion® WinForms menu option is available from v17.1.0.32. +I> The Syncfusion® WinForms menu option is available from v17.1.0.32. -The Syncfusion® provides the following extension supports in Visual Studio: +The Syncfusion® provides the following extension supports in Visual Studio: -1. [Syncfusion Windows Forms Project Template](https://help.syncfusion.com/extension/windowsforms-extension/syncfusion-project-templates-for-windows-forms): To create the Syncfusion® Windows Forms application by adding the required Syncfusion® assemblies and forms. -2. [Item Template](https://help.syncfusion.com/extension/windowsforms-extension/syncfusion-item-templates-for-windows-forms): Add predefined Syncfusion® items (Forms) and the required Syncfusion® assemblies in WinForms Application. -3. [Reference Manager](./add-references): To add the required Syncfusion® assembly to Windows project reference based on the selected control. -4. [Toolbox Configuration](toolbox-configuration): To configure the Syncfusion® controls into the Visual Studio .NET toolbox. -5. [Troubleshooter](troubleshooting): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. +1. [Syncfusion® Windows Forms Project Template](https://help.Syncfusion.com/extension/windowsforms-extension/Syncfusion-project-templates-for-windows-forms): To create the Syncfusion® Windows Forms application by adding the required Syncfusion® assemblies and forms. +2. [Item Template](https://help.Syncfusion.com/extension/windowsforms-extension/Syncfusion-item-templates-for-windows-forms): Add predefined Syncfusion® items (Forms) and the required Syncfusion® assemblies in WinForms Application. +3. [Reference Manager](./add-references): To add the required Syncfusion® assembly to Windows project reference based on the selected control. +4. [Toolbox Configuration](toolbox-configuration): To configure the Syncfusion® controls into the Visual Studio .NET toolbox. +5. [Troubleshooter](troubleshooting): Troubleshoot the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly. **No project selected in Visual Studio** -![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Microsoft Windows Forms application in Visual Studio** -![Syncfusion Menu when Selected Microsoft Windows Forms application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) +![Syncfusion® Menu when Selected Microsoft Windows Forms application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) -**Selected Syncfusion® Windows Forms application in Visual Studio** +**Selected Syncfusion® Windows Forms application in Visual Studio** -![Syncfusion Menu when Selected Synfusion Windows Forms application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) +![Syncfusion® Menu when Selected Synfusion Windows Forms application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) -N> From Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. +N> From Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. -The Syncfusion® Windows Forms Visual Studio Extensions are installed along with the following setups, +The Syncfusion® Windows Forms Visual Studio Extensions are installed along with the following setups, -* Essential Studio® for Enterprise Edition with the platform Windows Forms -* Essential Studio® for Windows Forms +* Essential Studio® for Enterprise Edition with the platform Windows Forms +* Essential Studio® for Windows Forms diff --git a/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md b/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md index 41c02e4c..65dc77fc 100644 --- a/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md +++ b/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md @@ -1,57 +1,57 @@ --- layout: post -title: Syncfusion Item Template | WinForms | Syncfusion -description: Syncfusion Item Templates provides to add the predefined forms with Syncfusion component in Windows Forms application. +title: Syncfusion Item Template | WinForms | Syncfusion +description: Syncfusion Item Templates provides to add the predefined forms with Syncfusion component in Windows Forms application. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Add Syncfusion® Components to the WinForms Application +# Add Syncfusion® Components to the WinForms Application -Syncfusion supports Visual Studio Item Templates to add Syncfusion® WinForms Components to a WinForms application with Syncfusion® WinForms references. +Syncfusion® supports Visual Studio Item Templates to add Syncfusion® WinForms Components to a WinForms application with Syncfusion® WinForms references. -I> The Syncfusion® Windows Forms item templates are available from v13.1.0.21. +I> The Syncfusion® Windows Forms item templates are available from v13.1.0.21. -The following steps will guide you in adding the Syncfusion® WinForms components to your Visual Studio WinForms application. +The following steps will guide you in adding the Syncfusion® WinForms components to your Visual Studio WinForms application. -> Check whether the **WinForms Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later and Visual Studio 2017 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic. +> Check whether the **WinForms Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later and Visual Studio 2017 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.Syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic. -## Add Components using Syncfusion® Item Template +## Add Components using Syncfusion® Item Template 1. Open a new or existing WinForms application. **Option 1:** -2. From the **Solution Explorer, right-click** on the WinForms application. Choose **Add Syncfusion® Item...**. +2. From the **Solution Explorer, right-click** on the WinForms application. Choose **Add Syncfusion® Item...**. - ![Choose Add Syncfusion Item option from right click project](Item-Template-images/Add-syncfusion-item.png) + ![Choose Add Syncfusion® Item option from right click project](Item-Template-images/Add-Syncfusion-item.png) **Option 2:** -3. Click **Extensions > Essential Studio® for WinForms > Add Syncfusion® Item…** in Visual Studio. +3. Click **Extensions > Essential Studio® for WinForms > Add Syncfusion® Item…** in Visual Studio. - ![Choose Add Syncfusion Item option from menu](Item-Template-images/Add-item.png) + ![Choose Add Syncfusion® Item option from menu](Item-Template-images/Add-item.png) -4. The Syncfusion® WinForms Item Template wizard will be launched as follows. +4. The Syncfusion® WinForms Item Template wizard will be launched as follows. - ![Syncfusion WinForms Item template Components](Item-Template-images/Add-syncfusion-ui.png) + ![Syncfusion® WinForms Item template Components](Item-Template-images/Add-Syncfusion-ui.png) 5. Select the WinForms Components from the Component list within your WinForms Item Template. The features associated with the selected Component will be presented. From here, choose the specific features that are essential for your project. -6. Choose an assembly reference option such as GAC location, Essential Studio® installed location, or NuGet packages to specify where the required Syncfusion® assemblies are added to the project. +6. Choose an assembly reference option such as GAC location, Essential Studio® installed location, or NuGet packages to specify where the required Syncfusion® assemblies are added to the project. - N> If the Syncfusion® Essential WindowsForm build is installed, the Installed location and GAC options will be enabled. Without installing the Syncfusion® Essential WindowsForm setup, use the NuGet option. The GAC option will not be available when using the Syncfusion® WinForms Components in a .NET Core application. The Version drop-down lists the installed WinForms versions. + N> If the Syncfusion® Essential WindowsForm build is installed, the Installed location and GAC options will be enabled. Without installing the Syncfusion® Essential WindowsForm setup, use the NuGet option. The GAC option will not be available when using the Syncfusion® WinForms Components in a .NET Core application. The Version drop-down lists the installed WinForms versions. 7. Click **Add**, and a pop-up will appear providing information about adding Component **files** and **NuGet/Assemblies** details. - ![Syncfusion WinForms Item template details](Item-Template-images/Add-syncfusion-item-3.png) + ![Syncfusion® WinForms Item template details](Item-Template-images/Add-Syncfusion-item-3.png) -8. Click **OK** to incorporate the chosen Components into the WinForms application, along with the necessary Syncfusion® assemblies. +8. Click **OK** to incorporate the chosen Components into the WinForms application, along with the necessary Syncfusion® assemblies. - ![Syncfusion WinForms Item template Gallery](Item-Template-images/Add-syncfusion-item-details.png) + ![Syncfusion® WinForms Item template Gallery](Item-Template-images/Add-Syncfusion-item-details.png) -9. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/ licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +9. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion WinForms Item template Gallery](Item-Template-images/Syncfusion-Item-Template-Gallery-7.png) \ No newline at end of file + ![Syncfusion® WinForms Item template Gallery](Item-Template-images/Syncfusion-Item-Template-Gallery-7.png) \ No newline at end of file diff --git a/Extension/WindowsForms-Extension/Syncfusion-Notifications.md b/Extension/WindowsForms-Extension/Syncfusion-Notifications.md index 88d300de..af094ac5 100644 --- a/Extension/WindowsForms-Extension/Syncfusion-Notifications.md +++ b/Extension/WindowsForms-Extension/Syncfusion-Notifications.md @@ -1,49 +1,49 @@ --- layout: post title: Notifications | WinForms | Syncfusion -description: For displaying the notifications about trial and newer version update information for Syncfusion applications. +description: For displaying the notifications about trial and newer version update information for Syncfusion applications. platform: extension control: Visual Studio Extensions documentation: ug --- -# Syncfusion® Notifications +# Syncfusion® Notifications -Syncfusion enhances the user experience in Windows Forms applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. +Syncfusion® enhances the user experience in Windows Forms applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. -N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. +N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. ## Notification Configuration -The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. +The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. -It can be accessed by clicking **Tools -> Options -> Syncfusion® -> Winforms** +It can be accessed by clicking **Tools -> Options -> Syncfusion® -> Winforms** ![Option Page](images/winforms-optionPage.png) ## Notification Types -**1. Syncfusion® Trial Application Notification** +**1. Syncfusion® Trial Application Notification** -When you utilize Syncfusion® trial assemblies in your Windows Forms application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion. +When you utilize Syncfusion® trial assemblies in your Windows Forms application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion®. ![Trial Notification](images/winforms-trial.png) -**2. Newer Syncfusion® NuGet Package Notification** +**2. Newer Syncfusion® NuGet Package Notification** -If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. +If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. ![NuGet Notification](images/winforms-nuget.png) -**3. Newer Essential Studio® Build Notification** +**3. Newer Essential Studio® Build Notification** -If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® Windows,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your Windows Forms development projects. +If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® Windows,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your Windows Forms development projects. ![Build Notification](images/winforms-build.png) **4. Invalid License Key Notification** -If you have mistakenly used an incorrect license key or used a license from another version or platform in your Windows Forms application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. +If you have mistakenly used an incorrect license key or used a license from another version or platform in your Windows Forms application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. ![Invalid Notification](images/winforms-invalid.png) diff --git a/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md b/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md index 7513ca6c..3fd82125 100644 --- a/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md +++ b/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md @@ -1,53 +1,53 @@ --- layout: post title: Project Templates for Windows Forms | WinForms | Syncfusion -description: Syncfusion Project Templates Extension creates the Syncfusion Windows Forms Application by adding the required assemblies. +description: Syncfusion Project Templates Extension creates the Syncfusion Windows Forms Application by adding the required assemblies. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Create WinForms application -Syncfusion provides the Visual Studio Project Template for the Syncfusion® WinForms platform to create the Syncfusion® WinForms Application by adding the required Syncfusion® assemblies and forms. +Syncfusion® provides the Visual Studio Project Template for the Syncfusion® WinForms platform to create the Syncfusion® WinForms Application by adding the required Syncfusion® assemblies and forms. -I> The Syncfusion® Windows Forms templates are available from v14.3.0.49. +I> The Syncfusion® Windows Forms templates are available from v14.3.0.49. ->WinForms Project Template works seamlessly with Visual Studio 2015 or lower. For the Visual Studio 2017 or later versions, it is recommended to use a [WinForms Template Studio](https://help.syncfusion.com/windowsforms/visual-studio-integration/template-studio). +>WinForms Project Template works seamlessly with Visual Studio 2015 or lower. For the Visual Studio 2017 or later versions, it is recommended to use a [WinForms Template Studio](https://help.Syncfusion.com/windowsforms/visual-studio-integration/template-studio). -Use the following steps to create the Syncfusion® Windows Forms project through the Visual Studio Project Template. +Use the following steps to create the Syncfusion® Windows Forms project through the Visual Studio Project Template. -> Check whether the **WinForms Extensions - Syncfusion** are installed or not in Visual Studio 2015 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://help.syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic. +> Check whether the **WinForms Extensions - Syncfusion®** are installed or not in Visual Studio 2015 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension not installed, please install the extension by follow the steps from the [download and installation](https://help.Syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic. -1. To create a Syncfusion® Windows Forms project, follow either one of the options below: +1. To create a Syncfusion® Windows Forms project, follow either one of the options below: **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for WinForms > Create New Syncfusion® Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion Windows Forms Application via Syncfusion® menu](Project-Template-images\Syncfusion-menu.png) + ![Choose Syncfusion® Windows Forms Application via Syncfusion® menu](Project-Template-images\Syncfusion-menu.png) - N> In Visual Studio 2015 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. + N> In Visual Studio 2015 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. **Option 2:** - Choose **File -> New -> Project**. Opens a new dialog to create a new project. You can obtain the templates provided by Syncfusion® for WinForms by filtering the project type with Syncfusion® or by using the Syncfusion® keyword in the search option + Choose **File -> New -> Project**. Opens a new dialog to create a new project. You can obtain the templates provided by Syncfusion® for WinForms by filtering the project type with Syncfusion® or by using the Syncfusion® keyword in the search option - ![Choose Syncfusion Windows Forms Application from Visual Studio new project dialog](Project-Template-images\Syncfusion-Project-Template-Gallery2019-1.png) + ![Choose Syncfusion® Windows Forms Application from Visual Studio new project dialog](Project-Template-images\Syncfusion-Project-Template-Gallery2019-1.png) - In Visual Studio 2015 or lower, Select File > New > Project and navigate to Syncfusion® > Windows > Syncfusion® Windows Forms Application in Visual Studio. + In Visual Studio 2015 or lower, Select File > New > Project and navigate to Syncfusion® > Windows > Syncfusion® Windows Forms Application in Visual Studio. - ![Choose Syncfusion Windows Forms Application from Visual Studio new project dialog](Project-Template-images\Syncfusion-Project-Template-Gallery-1.png) + ![Choose Syncfusion® Windows Forms Application from Visual Studio new project dialog](Project-Template-images\Syncfusion-Project-Template-Gallery-1.png) 2. Name the **Project**, choose the destination location when required, select the project type, and choose the reference from where the assembly is added to the project then click **OK**. - N> Minimum target Framework is 3.5 for Syncfusion® WinForms project templates. + N> Minimum target Framework is 3.5 for Syncfusion® WinForms project templates. -3. Choose the options to configure the Syncfusion® WinForms Application by using the following Project Configuration Wizard. +3. Choose the options to configure the Syncfusion® WinForms Application by using the following Project Configuration Wizard. - ![Syncfusion Windows Forms project configuration wizard](Project-Template-images\Syncfusion-Project-Template-Gallery2019-2.png) + ![Syncfusion® Windows Forms project configuration wizard](Project-Template-images\Syncfusion-Project-Template-Gallery2019-2.png) - In Visual Studio 2015 or lower, Syncfusion® Windows Forms Application project configuration wizard. + In Visual Studio 2015 or lower, Syncfusion® Windows Forms Application project configuration wizard. - ![Syncfusion Windows Forms project configuration wizard](Project-Template-images\Syncfusion-Project-Template-Gallery-2.png) + ![Syncfusion® Windows Forms project configuration wizard](Project-Template-images\Syncfusion-Project-Template-Gallery-2.png) **Project Configurations** @@ -55,24 +55,24 @@ Use the following steps to create the Syncfusion® **Language:** Select the language, either CSharp or VB. - **Reference From:** Choose the assembly location such as NuGet, GAC Location, or Essential Studio® installed location, from where the assembly is added to the project. + **Reference From:** Choose the assembly location such as NuGet, GAC Location, or Essential Studio® installed location, from where the assembly is added to the project. - N> Installed location and GAC option will be available only when the Syncfusion® Essential Windows Forms setup has been installed. You can use NuGet option without installing the Syncfusion® Essential Windows Forms setup. + N> Installed location and GAC option will be available only when the Syncfusion® Essential Windows Forms setup has been installed. You can use NuGet option without installing the Syncfusion® Essential Windows Forms setup. **Installed ES Build Version:** Choose the build version to add the corresponding version assemblies to the project. - N> Installed ES build version option will be available only when you install the Syncfusion® Essential Windows Forms setup and choose the assembly location as Installed Location or GAC. + N> Installed ES build version option will be available only when you install the Syncfusion® Essential Windows Forms setup and choose the assembly location as Installed Location or GAC. **Select Window:** Choose the window as required for application. -4. After choosing above project configuration options in the Project Configuration Wizard, click the create button then Syncfusion® WinForms project is created with the necessary XAML files and required Syncfusion® WinForms assemblies/NuGet packages. +4. After choosing above project configuration options in the Project Configuration Wizard, click the create button then Syncfusion® WinForms project is created with the necessary XAML files and required Syncfusion® WinForms assemblies/NuGet packages. - ![Syncfusion Windows Forms project created with required references](Project-Template-images\Syncfusion-Project-Template-Gallery-6.png) + ![Syncfusion® Windows Forms project created with required references](Project-Template-images\Syncfusion-Project-Template-Gallery-6.png) - ![Syncfusion Windows Forms project created with required forms](Project-Template-images\Syncfusion-Project-Template-Gallery-7.png) + ![Syncfusion® Windows Forms project created with required forms](Project-Template-images\Syncfusion-Project-Template-Gallery-7.png) - ![Syncfusion Windows Forms project created with readme](Project-Template-images\Syncfusion-Project-Template-Gallery-9.PNG) + ![Syncfusion® Windows Forms project created with readme](Project-Template-images\Syncfusion-Project-Template-Gallery-9.PNG) -5. Then, the Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post to learn more the licensing changes introduced in Essential Studio®. +5. Then, the Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post to learn more the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion Windows Forms Project](Project-Template-images\Syncfusion-Project-Template-Gallery-8.png) \ No newline at end of file + ![Syncfusion® license registration required information dialog in Syncfusion® Windows Forms Project](Project-Template-images\Syncfusion-Project-Template-Gallery-8.png) \ No newline at end of file diff --git a/Extension/WindowsForms-Extension/Template-Studio.md b/Extension/WindowsForms-Extension/Template-Studio.md index ed35038a..fa2a9997 100644 --- a/Extension/WindowsForms-Extension/Template-Studio.md +++ b/Extension/WindowsForms-Extension/Template-Studio.md @@ -1,66 +1,66 @@ --- layout: post title: Template Studio | WinForms | Syncfusion -description: Visual Studio Project Templates for the Syncfusion WinForms platform to create Syncfusion WinForms Application by addiing the required assemblies +description: Visual Studio Project Templates for the Syncfusion WinForms platform to create Syncfusion WinForms Application by addiing the required assemblies platform: windowsforms -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® WinForms Template Studio +# Syncfusion® WinForms Template Studio -The WinForms Template Studio by Syncfusion® is a specialized tool for constructing applications with their WinForms components. This studio simplifies development by incorporating crucial Syncfusion® components, handling required NuGet references, offering preset namespaces, and creating component render code. Acting as a wizard, it facilitates the creation of WinForms applications using Syncfusion® components, streamlining the process for developers. +The WinForms Template Studio by Syncfusion® is a specialized tool for constructing applications with their WinForms components. This studio simplifies development by incorporating crucial Syncfusion® components, handling required NuGet references, offering preset namespaces, and creating component render code. Acting as a wizard, it facilitates the creation of WinForms applications using Syncfusion® components, streamlining the process for developers. -I> The Syncfusion® WinForms Template Studio is available from v24.1.41. +I> The Syncfusion® WinForms Template Studio is available from v24.1.41. -N> WinForms Template Studio is compatible with Visual Studio 2022, Visual Studio 2019, and Visual Studio 2017. For the Visual Studio 2015 or lower versions, it is recommended to use a [WinForms project template](https://help.syncfusion.com/windowsforms/visual-studio-integration/create-project). +N> WinForms Template Studio is compatible with Visual Studio 2022, Visual Studio 2019, and Visual Studio 2017. For the Visual Studio 2015 or lower versions, it is recommended to use a [WinForms project template](https://help.Syncfusion.com/windowsforms/visual-studio-integration/create-project). -Create the Syncfusion® WinForms project using the Visual Studio Project Template by following the provided steps. +Create the Syncfusion® WinForms project using the Visual Studio Project Template by following the provided steps. -> Check whether the **WinForms Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later, and for Visual Studio 2017 by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic. +> Check whether the **WinForms Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later, and for Visual Studio 2017 by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.Syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic. 1. Open the Visual Studio 2022. -2. Select one of the following options to create the Syncfusion® WinForms application +2. Select one of the following options to create the Syncfusion® WinForms application **Option 1:** - Choose **Extension -> Syncfusion® -> Essential Studio® for WinForms -> Create New Syncfusion® Project…** from the Visual Studio menu. + Choose **Extension -> Syncfusion® -> Essential Studio® for WinForms -> Create New Syncfusion® Project…** from the Visual Studio menu. - ![Choose Syncfusion WinForms Application from Visual Studio new project dialog via Syncfusion® menu](Template-Studio-Images/WF-1.png) + ![Choose Syncfusion® WinForms Application from Visual Studio new project dialog via Syncfusion® menu](Template-Studio-Images/WF-1.png) - N> In Visual Studio 2017, you can see the Syncfusion® menu directly in the Visual Studio menu. + N> In Visual Studio 2017, you can see the Syncfusion® menu directly in the Visual Studio menu. **Option 2:** - Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by Syncfusion® or typing Syncfusion® as a keyword in the search option can help you find the Syncfusion® templates for WinForms. + Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by Syncfusion® or typing Syncfusion® as a keyword in the search option can help you find the Syncfusion® templates for WinForms. - ![Choose Syncfusion WinForms Application from Visual Studio new project dialog](Template-Studio-Images/WF-2.png) + ![Choose Syncfusion® WinForms Application from Visual Studio new project dialog](Template-Studio-Images/WF-2.png) -3. Select the **Syncfusion WinForms Template Studio** and click Next. +3. Select the **Syncfusion® WinForms Template Studio** and click Next. - ![Choose Syncfusion WinForms Application from Visual Studio new project dialog](Template-Studio-Images/WF-3.png) + ![Choose Syncfusion® WinForms Application from Visual Studio new project dialog](Template-Studio-Images/WF-3.png) -4. When you launch the **Syncfusion WinForms Template Studio**, you will encounter a configuration wizard that allows you to set up your Syncfusion® WinForms application. Within this wizard, you will have the option to specify your preferred .NET Core Version or .NET Framework Version, select the desired language(CSharp or Visual Basic), and choose the reference type according to your requirements. +4. When you launch the **Syncfusion® WinForms Template Studio**, you will encounter a configuration wizard that allows you to set up your Syncfusion® WinForms application. Within this wizard, you will have the option to specify your preferred .NET Core Version or .NET Framework Version, select the desired language(CSharp or Visual Basic), and choose the reference type according to your requirements. - ![Syncfusion WinForms project configuration wizard](Template-Studio-Images/WF-5.png) + ![Syncfusion® WinForms project configuration wizard](Template-Studio-Images/WF-5.png) - N> The installed location and GAC options will be available only after the Syncfusion® Essential WinForms setup has been installed. Use the NuGet option instead of installing the Syncfusion® Essential WinForms setup. Also, the GAC option will not be available when you choose .NET 6.0, .NET 7.0, and .NET 8.0 from the project type option in Visual Studio. + N> The installed location and GAC options will be available only after the Syncfusion® Essential WinForms setup has been installed. Use the NuGet option instead of installing the Syncfusion® Essential WinForms setup. Also, the GAC option will not be available when you choose .NET 6.0, .NET 7.0, and .NET 8.0 from the project type option in Visual Studio. I> Visual Basic Language support is available in WinForms Template Studio starting from version 25.1.35. -5. Navigate to the **Type** tab and choose the Syncfusion® WinForms application type you want. When selecting the type of template for your application, you have two options: +5. Navigate to the **Type** tab and choose the Syncfusion® WinForms application type you want. When selecting the type of template for your application, you have two options: - ![Syncfusion WinForms project type selection wizard](Template-Studio-Images/WF-4.png) + ![Syncfusion® WinForms project type selection wizard](Template-Studio-Images/WF-4.png) **Predefined template:** Choose this option to select from 5 predefined templates, including Calendar, Contact, Outlook, Docking Manager, and Spreadsheet. By choosing one of these templates, you can create your application without needing to follow any further steps. - ![Syncfusion WinForms Predefined template wizard](Template-Studio-Images/WF-10.png) + ![Syncfusion® WinForms Predefined template wizard](Template-Studio-Images/WF-10.png) **Project type:** Choose this option to select from 4 project types, including Blank, Menu Bar, Ribbon, and Tabbed Form. -6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion® WinForms components you can add to the application. +6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion® WinForms components you can add to the application. - ![Syncfusion WinForms pages selection wizard](Template-Studio-Images/WF-6.png) + ![Syncfusion® WinForms pages selection wizard](Template-Studio-Images/WF-6.png) To unselect the added control(s), Click ‘x’ for the corresponding control in the control list from the Project Details. @@ -68,11 +68,11 @@ Create the Syncfusion® WinForms project us 7. Click **Next** or navigate to the **Control Features** tab to view the listed features for the selected controls. From here, choose the features needed. - ![Syncfusion WinForms control features selection wizard](Template-Studio-Images/WF-15.png) + ![Syncfusion® WinForms control features selection wizard](Template-Studio-Images/WF-15.png) 8. Click **Next** or navigate the **App Features** tab to select the desired application features. - ![Syncfusion WinForms app features selection wizard](Template-Studio-Images/WF-7.png) + ![Syncfusion® WinForms app features selection wizard](Template-Studio-Images/WF-7.png) N> The App Features option is not accessible for .NET Framework. @@ -80,15 +80,15 @@ Create the Syncfusion® WinForms project us In the **Project Details** section, modify configurations and project types. Additionally, you can remove one or more controls from the selected list and remove the chosen application feature. - ![Syncfusion WinForms project details selection and unselection wizard](Template-Studio-Images/WF-8.png) + ![Syncfusion® WinForms project details selection and unselection wizard](Template-Studio-Images/WF-8.png) -9. Click **Create** to generate the Syncfusion® WinForms application. Once you've created the project, the relevant Syncfusion® NuGet packages will be automatically added to your project for the chosen components. For example, if you add an **DataGrid** control, the corresponding Syncfusion® NuGet packages required for that control will be installed. +9. Click **Create** to generate the Syncfusion® WinForms application. Once you've created the project, the relevant Syncfusion® NuGet packages will be automatically added to your project for the chosen components. For example, if you add an **DataGrid** control, the corresponding Syncfusion® NuGet packages required for that control will be installed. - ![Syncfusion WinForms project created with readme](Template-Studio-Images/WF-9.png) + ![Syncfusion® WinForms project created with readme](Template-Studio-Images/WF-9.png) ![NuGetEntry](Template-Studio-Images/NuGetEntry.png) - To find out which NuGet packages are needed for other WinForms controls, please refer to this [documentation link](https://help.syncfusion.com/windowsforms/control-dependencies) for detailed information on the required packages for each control. + To find out which NuGet packages are needed for other WinForms controls, please refer to this [documentation link](https://help.Syncfusion.com/windowsforms/control-dependencies) for detailed information on the required packages for each control. 10. When you create a WinForms project, the following Dependency Injection (DI) setup is added to the **Program.cs** file. This setup registers services, view models, and views with the DI container, ensuring proper functionality and service management within your application. Below **ConfigureServices** method in program.cs file establishes the DI setup in a WinForms project. It manages the application's services, view models, and views. Here's a detailed breakdown: @@ -152,6 +152,6 @@ Here's a simple explanation: > > -13. If you install the trial setup or NuGet packages from nuget.org, you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from the 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. +13. If you install the trial setup or NuGet packages from nuget.org, you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from the 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion WinForms project](Template-Studio-Images/Syncfusion-Project-Template-Gallery-8.png) \ No newline at end of file + ![Syncfusion® license registration required information dialog in Syncfusion® WinForms project](Template-Studio-Images/Syncfusion-Project-Template-Gallery-8.png) \ No newline at end of file diff --git a/Extension/WindowsForms-Extension/Toolbox-Configuration.md b/Extension/WindowsForms-Extension/Toolbox-Configuration.md index 357272f1..7f0ab016 100644 --- a/Extension/WindowsForms-Extension/Toolbox-Configuration.md +++ b/Extension/WindowsForms-Extension/Toolbox-Configuration.md @@ -1,7 +1,7 @@ --- layout: post title: Toolbox Configuration | WinForms | Syncfusion -description: This section provides information regarding all the Syncfusion Essential Studio utilities and its usage +description: This section provides information regarding all the Syncfusion Essential Studio utilities and its usage platform: extension control: Essential Studio documentation: ug @@ -9,27 +9,27 @@ documentation: ug # Toolbox Configuration -The Syncfusion® Toolbox utility adds the Syncfusion® WinForms controls into the Visual Studio .NET toolbox. +The Syncfusion® Toolbox utility adds the Syncfusion® WinForms controls into the Visual Studio .NET toolbox. -N> Visual Studio Express Edition does not support toolbox configuration. However, you can manually configure the Syncfusion® controls into the Visual Studio Express Toolbox. To do so, refer the [Manual Toolbox Configuration](https://help.syncfusion.com/common/faq/how-to-configure-the-toolbox-of-visual-studio-manually). +N> Visual Studio Express Edition does not support toolbox configuration. However, you can manually configure the Syncfusion® controls into the Visual Studio Express Toolbox. To do so, refer the [Manual Toolbox Configuration](https://help.Syncfusion.com/common/faq/how-to-configure-the-toolbox-of-visual-studio-manually). -Syncfusion controls will be automatically configured in the Visual Studio toolbox, while installing the Syncfusion® Windows Forms installer, if the “Configure Syncfusion® Controls in Visual Studio” checkbox is selected from installer UI. +Syncfusion® controls will be automatically configured in the Visual Studio toolbox, while installing the Syncfusion® Windows Forms installer, if the “Configure Syncfusion® Controls in Visual Studio” checkbox is selected from installer UI. -Use the following steps to add the Syncfusion® WinForms controls through the Syncfusion® Toolbox Installer: +Use the following steps to add the Syncfusion® WinForms controls through the Syncfusion® Toolbox Installer: 1. To launch Toolbox configuration utility, follow either one of the options below: **Option 1:** - To open the Syncfusion® Control Panel, click **Add On and Utilities > Toolbox Installer**. + To open the Syncfusion® Control Panel, click **Add On and Utilities > Toolbox Installer**. ![Add On and Utilities](Toolbox-Configuration_images/Toolbox-Configuration_img1.png) **Option 2:** - Click **Syncfusion menu** and choose **Essential Studio for WinForms > Toolbox Configuration...** in **Visual Studio**. + Click **Syncfusion® menu** and choose **Essential Studio® for WinForms > Toolbox Configuration...** in **Visual Studio**. - ![Toolbox Installer via Syncfusion menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) + ![Toolbox Installer via Syncfusion® menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. 2. Toolbox Installer will be opened. @@ -37,17 +37,17 @@ Use the following steps to add the Syncfusion®® controls in VS 2005 toolbox. - * Install VS2008 – Configures Framework 3.5 Syncfusion® controls in VS 2008 toolbox. - * Install VS2010 – Configures Framework 4.0 Syncfusion® controls in VS 2010 toolbox. - * Install VS2012 – Configures Framework 4.5 Syncfusion® controls in VS 2012 toolbox. - * Install VS2013 – Configures Framework 4.5.1 Syncfusion® controls in VS 2013 toolbox. - * Install VS2015 – Configures Framework 4.6 Syncfusion® controls in VS 2015 toolbox. - * Install VS2017 – Configures Framework 4.6 Syncfusion® controls in VS 2017 toolbox. - * Install VS2019 – Configures Framework 4.6 Syncfusion® controls in VS 2019 toolbox - * Install VS2022 – Configures Framework 4.6 Syncfusion® controls in VS 2019 toolbox + * Install VS2005 – Configures Framework 2.0 Syncfusion® controls in VS 2005 toolbox. + * Install VS2008 – Configures Framework 3.5 Syncfusion® controls in VS 2008 toolbox. + * Install VS2010 – Configures Framework 4.0 Syncfusion® controls in VS 2010 toolbox. + * Install VS2012 – Configures Framework 4.5 Syncfusion® controls in VS 2012 toolbox. + * Install VS2013 – Configures Framework 4.5.1 Syncfusion® controls in VS 2013 toolbox. + * Install VS2015 – Configures Framework 4.6 Syncfusion® controls in VS 2015 toolbox. + * Install VS2017 – Configures Framework 4.6 Syncfusion® controls in VS 2017 toolbox. + * Install VS2019 – Configures Framework 4.6 Syncfusion® controls in VS 2019 toolbox + * Install VS2022 – Configures Framework 4.6 Syncfusion® controls in VS 2019 toolbox - N> You can also configure Syncfusion® controls from a lower version Framework assembly to higher version of Visual Studio. + N> You can also configure Syncfusion® controls from a lower version Framework assembly to higher version of Visual Studio. 3. The successful configuration of Toolbox is indicated by an Information message. Click **OK**. diff --git a/Extension/WindowsForms-Extension/Troubleshooting.md b/Extension/WindowsForms-Extension/Troubleshooting.md index d1b1ce0b..1f6f26cc 100644 --- a/Extension/WindowsForms-Extension/Troubleshooting.md +++ b/Extension/WindowsForms-Extension/Troubleshooting.md @@ -1,50 +1,50 @@ --- layout: post title: Troubleshooting | WinForms | Syncfusion -description: Syncfusion Troubleshooter is Visual Studio extension to troubleshoot the configuration issues in Syncfusion assembly reference, webconfig entries in projects. +description: Syncfusion Troubleshooter is Visual Studio extension to troubleshoot the configuration issues in Syncfusion assembly reference, webconfig entries in projects. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Troubleshoot the project -Troubleshoot the project with the Syncfusion® configuration and apply the fix, such as adding a Syncfusion® assembly to the project with the wrong .NET Framework version or missing any Syncfusion® dependent assembly of a referred assembly. The Syncfusion® Troubleshooter is capable of performing the following tasks: +Troubleshoot the project with the Syncfusion® configuration and apply the fix, such as adding a Syncfusion® assembly to the project with the wrong .NET Framework version or missing any Syncfusion® dependent assembly of a referred assembly. The Syncfusion® Troubleshooter is capable of performing the following tasks: * Report the Configuration issues. * Apply the solution. ## Report the Configuration issues -The following steps help you to utilize the Syncfusion® Troubleshooter by Visual Studio. +The following steps help you to utilize the Syncfusion® Troubleshooter by Visual Studio. -> Before use the Syncfusion® Troubleshooter for WinForms, check whether the **WinForms Extensions - Syncfusion** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed.If this extension not installed, please install the extension by follow the steps from the [download and installation](https://help.syncfusion.com/windowsforms/visual-studio-integration/vs2019-extensions/download-and-installation/) help topic. +> Before use the Syncfusion® Troubleshooter for WinForms, check whether the **WinForms Extensions - Syncfusion®** installed or not in Visual Studio Extension Manager by clicking on the Tools -> Extensions and Updates -> Installed for Visual Studio 2017 or lower and for Visual Studio 2019 by clicking on the Extensions -> Manage Extensions -> Installed.If this extension not installed, please install the extension by follow the steps from the [download and installation](https://help.Syncfusion.com/windowsforms/visual-studio-integration/vs2019-extensions/download-and-installation/) help topic. -1. To open Syncfusion® Troubleshooter Wizard, follow either one of the options below: +1. To open Syncfusion® Troubleshooter Wizard, follow either one of the options below: **Option 1:** - Open an existing Syncfusion® WinForms Application, Click **Syncfusion Menu** and choose **Essential Studio for WinForms > Troubleshoot…** in Visual Studio. + Open an existing Syncfusion® WinForms Application, Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms > Troubleshoot…** in Visual Studio. - ![Syncfusion Troubleshooter via Syncfusion menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) + ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2:** - Right-click the Project file in Solution Explorer, then select the command Syncfusion® Troubleshooter… + Right-click the Project file in Solution Explorer, then select the command Syncfusion® Troubleshooter… - ![Syncfusion Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.jpeg) + ![Syncfusion® Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.jpeg) -2. Analyze the project now, and if any Syncfusion® controls project configuration errors are discovered, they will be reported in the Troubleshooter dialog.  If there are no configuration issues with the project, the dialog box will indicate that no modifications are required in the following areas: +2. Analyze the project now, and if any Syncfusion® controls project configuration errors are discovered, they will be reported in the Troubleshooter dialog.  If there are no configuration issues with the project, the dialog box will indicate that no modifications are required in the following areas: -* Syncfusion® assembly references. -* Syncfusion® NuGet Packages. -* Syncfusion® Toolbox Configuration. +* Syncfusion® assembly references. +* Syncfusion® NuGet Packages. +* Syncfusion® Toolbox Configuration. ![No configuration changes required dialog box](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img2.png) -I> The Syncfusion® Troubleshooter command will be visible only for Syncfusion® projects that means Syncfusion® assemblies or Syncfusion® NuGet packages should be referred in to the project. +I> The Syncfusion® Troubleshooter command will be visible only for Syncfusion® projects that means Syncfusion® assemblies or Syncfusion® NuGet packages should be referred in to the project. -The Syncfusion® Troubleshooter handles the following project configuration issues: +The Syncfusion® Troubleshooter handles the following project configuration issues: 1. Assembly Reference Issues. @@ -54,25 +54,25 @@ The Syncfusion® Troubleshooter handles the ### Assembly Reference Issues -The Syncfusion® Troubleshooter deals with the following assembly reference issues in Syncfusion® Projects. +The Syncfusion® Troubleshooter deals with the following assembly reference issues in Syncfusion® Projects. 1. Dependent assemblies are missing for referred assemblies from project. - **For Instance:** If “Syncfusion.Grid.Windows” assembly referred in project and “Syncfusion.Shared.Windows” (dependent of Syncfusion.Grid.Windows) not referred in project, the Syncfusion® Troubleshooter will show dependent assembly missing. + **For Instance:** If “Syncfusion.Grid.Windows” assembly referred in project and “Syncfusion.Shared.Windows” (dependent of Syncfusion.Grid.Windows) not referred in project, the Syncfusion® Troubleshooter will show dependent assembly missing. ![Dependent assemblies missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img3.png) -2. Syncfusion® assembly version mismatched. Compare to all Syncfusion® assembly’s versions in the same project. If found any Syncfusion® assembly version inconsistency, the Syncfusion® Troubleshooter will show Syncfusion® assemblies version mismatched. +2. Syncfusion® assembly version mismatched. Compare to all Syncfusion® assembly’s versions in the same project. If found any Syncfusion® assembly version inconsistency, the Syncfusion® Troubleshooter will show Syncfusion® assemblies version mismatched. - **For Instance:** If “Syncfusion.Tools.Windows” assembly (v15.2450.0.40) referred in project, but other Syncfusion® assemblies referred assembly version is v15.2450.0.43. Syncfusion® Troubleshooter will be shown Syncfusion® assembly version mismatched. + **For Instance:** If “Syncfusion.Tools.Windows” assembly (v15.2450.0.40) referred in project, but other Syncfusion® assemblies referred assembly version is v15.2450.0.43. Syncfusion® Troubleshooter will be shown Syncfusion® assembly version mismatched. ![Assembly version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img4.png) -3. Framework version mismatching (Syncfusion Assemblies) with project’s .NET Framework version. Find the supported .NET Framework details for Syncfusion® assemblies in the following link, +3. Framework version mismatching (Syncfusion® Assemblies) with project’s .NET Framework version. Find the supported .NET Framework details for Syncfusion® assemblies in the following link, - + - **For Instance:** The.NET Framework of the application is v4.5 and “Syncfusion.Tools.Windows” assembly (v17.1460.0.38 & .NET Framework version 4.6) referred in same application. The Syncfusion® Troubleshooter will show Syncfusion® assembly .NET Framework version is incompatible with project’s .NET Framework version. + **For Instance:** The.NET Framework of the application is v4.5 and “Syncfusion.Tools.Windows” assembly (v17.1460.0.38 & .NET Framework version 4.6) referred in same application. The Syncfusion® Troubleshooter will show Syncfusion® assembly .NET Framework version is incompatible with project’s .NET Framework version. ![Target Framework version of application](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img5.png) @@ -80,23 +80,23 @@ The Syncfusion® Troubleshooter deals with ### NuGet Issues -The Syncfusion® Troubleshooter deals with the following NuGet package related issues in Syncfusion® projects. +The Syncfusion® Troubleshooter deals with the following NuGet package related issues in Syncfusion® projects. -1. Multiple versions of Syncfusion® NuGet Packages are installed. If Syncfusion® NuGet Package version is differ from other Syncfusion® NuGet Package version, the Syncfusion® Troubleshooter will show Syncfusion® NuGet package version is mismatched. +1. Multiple versions of Syncfusion® NuGet Packages are installed. If Syncfusion® NuGet Package version is differ from other Syncfusion® NuGet Package version, the Syncfusion® Troubleshooter will show Syncfusion® NuGet package version is mismatched. - **For Instance:** Syncfusion® WinForms platform packages installed multiple version (v16.4.0.54 & v17.1.0.38), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched. + **For Instance:** Syncfusion® WinForms platform packages installed multiple version (v16.4.0.54 & v17.1.0.38), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched. - ![Syncfusion NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) + ![Syncfusion® NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) -2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version. +2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version. - **For Instance:** Syncfusion.SfBulletGraph.Windows40 NuGet package version(v15.2.0.17 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, the Syncfusion® Troubleshooter will show Syncfusion® package Framework version is mismatched. + **For Instance:** Syncfusion®.SfBulletGraph.Windows40 NuGet package version(v15.2.0.17 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, the Syncfusion® Troubleshooter will show Syncfusion® package Framework version is mismatched. - ![Syncfusion NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.png) + ![Syncfusion® NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.png) -3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. +3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. - **For Instance:** If install Syncfusion.Chart.Windows NuGet package alone in project, the Syncfusion® Troubleshooter will show the Syncfusion.Chart.Base and other dependent NuGet package missing. + **For Instance:** If install Syncfusion®.Chart.Windows NuGet package alone in project, the Syncfusion® Troubleshooter will show the Syncfusion®.Chart.Base and other dependent NuGet package missing. ![Dependent NuGet package missing issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.png) @@ -104,34 +104,34 @@ I> Internet connection is required to restore the missing dependent packages. If ### Toolbox Configuration Issues -The Syncfusion® Troubleshooter deals with the following Toolbox Configuration related issues in Syncfusion® projects. +The Syncfusion® Troubleshooter deals with the following Toolbox Configuration related issues in Syncfusion® projects. -1. If the project .NET Framework version is not installed/configured Syncfusion® Toolbox, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox .NET Framework version is mismatched. +1. If the project .NET Framework version is not installed/configured Syncfusion® Toolbox, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox .NET Framework version is mismatched. - **For Instance:** The project .NET Framework version is 4.5 and Syncfusion® Toolbox is not configured 4.6 framework assemblies only in corresponding Visual Studio, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox framework version mismatched. + **For Instance:** The project .NET Framework version is 4.5 and Syncfusion® Toolbox is not configured 4.6 framework assemblies only in corresponding Visual Studio, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox framework version mismatched. - ![Syncfusion Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) + ![Syncfusion® Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) -2. If Syncfusion® Toolbox configured version is differed from latest Syncfusion® assembly reference version or NuGet package version in same project, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version is mismatched. +2. If Syncfusion® Toolbox configured version is differed from latest Syncfusion® assembly reference version or NuGet package version in same project, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version is mismatched. - **For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched. + **For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched. - ![Syncfusion Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) + ![Syncfusion® Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) ## Apply the solution -1. After loading the Syncfusion® Troubleshooter dialog, check the corresponding check box of the issue to be resolved. Then click the “Fix Issue(s)” button. +1. After loading the Syncfusion® Troubleshooter dialog, check the corresponding check box of the issue to be resolved. Then click the “Fix Issue(s)” button. - ![Syncfusion Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.png) + ![Syncfusion® Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.png) 2. A dialog appears, which will ask to take a backup of the project before performing the troubleshooting process. If you need to backup the project before troubleshooting, click “Yes” button. - ![Syncfusion Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpeg) + ![Syncfusion® Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpeg) -3. Wait for a while, the Syncfusion® Troubleshooter is resolving the selected issues. After the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully”. +3. Wait for a while, the Syncfusion® Troubleshooter is resolving the selected issues. After the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully”. - ![Syncfusion Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpeg) + ![Syncfusion® Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpeg) -4. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. +4. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.jpeg) \ No newline at end of file + ![Syncfusion® license registration required information dialog in Syncfusion® Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.jpeg) \ No newline at end of file diff --git a/Extension/WindowsForms-Extension/download-and-installation.md b/Extension/WindowsForms-Extension/download-and-installation.md index d0749155..7f50ed8b 100644 --- a/Extension/WindowsForms-Extension/download-and-installation.md +++ b/Extension/WindowsForms-Extension/download-and-installation.md @@ -3,23 +3,23 @@ layout: post title: Downloand and Installation | WinForms | Syncfusion description: this section provide the information about how to download and install the extensions in Visual Studio. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -Syncfusion publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions). You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. +Syncfusion® publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions). You can either install it directly from Visual Studio or download and install it from the Visual Studio marketplace. ## Prerequisites -The following software prerequisites must be installed to install the Syncfusion® WinForms extension, as well as to creating, adding snippet, converting, and upgrading Syncfusion® WinForms applications. +The following software prerequisites must be installed to install the Syncfusion® WinForms extension, as well as to creating, adding snippet, converting, and upgrading Syncfusion® WinForms applications. * [Visual Studio 2010 or later](https://visualstudio.microsoft.com/downloads). ## Install through the Visual Studio Manage Extensions -The steps below assist you to how to install the Syncfusion® WinForms extensions from **Visual Studio Manage Extensions**. +The steps below assist you to how to install the Syncfusion® WinForms extensions from **Visual Studio Manage Extensions**. 1. Open the Visual Studio 2019. @@ -27,11 +27,11 @@ The steps below assist you to how to install the Syncfusion® extensions from the Visual Studio. +8. Now, under the menu **Extensions**, you can use the Syncfusion® extensions from the Visual Studio. ![SyncfusionMenu](Download-Installation-Images/SyncfusionMenu.png) ## Install from the Visual Studio Marketplace -The steps below illustrate how to download and install the Syncfusion® Windows extension from the Visual Studio Marketplace. +The steps below illustrate how to download and install the Syncfusion® Windows extension from the Visual Studio Marketplace. -1. Download the [Syncfusion WinForms Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions) from the Visual Studio Marketplace. +1. Download the [Syncfusion® WinForms Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions) from the Visual Studio Marketplace. 2. Close all Visual Studio instances running, if any. @@ -59,6 +59,6 @@ The steps below illustrate how to download and install the Syncfusion® extensions from the Visual Studio under the **Extensions** menu. +5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the **Extensions** menu. ![SyncfusionMenu](Download-Installation-Images/SyncfusionMenu.png) \ No newline at end of file diff --git a/Extension/Xamarin-Extension/Check-for-Updates.md b/Extension/Xamarin-Extension/Check-for-Updates.md index 84adc0dc..00dee5b8 100644 --- a/Extension/Xamarin-Extension/Check-for-Updates.md +++ b/Extension/Xamarin-Extension/Check-for-Updates.md @@ -1,30 +1,30 @@ --- layout: post title: Check for Updates | Xamarin | Syncfusion -description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. +description: Syncfusion Check for Updates provides Extensions to update most recent version of the Essential Studio release. platform: extension control: Visual Studio Extensions documentation: ug --- -# Check for Updates in Syncfusion® Xamarin +# Check for Updates in Syncfusion® Xamarin -Syncfusion® provides Extensions to update the most recent version of the Essential Studio® release. Installing the most recent version ensures that you always have the most up-to-date features, fixes, and improvements. +Syncfusion® provides Extensions to update the most recent version of the Essential Studio® release. Installing the most recent version ensures that you always have the most up-to-date features, fixes, and improvements. -I> The Syncfusion® Check for updates is available from v17.1.0.32. +I> The Syncfusion® Check for updates is available from v17.1.0.32. You can check updates availability in Visual Studio, and then install the update version if required. -1. Choose **Syncfusion -> Check for Updates…** in the Visual Studio menu +1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu - ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) + ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1_2019.png) + ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1_2019.png) 2. When an update is available, the Update dialog box appears. - ![Syncfusion check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) + ![Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) -3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. +3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. diff --git a/Extension/Xamarin-Extension/Create-Project.md b/Extension/Xamarin-Extension/Create-Project.md index 34e1441c..61193053 100644 --- a/Extension/Xamarin-Extension/Create-Project.md +++ b/Extension/Xamarin-Extension/Create-Project.md @@ -1,53 +1,53 @@ --- layout: post title: Create Project | xamarin | Syncfusion -description: Syncfusion Project Templates Extension creates the Syncfusion Xamarin Application by adding the required Syncfusion NuGet packages. +description: Syncfusion Project Templates Extension creates the Syncfusion Xamarin Application by adding the required Syncfusion NuGet packages. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Creating Syncfusion® Xamarin Application +# Creating Syncfusion® Xamarin Application -Syncfusion provides Visual Studio Project Templates for the Syncfusion® Xamarin platform, allowing you to quickly develop a Syncfusion® Xamarin application by just adding the needed Syncfusion® NuGet packages for the control you want to use. +Syncfusion® provides Visual Studio Project Templates for the Syncfusion® Xamarin platform, allowing you to quickly develop a Syncfusion® Xamarin application by just adding the needed Syncfusion® NuGet packages for the control you want to use. -I> The Syncfusion® Xamarin Project Templates are available from v16.2.0.41. +I> The Syncfusion® Xamarin Project Templates are available from v16.2.0.41. -To create the **Syncfusion Xamarin Application** in Visual Studio 2017, follow these steps +To create the **Syncfusion® Xamarin Application** in Visual Studio 2017, follow these steps -> Check whether the **Xamarin Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by going to **Tools -> Extensions and Updates -> Installed** for Visual Studio 2017 or lower, and **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 by going to **Extensions -> Manage Extensions -> Installed**. If this extension not installed, please install the extension by follow the steps from the [download and installation](download-and-installation) help topic. +> Check whether the **Xamarin Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by going to **Tools -> Extensions and Updates -> Installed** for Visual Studio 2017 or lower, and **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 by going to **Extensions -> Manage Extensions -> Installed**. If this extension not installed, please install the extension by follow the steps from the [download and installation](download-and-installation) help topic. -1. Follow one of the instructions below to create a Syncfusion® Xamarin project +1. Follow one of the instructions below to create a Syncfusion® Xamarin project **Option 1:** - Click **Syncfusion Menu** and choose **Essential Studio for Xamarin > Create New Syncfusion® Project…** in **Visual Studio**. + Click **Syncfusion® Menu** and choose **Essential Studio® for Xamarin > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion Xamarin application from Visual Studio new project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion® Xamarin application from Visual Studio new project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) - N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. + N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Choose Syncfusion Xamarin application from Visual Studio new project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate_2019.png) + ![Choose Syncfusion® Xamarin application from Visual Studio new project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate_2019.png) **Option 2:** - Choose **File > New > Project** and navigate to **Syncfusion > Cross-Platform > Syncfusion® Xamarin Project Template** in **Visual Studio**. + Choose **File > New > Project** and navigate to **Syncfusion® > Cross-Platform > Syncfusion® Xamarin Project Template** in **Visual Studio**. - ![Choose Syncfusion Xamarin application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1.jpeg) + ![Choose Syncfusion® Xamarin application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1.jpeg) - In Visual Studio 2019, Syncfusion® Xamarin project creation wizard like below. + In Visual Studio 2019, Syncfusion® Xamarin project creation wizard like below. - ![Choose Syncfusion Xamarin application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1_2019.png) + ![Choose Syncfusion® Xamarin application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1_2019.png) 2. Click **OK** once you've given the **project name**, selected a destination location, and set the project's Framework. The Project Configuration Wizard is now displayed. -3. Choose the Project, Android, iOS, and UWP by on/off in the following Project Configuration window to configure the Syncfusion® Xamarin Application. +3. Choose the Project, Android, iOS, and UWP by on/off in the following Project Configuration window to configure the Syncfusion® Xamarin Application. - ![Syncfusion Xamarin project configuaration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img2.jpeg) + ![Syncfusion® Xamarin project configuaration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img2.jpeg) **Project Configuration:** - **Assemblies From:** Choose NuGet or Installed Location to load the Syncfusion® Xamarin reference into Xamarin Application. + **Assemblies From:** Choose NuGet or Installed Location to load the Syncfusion® Xamarin reference into Xamarin Application. - N> Installed location option will be shown only when the Syncfusion® Xamarin setup has been installed. + N> Installed location option will be shown only when the Syncfusion® Xamarin setup has been installed. **Android** @@ -59,46 +59,46 @@ To create the **Syncfusion Xamarin Application** in Visual Studio 2017, follow t 1. **Target Device:** Choose the Xamarin.iOS device of Xamarin.iOS project either Unified, iPhone/iPod, or iPad. 2. **Target Version:** Select the Xamarin.iOS Project version. - **Choose controls:** To create the Syncfusion® Xamarin application, choose at least one Syncfusion® control. + **Choose controls:** To create the Syncfusion® Xamarin application, choose at least one Syncfusion® control. - N> If you want to add other Syncfusion® Xamarin controls in the created Syncfusion® Xamarin application, you can use our [Syncfusion Xamarin toolbox](https://help.syncfusion.com/xamarin/visual-studio-integration/toolbox-control) + N> If you want to add other Syncfusion® Xamarin controls in the created Syncfusion® Xamarin application, you can use our [Syncfusion® Xamarin toolbox](https://help.syncfusion.com/xamarin/visual-studio-integration/toolbox-control) - ![Choose Syncfusion Xamarin control](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.png) + ![Choose Syncfusion® Xamarin control](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.png) -4. The Syncfusion® Xamarin Application has been created when you click **Create**. +4. The Syncfusion® Xamarin Application has been created when you click **Create**. N> Choose any one of the project type and controls from Project Configuration Wizard. - ![Selected Syncfusion Xamarin control assemblies added to the UWP project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img13.PNG) + ![Selected Syncfusion® Xamarin control assemblies added to the UWP project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img13.PNG) -5. Based on the control selected, required Syncfusion® NuGet/Assemblies and configuration have been added to the project. +5. Based on the control selected, required Syncfusion® NuGet/Assemblies and configuration have been added to the project. **Net Standard /PCL** - ![Selected Syncfusion Xamarin control NuGet package installed in project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img3.jpeg) + ![Selected Syncfusion® Xamarin control NuGet package installed in project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img3.jpeg) - ![Selected Syncfusion Xamarin control assemblies added to the project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) + ![Selected Syncfusion® Xamarin control assemblies added to the project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) **Android** - ![Selected Syncfusion Xamarin control Android NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img6.jpeg) + ![Selected Syncfusion® Xamarin control Android NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img6.jpeg) - ![Selected Syncfusion Xamarin control assemblies added to the Android project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img7.jpeg) + ![Selected Syncfusion® Xamarin control assemblies added to the Android project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img7.jpeg) **iOS** - ![Selected Syncfusion Xamarin control iOS NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img8.jpeg) + ![Selected Syncfusion® Xamarin control iOS NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img8.jpeg) - ![Selected Syncfusion Xamarin control assemblies added to the iOS project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img9.jpeg) + ![Selected Syncfusion® Xamarin control assemblies added to the iOS project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img9.jpeg) **UWP** - ![Selected Syncfusion Xamarin control UWP NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img10.jpeg) + ![Selected Syncfusion® Xamarin control UWP NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img10.jpeg) - ![Selected Syncfusion Xamarin control assemblies added to the UWP project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img11.jpeg) + ![Selected Syncfusion® Xamarin control assemblies added to the UWP project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img11.jpeg) -6. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio. +6. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion license registration required information dialog in Syncfusion Xamarin Project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img12.jpeg) + ![Syncfusion® license registration required information dialog in Syncfusion® Xamarin Project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img12.jpeg) diff --git a/Extension/Xamarin-Extension/Download-and-Installation.md b/Extension/Xamarin-Extension/Download-and-Installation.md index 4567f113..7448ce7a 100644 --- a/Extension/Xamarin-Extension/Download-and-Installation.md +++ b/Extension/Xamarin-Extension/Download-and-Installation.md @@ -1,20 +1,20 @@ --- layout: post title: Download and Installation | Xamarin | Syncfusion -description: How to download and install the Syncfusion Xamarin Visual Studio Extensions from Visual Studio Market Place +description: How to download and install the Syncfusion Xamarin Visual Studio Extensions from Visual Studio Market Place platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Download and Installation -In [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.XamarinExtension), Syncfusion® publishing the Xamarin Visual Studio extension. You can either use the Visual Studio to install it or go to the Visual Studio marketplace to download and install it. +In [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.XamarinExtension), Syncfusion® publishing the Xamarin Visual Studio extension. You can either use the Visual Studio to install it or go to the Visual Studio marketplace to download and install it. ## Install through the Visual Studio Manage Extensions -The steps below assist you to how to install the Syncfusion® Xamarin extensions from Visual Studio **Manage Extensions**. +The steps below assist you to how to install the Syncfusion® Xamarin extensions from Visual Studio **Manage Extensions**. 1. Open the Visual Studio. 2. Navigate to **Extension -> Manage Extensions** and open the Manage Extensions. @@ -22,26 +22,26 @@ The steps below assist you to how to install the Syncfusion® extensions from Visual Studio under the Extensions menu. +8. Now, you can use the Syncfusion® extensions from Visual Studio under the Extensions menu. - ![Syncfusion Xamarin Menu](Download-and-Installation-images/SyncfusionXamarinMenu.png) + ![Syncfusion® Xamarin Menu](Download-and-Installation-images/SyncfusionXamarinMenu.png) ## Install from the Visual Studio Marketplace -The steps below illustrate how to download and install the Syncfusion® Xamarin extension from the Visual Studio Marketplace. +The steps below illustrate how to download and install the Syncfusion® Xamarin extension from the Visual Studio Marketplace. -1. Download the [Syncfusion Xamarin Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.XamarinExtension) from the Visual Studio Marketplace. +1. Download the [Syncfusion® Xamarin Extensions](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.XamarinExtension) from the Visual Studio Marketplace. 2. If any Visual Studio instances are still open, close them. 3. Double-click on the downloaded VSIX file to install. You can see the VSIX installation prompts for the Visual Studio 2019 version. If Visual Studio 2019 is not installed, it will not be possible to install the extension ![Vsix Modify Window](Download-and-Installation-images/VSIXInstall.png) 4. Click the **Install** button. -5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the Extensions menu. +5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the Extensions menu. - ![Syncfusion Xamarin Menu](Download-and-Installation-images/SyncfusionXamarinMenu.png) \ No newline at end of file + ![Syncfusion® Xamarin Menu](Download-and-Installation-images/SyncfusionXamarinMenu.png) \ No newline at end of file diff --git a/Extension/Xamarin-Extension/Essential-UI-Kit.md b/Extension/Xamarin-Extension/Essential-UI-Kit.md index 87632ed0..d3d14276 100644 --- a/Extension/Xamarin-Extension/Essential-UI-Kit.md +++ b/Extension/Xamarin-Extension/Essential-UI-Kit.md @@ -1,29 +1,29 @@ --- layout: post title: Essential UI Kit | Xamarin | Syncfusion -description: The Syncfusion Xamarin Essential UI Kit extension provides the predefined design for the Xamarin.Forms. +description: The Syncfusion Xamarin Essential UI Kit extension provides the predefined design for the Xamarin.Forms. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Xamarin Essential® UI Kit +# Xamarin Essential® UI Kit -Essential® UI Kit for Xamarin.Forms includes predefined XAML templates for Xamarin.Forms apps. The UI kit allows to build a user interface in a cross-platform application. It clearly separates the View, View Model, and Model classes, making it simple to integrate your business logic and make changes to the existing view. +Essential® UI Kit for Xamarin.Forms includes predefined XAML templates for Xamarin.Forms apps. The UI kit allows to build a user interface in a cross-platform application. It clearly separates the View, View Model, and Model classes, making it simple to integrate your business logic and make changes to the existing view. ## Installation of Xamarin UI Kit Extension -Install the appropriate [Xamarin UI Kit Extension](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Essential-UI-Kit-Xamarin-Forms) in Visual Studio by downloading them from the marketplace. As a result, you can use the Syncfusion® Extension from your project's Syncfusion® menu. +Install the appropriate [Xamarin UI Kit Extension](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Essential-UI-Kit-Xamarin-Forms) in Visual Studio by downloading them from the marketplace. As a result, you can use the Syncfusion® Extension from your project's Syncfusion® menu. ## Include XAML templates in Xamarin.Forms apps 1. Launch a new or existing Xamarin application. -2. Select the **Essential® UI Kit for Xamarin.Forms** from the **Solution Explorer** by right-clicking on your **Xamarin.Forms** project +2. Select the **Essential® UI Kit for Xamarin.Forms** from the **Solution Explorer** by right-clicking on your **Xamarin.Forms** project - ![Syncfusion Essential UI Kit Context menu](Essential-UI-Kit-images/Context-Menu.png) + ![Syncfusion® Essential® UI Kit Context menu](Essential-UI-Kit-images/Context-Menu.png) - N> The Essential® UI Kit for Xamarin.Forms add-in will be shown when the project has the Xamarin.Forms NuGet package as a reference and also, Xamarin.Forms project should be a NET Standard project. + N> The Essential® UI Kit for Xamarin.Forms add-in will be shown when the project has the Xamarin.Forms NuGet package as a reference and also, Xamarin.Forms project should be a NET Standard project. 3. The Category dialogue box will then appear, with its pre-defined template. @@ -35,7 +35,7 @@ Install the appropriate [Xamarin UI Kit Extension](https://marketplace.visualstu ![Edit page Name](Essential-UI-Kit-images/edit-page-name.png) -6. The selected pages will be added along with View, View Model, Model classes, resource files and Syncfusion® NuGet package reference, +6. The selected pages will be added along with View, View Model, Model classes, resource files and Syncfusion® NuGet package reference, ![MVVM files](Essential-UI-Kit-images/mvvm-files.png) @@ -43,7 +43,7 @@ Install the appropriate [Xamarin UI Kit Extension](https://marketplace.visualstu ![Added Resources](Essential-UI-Kit-images/Resources.png) -7. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio. +7. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. ## Run the UI template item diff --git a/Extension/Xamarin-Extension/Overview.md b/Extension/Xamarin-Extension/Overview.md index 5b241060..b7b47a29 100644 --- a/Extension/Xamarin-Extension/Overview.md +++ b/Extension/Xamarin-Extension/Overview.md @@ -1,34 +1,34 @@ --- layout: post title: Xamarin Extension | Extension | Syncfusion -description: The Syncfusion Xamarin Extensions provide quick access to create or configure the Syncfusion Xamarin projects +description: The Syncfusion Xamarin Extensions provide quick access to create or configure the Syncfusion Xamarin projects platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- # Xamarin Extension Overview -The Syncfusion® Xamarin Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio. +The Syncfusion® Xamarin Visual Studio Extensions can be accessed through the Syncfusion® Menu to create and configure the project with Syncfusion® references in Visual Studio. -I> The Syncfusion® Xamarin menu option is available from v17.1.0.32. +I> The Syncfusion® Xamarin menu option is available from v17.1.0.32. -The Syncfusion® provides the following extension supports in Visual Studio: +The Syncfusion® provides the following extension supports in Visual Studio: -1. [Syncfusion Xamarin Project Template](https://help.syncfusion.com/extension/xamarin-extension/create-project): Create the Syncfusion® Xamarin application by adding the required Syncfusion® NuGet based on the control chosen. -2. [Essential UI Kit](https://help.syncfusion.com/extension/xamarin-extension/essential-ui-kit#template-selection-and-naming): Add the predefined Syncfusion® XAML templates in Xamarin.Form and install the required Syncfusion® NuGet packages. +1. [Syncfusion® Xamarin Project Template](https://help.syncfusion.com/extension/xamarin-extension/create-project): Create the Syncfusion® Xamarin application by adding the required Syncfusion® NuGet based on the control chosen. +2. [Essential® UI Kit](https://help.syncfusion.com/extension/xamarin-extension/essential-ui-kit#template-selection-and-naming): Add the predefined Syncfusion® XAML templates in Xamarin.Form and install the required Syncfusion® NuGet packages. N> Xamarin Item Template is available only in marketplace. -3. [Toolbox](https://help.syncfusion.com/extension/xamarin-extension/toolbox): Add the Syncfusion® Xamarin components in Xamarin.Forms designer. +3. [Toolbox](https://help.syncfusion.com/extension/xamarin-extension/toolbox): Add the Syncfusion® Xamarin components in Xamarin.Forms designer. **No project selected in Visual Studio** -![Syncfusion Menu when No project selected in Visual Studio](Overview_images/Syncfusion_Menu_OverView1.png) +![Syncfusion® Menu when No project selected in Visual Studio](Overview_images/Syncfusion_Menu_OverView1.png) -**Selected Microsoft/Syncfusion Xamarin (Xamarin.Forms) application in Visual Studio** +**Selected Microsoft/Syncfusion® Xamarin (Xamarin.Forms) application in Visual Studio** -![Syncfusion Menu when Selected Microsoft/Syncfusion Xamarin in Visual Studio](Overview_images/Syncfusion_Menu_OverView2.png) +![Syncfusion® Menu when Selected Microsoft/Syncfusion® Xamarin in Visual Studio](Overview_images/Syncfusion_Menu_OverView2.png) -N> From Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. +N> From Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. diff --git a/Extension/Xamarin-Extension/Syncfusion-Notifications.md b/Extension/Xamarin-Extension/Syncfusion-Notifications.md index cecedf07..9ecc22fb 100644 --- a/Extension/Xamarin-Extension/Syncfusion-Notifications.md +++ b/Extension/Xamarin-Extension/Syncfusion-Notifications.md @@ -1,49 +1,49 @@ --- layout: post title: Notifications | Xamarin | Syncfusion -description: For displaying the notifications about trial and newer version update information for Syncfusion applications. +description: For displaying the notifications about trial and newer version update information for Syncfusion applications. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Notifications +# Syncfusion® Notifications -Syncfusion enhances the user experience in Xamarin applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. +Syncfusion® enhances the user experience in Xamarin applications through notification messages. These notifications cover various aspects, including alerts for trial applications when utilizing Syncfusion® trial assemblies, updates regarding the availability of the latest Syncfusion® NuGet package, and notifications regarding newer releases of Essential Studio®. By keeping users informed, Syncfusion® ensures that developers stay updated with Syncfusion® latest features and enhancements. -N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. +N> The Syncfusion® Notification feature is available from Essential Studio® v22.1.34. ## Notification Configuration -The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. +The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle. -It can be accessed by clicking **Tools -> Options -> Syncfusion® -> Xamarin** +It can be accessed by clicking **Tools -> Options -> Syncfusion® -> Xamarin** ![Option Page](images/xamarin-optionPage.png) ## Notification Types -**1. Syncfusion® Trial Application Notification** +**1. Syncfusion® Trial Application Notification** -When you utilize Syncfusion® trial assemblies in your Xamarin application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion. +When you utilize Syncfusion® trial assemblies in your Xamarin application, you will receive a notification stating, **This application uses a trial Syncfusion® license.** This notification encourages you to obtain a valid license key, enabling you to fully explore and experience the extensive features and capabilities offered by Syncfusion®. ![Trial Notification](images/xamarin-trial.png) -**2. Newer Syncfusion® NuGet Package Notification** +**2. Newer Syncfusion® NuGet Package Notification** -If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. +If you have installed lower versions of Syncfusion® NuGet packages in your application, you will be notified about the availability of higher versions of Syncfusion® NuGet packages on nuget.org. This empowers you to easily identify opportunities to upgrade and gain access to new features, performance enhancements, and bug fixes. ![NuGet Notification](images/xamarin-nuget.png) -**3. Newer Essential Studio® Build Notification** +**3. Newer Essential Studio® Build Notification** -If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio Xamarin,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your Xamarin development projects. +If you use older versions of Syncfusion® assemblies or NuGet packages from **Essential Studio® Xamarin,** Syncfusion® will notify you about new releases for the latest Essential Studio® build. Updating to the newest version ensures access to recent features, enhancements, and important updates, maximizing the capabilities of Syncfusion® in your Xamarin development projects. ![Build Notification](images/xamarin-build.png) **4. Invalid License Key Notification** -If you have mistakenly used an incorrect license key or used a license from another version or platform in your Xamarin application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. +If you have mistakenly used an incorrect license key or used a license from another version or platform in your Xamarin application, Syncfusion® will display a notification message stating, **The provided Syncfusion® license key is invalid.** This message serves as a reminder to obtain a valid license key and ensure proper licensing for Syncfusion® components. ![Invalid Notification](images/xamarin-invalid.png) diff --git a/Extension/Xamarin-Extension/Toolbox.md b/Extension/Xamarin-Extension/Toolbox.md index 30366279..576f0a7b 100644 --- a/Extension/Xamarin-Extension/Toolbox.md +++ b/Extension/Xamarin-Extension/Toolbox.md @@ -1,49 +1,49 @@ --- layout: post title: Toolbox Control | xamarin | Syncfusion -description: Syncfusion Xamarin Toolbox to add the Syncfusion Xamarin (Xamarin.Forms) controls in your project without coding in the Visual Studio designer. +description: Syncfusion Xamarin Toolbox to add the Syncfusion Xamarin (Xamarin.Forms) controls in your project without coding in the Visual Studio designer. platform: extension -control: Syncfusion Extensions +control: Syncfusion Extensions documentation: ug --- -# Syncfusion® Xamarin Toolbox +# Syncfusion® Xamarin Toolbox -Syncfusion provides a Syncfusion® **Visual Studio** Toolbox for the Xamarin platform to include the Syncfusion® Xamarin (Xamarin.Forms) components in Xamarin application. It supports from Visual Studio 2017. The Syncfusion® Xamarin toolbox allows you to add a Syncfusion® Xamarin component code to the application effortlessly at the appropriate place in the XAML design file. +Syncfusion® provides a Syncfusion® **Visual Studio** Toolbox for the Xamarin platform to include the Syncfusion® Xamarin (Xamarin.Forms) components in Xamarin application. It supports from Visual Studio 2017. The Syncfusion® Xamarin toolbox allows you to add a Syncfusion® Xamarin component code to the application effortlessly at the appropriate place in the XAML design file. -I> The Syncfusion® Xamarin Toolbox is available from Essential Studio® 2018 Volume 2(v16.2.0.41). +I> The Syncfusion® Xamarin Toolbox is available from Essential Studio® 2018 Volume 2(v16.2.0.41). -> Check whether the **Xamarin Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by navigating to **Tools -> Extensions and Updates -> Installed** for Visual Studio 2017, and **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 by navigating to **Extensions -> Manage Extensions -> Installed**. If this extension not installed, please install the extension by follow the steps from the [download and installation](download-and-installation) help topic. +> Check whether the **Xamarin Extensions - Syncfusion®** are installed or not in Visual Studio Extension Manager by navigating to **Tools -> Extensions and Updates -> Installed** for Visual Studio 2017, and **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 by navigating to **Extensions -> Manage Extensions -> Installed**. If this extension not installed, please install the extension by follow the steps from the [download and installation](download-and-installation) help topic. -## Launching Syncfusion® Xamarin Toolbox from Syncfusion® menu +## Launching Syncfusion® Xamarin Toolbox from Syncfusion® menu **Visual Studio 2019 and later** -To launch the Syncfusion® Toolbox from Visual Studio 2019 and later, click **Extensions** in Visual Studio menu and choose **Syncfusion > Essential Studio® for Xamarin > Launch Toolbox…** +To launch the Syncfusion® Toolbox from Visual Studio 2019 and later, click **Extensions** in Visual Studio menu and choose **Syncfusion® > Essential Studio® for Xamarin > Launch Toolbox…** - ![Syncfusion Xamarin Custom Toolbox via Syncfusion menu](Toolbox_images/Syncfusion_Menu_Toolbox_2019.png) + ![Syncfusion® Xamarin Custom Toolbox via Syncfusion® menu](Toolbox_images/Syncfusion_Menu_Toolbox_2019.png) **Visual Studio 2017** -To launch the Syncfusion® Toolbox from Visual Studio 2017, click **Syncfusion** in Visual Studio menu and choose **Essential Studio for Xamarin > Launch Toolbox...** +To launch the Syncfusion® Toolbox from Visual Studio 2017, click **Syncfusion®** in Visual Studio menu and choose **Essential Studio® for Xamarin > Launch Toolbox...** - ![Syncfusion Xamarin Custom Toolbox via Syncfusion menu](Toolbox_images/Syncfusion_Menu_Toolbox.png) + ![Syncfusion® Xamarin Custom Toolbox via Syncfusion® menu](Toolbox_images/Syncfusion_Menu_Toolbox.png) -## Launching Syncfusion® Xamarin Toolbox from View menu +## Launching Syncfusion® Xamarin Toolbox from View menu -To launch the Visual Studio Toolbox from Visual Studio menu in Visual Studio 2017 and later, click **View > Other Windows > Syncfusion® Toolbox** in Visual Studio. +To launch the Visual Studio Toolbox from Visual Studio menu in Visual Studio 2017 and later, click **View > Other Windows > Syncfusion® Toolbox** in Visual Studio. - ![Syncfusion Xamarin Custom Toolbox menu](Toolbox_images/Toolbox-img1.png) + ![Syncfusion® Xamarin Custom Toolbox menu](Toolbox_images/Toolbox-img1.png) -> You can also find the Syncfusion® Toolbox option by typing "Syncfusion Toolbox" into the Quick Launch search field (top right corner in Visual Studio). +> You can also find the Syncfusion® Toolbox option by typing "Syncfusion® Toolbox" into the Quick Launch search field (top right corner in Visual Studio). - ![Syncfusion Xamarin Custom Toolbox menu](Toolbox_images/quick-launchToolbox-img.png) + ![Syncfusion® Xamarin Custom Toolbox menu](Toolbox_images/quick-launchToolbox-img.png) -## Render Syncfusion® components +## Render Syncfusion® components -1. When you click the Syncfusion® Toolbox window, the Syncfusion® Toolbox wizard is launched, and Syncfusion® components are enabled once you access your application's designer page (XAML). Syncfusion® components will not appear until open the appropriate design (XAML) file from the Xamarin shared/.NET Standard/PCL project. The rendering of the Syncfusion® Xamarin components is made as simple as possible. All you need to do simply dragging and dropping the Syncfusion® Xamarin component from the Syncfusion® toolbox into the designer. The selected component's code snippet and namespace will be added to the designer page(XAML) and the required Syncfusion® Xamarin NuGet packages will be installed. +1. When you click the Syncfusion® Toolbox window, the Syncfusion® Toolbox wizard is launched, and Syncfusion® components are enabled once you access your application's designer page (XAML). Syncfusion® components will not appear until open the appropriate design (XAML) file from the Xamarin shared/.NET Standard/PCL project. The rendering of the Syncfusion® Xamarin components is made as simple as possible. All you need to do simply dragging and dropping the Syncfusion® Xamarin component from the Syncfusion® toolbox into the designer. The selected component's code snippet and namespace will be added to the designer page(XAML) and the required Syncfusion® Xamarin NuGet packages will be installed. - ![Syncfusion Xamarin Toolbox wizard](Toolbox_images/toolbox-gif.gif) + ![Syncfusion® Xamarin Toolbox wizard](Toolbox_images/toolbox-gif.gif) -2. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio. \ No newline at end of file +2. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file From 9858b5cbff66c7ca78c1b969cdb81852e2ef6ac2 Mon Sep 17 00:00:00 2001 From: Kesavaraman Date: Wed, 22 Jan 2025 18:47:15 +0530 Subject: [PATCH 2/7] Trademark Removed --- .../ASPNET-Extension/Check-for-Updates.md | 4 +-- Extension/ASPNET-Extension/Overview.md | 6 ++-- .../ASPNET-Extension/Project-Conversion.md | 16 ++++----- .../ASPNET-Extension/Project-Migration.md | 8 ++--- Extension/ASPNET-Extension/Sample-Creator.md | 24 ++++++------- .../Syncfusion-Project-Templates.md | 20 +++++------ .../ASPNET-Extension/Toolbox-Configuration.md | 2 +- Extension/ASPNET-Extension/Troubleshooting.md | 34 +++++++++--------- .../Command-Line-installation.md | 2 +- .../Download-ASPNET-MVC-Extension.md | 4 +-- Extension/ASPNET-MVC-Extension/Overview.md | 6 ++-- .../Project-Conversion.md | 36 +++++++++---------- .../ASPNET-MVC-Extension/Project-Migration.md | 8 ++--- .../ASPNET-MVC-Extension/Sample-Creator.md | 20 +++++------ .../Step-by-Step-Installation.md | 12 +++---- .../Syncfusion-Project-Templates.md | 22 ++++++------ Extension/ASPNETCore-Extension/Overview.md | 6 ++-- .../Project-Conversion.md | 20 +++++------ .../ASPNETCore-Extension/Project-Migration.md | 8 ++--- .../ASPNETCore-Extension/Sample-Creator.md | 16 ++++----- .../Syncfusion-Project-Templates.md | 12 +++---- .../Overview.md | 2 +- .../Project-Conversion.md | 4 +-- .../Project-Migration.md | 2 +- .../Sample-Creator.md | 2 +- .../Scaffolding.md | 8 ++--- .../Syncfusion-Project-Templates.md | 8 ++--- .../Visual-Studio-Code/code-snippet.md | 2 +- .../Visual-Studio/scaffolding.md | 2 +- ...t-message-in-Syncfusion-Xamarin-Toolbox.md | 4 +-- ...the-new-project-window-of-Visual-Studio.md | 10 +++--- ...al-Studio-How-can-to-get-them-installed.md | 6 ++-- 32 files changed, 168 insertions(+), 168 deletions(-) diff --git a/Extension/ASPNET-Extension/Check-for-Updates.md b/Extension/ASPNET-Extension/Check-for-Updates.md index e6c063cf..3b2fa31b 100644 --- a/Extension/ASPNET-Extension/Check-for-Updates.md +++ b/Extension/ASPNET-Extension/Check-for-Updates.md @@ -17,12 +17,12 @@ You can check the availability of updates in Visual Studio and then install the 1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu - ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) + ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. 2. When an update is available, the Update dialog box appears. - ![Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) + ![Syncfusion check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) 3. Syncfusion® Essential Studio® can be downloaded from the Syncfusion® website by clicking the **Download** button. diff --git a/Extension/ASPNET-Extension/Overview.md b/Extension/ASPNET-Extension/Overview.md index 665e6321..5cd7ce04 100644 --- a/Extension/ASPNET-Extension/Overview.md +++ b/Extension/ASPNET-Extension/Overview.md @@ -26,15 +26,15 @@ The Syncfusion® provides the following extension supports in Visual Studio: **No project selected in Visual Studio** -![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Microsoft ASP.NET WebSite or Web application in Visual Studio** -![Syncfusion® Menu when Selected Microsoft ASP.NET application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) +![Syncfusion Menu when Selected Microsoft ASP.NET application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) **Selected Syncfusion® ASP.NET (Essential® JS1) WebSite or Web application in Visual Studio** -![Syncfusion® Menu when Selected Synfusion® ASP.NET EJ1 application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) +![Syncfusion Menu when Selected Synfusion ASP.NET EJ1 application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. diff --git a/Extension/ASPNET-Extension/Project-Conversion.md b/Extension/ASPNET-Extension/Project-Conversion.md index e5fa7167..5962cc8e 100644 --- a/Extension/ASPNET-Extension/Project-Conversion.md +++ b/Extension/ASPNET-Extension/Project-Conversion.md @@ -24,18 +24,18 @@ The following steps will assist you to use the Syncfusion® Project conversion i **Option 1** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Convert to Syncfusion® ASP.NET Application…** in **Visual Studio**. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Conversion via Syncfusion® menu](Convert-Project_images/Syncfusion_Menu_Project_Conversion1.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project Conversion via Syncfusion menu](Convert-Project_images/Syncfusion_Menu_Project_Conversion1.png) N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2** Right-click the Project from Solution Explorer, select **Syncfusion® Web (Essential® JS 1)**, and choose the **Convert to Syncfusion® ASP.NET (Essential® JS 1) Application...** Refer to the following screenshot for more information. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Conversion add-in](Convert-Project_images/Project-Conversion-img1.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project Conversion add-in](Convert-Project_images/Project-Conversion-img1.png) 3. The Project Conversion Wizard appears, allowing you to configure the project. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Conversion wizard](Convert-Project_images/Project-Conversion-img2.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project Conversion wizard](Convert-Project_images/Project-Conversion-img2.png) The following configurations are used in the Project Conversion wizard: @@ -49,7 +49,7 @@ The following steps will assist you to use the Syncfusion® Project conversion i **Choose CDN Support:** The project's master page will be updated based on the required Syncfusion® CDN links. - ![Choose CDN Support to refer the Syncfusion® assets from CDN for ASP.NET Web Forms project](Convert-Project_images/Project-Conversion-img6.jpeg) + ![Choose CDN Support to refer the Syncfusion assets from CDN for ASP.NET Web Forms project](Convert-Project_images/Project-Conversion-img6.jpeg) **Copy Global Resources:** If you select the Copy Global Resources option, the Syncfusion® localization culture files will be shipped to the project from the Installed Location. @@ -63,14 +63,14 @@ The following steps will assist you to use the Syncfusion® Project conversion i 4. When you click the **Convert** button, the **Project Backup** dialog will appear. If you click **Yes** in the dialog, it will backup the current project before converting it to a Syncfusion® project. If you choose **No**, the project will be converted to a Syncfusion® project without a backup. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Conversion backup dialog](Convert-Project_images/Project-Conversion-img9.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project Conversion backup dialog](Convert-Project_images/Project-Conversion-img9.png) 5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project. - ![Reference assemblies use of Syncfusion® Essential® JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img10.png) + ![Reference assemblies use of Syncfusion Essential JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img10.png) - ![Scripts and CSS for Syncfusion® Essential® JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img11.png) + ![Scripts and CSS for Syncfusion Essential JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img11.png) - ![Web.config assembly reference of Syncfusion® Essential® JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img12.png) + ![Web.config assembly reference of Syncfusion Essential JS 1 ASP.NET Web Forms Project](Convert-Project_images/Project-Conversion-img12.png) 6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/ASPNET-Extension/Project-Migration.md b/Extension/ASPNET-Extension/Project-Migration.md index a29e6b91..0a3c289a 100644 --- a/Extension/ASPNET-Extension/Project-Migration.md +++ b/Extension/ASPNET-Extension/Project-Migration.md @@ -22,18 +22,18 @@ To migrate you’re existing Syncfusion® ASP.NET application, follow the steps **Option 1** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Migrate Project…** in **Visual Studio**. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Migration via Syncfusion® menu](Upgrade-Project_images/Syncfusion_Menu_Project_Migration1.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project Migration via Syncfusion menu](Upgrade-Project_images/Syncfusion_Menu_Project_Migration1.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2** Right-click the **Syncfusion® ASP.NET Application** from Solution Explorer and select **Syncfusion® Web (Essential® JS 1)**. Choose **Migrate the Essential® JS 1 Project to Another version…** - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Migration add-in](Upgrade-Project_images/Project-Migration_img1.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project Migration add-in](Upgrade-Project_images/Project-Migration_img1.png) 2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Migration wizard](Upgrade-Project_images/Project-Migration_img2.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project Migration wizard](Upgrade-Project_images/Project-Migration_img2.png) 3. The **Project Migration** window allows you to configure the following options: @@ -45,7 +45,7 @@ To migrate you’re existing Syncfusion® ASP.NET application, follow the steps 4. Click the **Migrate** Button. The **Project Backup** dialogue box appears. If you select **Yes** in the dialog, it will backup the current project before migrating the Syncfusion® project. If you select **No**, the project will be migrated to the required Syncfusion® version without a backup. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project Migration backup dialog](Upgrade-Project_images/Project-Migration_img4.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project Migration backup dialog](Upgrade-Project_images/Project-Migration_img4.png) 5. The Syncfusion® Reference Assemblies, Scripts, and CSS, Web. Config entries in the project are updated to the corresponding version. diff --git a/Extension/ASPNET-Extension/Sample-Creator.md b/Extension/ASPNET-Extension/Sample-Creator.md index e719f178..edcadbff 100644 --- a/Extension/ASPNET-Extension/Sample-Creator.md +++ b/Extension/ASPNET-Extension/Sample-Creator.md @@ -18,26 +18,26 @@ To create the Syncfusion® ASP.NET (Essential® JS 1) Application using the Samp **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Launch Sample Creator…** in **Visual Studio**. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms control panel to launch Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/Syncfusion_Menu_Sample_Creator.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms control panel to launch Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/Syncfusion_Menu_Sample_Creator.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2:** Launch the Syncfusion® ASP.NET (Essential® JS 1) Control Panel. To run the ASP.NET (Essential® JS 1) Sample Creator, click the Sample Creator button. More information can be found in the screenshot below. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms control panel to launch Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/SampleCreator-img1.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms control panel to launch Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/SampleCreator-img1.png) -2. The Syncfusion® components and their features are listed in the ASP.NET (Essential® JS 1) Sample Creator. +2. The Syncfusion® components and their features are listed in the ASP.NET (Essential JS 1) Sample Creator. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator wizard](Create-Samples_images/SampleCreator-img2.png) + ![Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator wizard](Create-Samples_images/SampleCreator-img2.png) **Components Selection:** Choose the required components. The components are grouped with Syncfusion® products, and the components are grouped by product. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator controls selection](Create-Samples_images/SampleCreator-img3.jpeg) + ![Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator controls selection](Create-Samples_images/SampleCreator-img3.jpeg) **Feature Selection:** Based on the components, the feature is enabled to choose the features of the corresponding components. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator features selection](Create-Samples_images/SampleCreator-img4.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator features selection](Create-Samples_images/SampleCreator-img4.jpeg) **Project Configuration** @@ -55,29 +55,29 @@ To create the Syncfusion® ASP.NET (Essential® JS 1) Application using the Samp * **Theme Selection:** Choose the required theme. This section shows the controls preview before creating the Syncfusion® project. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator project configuration selection](Create-Samples_images/SampleCreator-img5.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator project configuration selection](Create-Samples_images/SampleCreator-img5.png) 2. Click the **Create** button. After you've finished creating the project, open it by clicking **Yes**. If you click **No**, the project's corresponding location will be opened. For more information, see the screenshot below. - ![The project successfully created using Syncfusion® Essential® JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/SampleCreator-img6.png) + ![The project successfully created using Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator](Create-Samples_images/SampleCreator-img6.png) 3. The new Syncfusion® ASP.NET (Essential® JS 1) project is created with the resources. * Added the required Controllers and View files in the project. - ![Required ASPX and Class files for Syncfusion® Essential® JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img7.png) + ![Required ASPX and Class files for Syncfusion Essential JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img7.png) * Under Project Reference, the necessary Syncfusion® assemblies are added for selected components. - ![Required reference assemblies for Syncfusion® Essential® JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img8.png) + ![Required reference assemblies for Syncfusion Essential JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img8.png) * Syncfusion® ASP.NET (Essential® JS 1) scripts and theme files were included. - ![Required Scripts and Themes files for Syncfusion® Essential® JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img9.png) + ![Required Scripts and Themes files for Syncfusion Essential JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img9.png) * Configure the Web.Config file by adding the Syncfusion® reference assemblies, namespaces and controls. - ![Required Web.config assembliesa and namespaces entry for Syncfusion® Essential® JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img10.png) + ![Required Web.config assembliesa and namespaces entry for Syncfusion Essential JS 1 ASP.NET Web Forms controls](Create-Samples_images/SampleCreator-img10.png) diff --git a/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md index 6b35ea97..4506a271 100644 --- a/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md +++ b/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md @@ -22,14 +22,14 @@ To create the **Syncfusion® ASP.NET (Essential® JS 1) Application** using the **Option 1** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Create New Syncfusion® ASPNET Web Forms Project…** in **Visual Studio**. - ![Choose Syncfusion® ASP.NET Web Application or Syncfusion® ASP.NET Web Site from Visual Studio new project dialog via Syncfusion® menu](Create-Project_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion ASP.NET Web Application or Syncfusion ASP.NET Web Site from Visual Studio new project dialog via Syncfusion menu](Create-Project_images/Syncfusion_Menu_ProjectTemplate.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2** Choose **File > New > Project** and navigate to **Syncfusion > Web > Syncfusion® ASP.NET Web Forms Application** in **Visual Studio**. - ![Choose Syncfusion® ASP.NET Web Forms Application from Visual Studio new project dialog](Create-Project_images/Syncfusion-Project-Templates-img1.png) + ![Choose Syncfusion ASP.NET Web Forms Application from Visual Studio new project dialog](Create-Project_images/Syncfusion-Project-Templates-img1.png) 2. Name the **project**, select the destination location, and configure the project's .NET Framework, then click **OK**. The Project Configuration Wizard is displayed. @@ -37,7 +37,7 @@ To create the **Syncfusion® ASP.NET (Essential® JS 1) Application** using the 3. Using the following Project Configuration window, select the options to configure the Syncfusion® ASP.NET Web Forms Application. - ![Syncfusion® Essential® JS 1 ASP.NET Web Forms Project configuration wizard](Create-Project_images/Syncfusion-Project-Templates-img2.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Project configuration wizard](Create-Project_images/Syncfusion-Project-Templates-img2.png) **Project Configurations** @@ -59,7 +59,7 @@ To create the **Syncfusion® ASP.NET (Essential® JS 1) Application** using the **Assets From:** Choose the Syncfusion® Essential® JS assets to be added to the ASP.NET Web Forms Project from the NuGet, CDN, or Installed Location. - ![Choose the Syncfusion® Essential® JS assets to ASP.NET Web Forms Project, either NuGet, CDN or Installed Location](Create-Project_images/Syncfusion-Project-Templates-img7.png) + ![Choose the Syncfusion Essential JS assets to ASP.NET Web Forms Project, either NuGet, CDN or Installed Location](Create-Project_images/Syncfusion-Project-Templates-img7.png) **Installed Version** Choose the version of the project that needs to be created. @@ -67,22 +67,22 @@ To create the **Syncfusion® ASP.NET (Essential® JS 1) Application** using the 4. Select the components, Assemblies, and Scripts that should be added to the project, and then click the Create button. The Syncfusion® ASP.NET Web Forms project will be created. - ![Syncfusion® Essential® ASP.NET Web Feature selection](Create-Project_images/Syncfusion-Project-Templates-img9.png) + ![Syncfusion Essential ASP.NET Web Feature selection](Create-Project_images/Syncfusion-Project-Templates-img9.png) - ![Syncfusion® Essential® ASP.NET Web Feature selection](Create-Project_images/Syncfusion-Project-Templates-img14.PNG) + ![Syncfusion Essential ASP.NET Web Feature selection](Create-Project_images/Syncfusion-Project-Templates-img14.PNG) 5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project. - ![References of Syncfusion® Essential® JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img10.png) + ![References of Syncfusion Essential JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img10.png) - ![Scripts and Themes of Syncfusion® Essential® JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img11.png) + ![Scripts and Themes of Syncfusion Essential JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img11.png) - ![Web.config references of Syncfusion® Essential® JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img12.png) + ![Web.config references of Syncfusion Essential JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img12.png) 6.Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration information message box for Syncfusion® Essential® JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img13.jpeg) + ![Syncfusion license registration information message box for Syncfusion Essential JS 1 ASP.NET Web Forms project](Create-Project_images/Syncfusion-Project-Templates-img13.jpeg) diff --git a/Extension/ASPNET-Extension/Toolbox-Configuration.md b/Extension/ASPNET-Extension/Toolbox-Configuration.md index 20934e81..d943e8e3 100644 --- a/Extension/ASPNET-Extension/Toolbox-Configuration.md +++ b/Extension/ASPNET-Extension/Toolbox-Configuration.md @@ -27,7 +27,7 @@ To add the Syncfusion® ASP.NET Web Forms components via the Syncfusion® Toolbo **Option 2:** Click **Syncfusion® menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Toolbox Configuration...** in **Visual Studio** - ![Toolbox Installer via Syncfusion® menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) + ![Toolbox Installer via Syncfusion menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. diff --git a/Extension/ASPNET-Extension/Troubleshooting.md b/Extension/ASPNET-Extension/Troubleshooting.md index da0562ec..b4c4f6ff 100644 --- a/Extension/ASPNET-Extension/Troubleshooting.md +++ b/Extension/ASPNET-Extension/Troubleshooting.md @@ -26,14 +26,14 @@ The steps below will assist you in using the Syncfusion® Troubleshooter by Visu **Option 1** Open an existing Syncfusion® ASP.NET Web Forms Application, Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Troubleshoot…** in Visual Studio. - ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) + ![Syncfusion Troubleshooter via Syncfusion menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2** Right-click the Project file in Solution Explorer, then select the command **Syncfusion® Troubleshooter…** - ![Syncfusion® Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.png) + ![Syncfusion Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.png) 2. Now, analyze the project, and if any issues are discovered, it will report the project configuration issues of Syncfusion® components in the Troubleshooter dialogue. If the project has no configuration issues, the dialogue box will indicate that no configuration changes are required in the following areas: @@ -97,7 +97,7 @@ The Syncfusion® Troubleshooter handles the following NuGet package issues in Sy **For Instance:** If you have multiple versions of the Syncfusion® Web platform packages installed (v16.4.0.54 and v17.1.0.38), the Syncfusion® Troubleshooter will display Syncfusion® package version mismatch. - ![Syncfusion® NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) + ![Syncfusion NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) 2. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. @@ -115,17 +115,17 @@ The Syncfusion® Troubleshooter handles with Web.config entry-related issues in **For Instance:** If the “Syncfusion.EJ.Pivot” assembly (v17.1450.0.38) is mentioned in the project, but the “Syncfusion.EJ.Pivot” assembly entry version (v16.4450.0.54) is mentioned in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® assembly entry version. - ![Syncfusion® Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.png) + ![Syncfusion Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.png) 2. Syncfusion® assembly entry has multiple versions and is duplicated. When a Syncfusion® assembly entry is presented in Web.config that is not referred to in the project, or when multiple Syncfusion® assembly entries are presented in Web.config for the same Syncfusion® assembly, Syncfusion® Troubleshooter will display the duplicate assembly entry. **For Instance:** If the project contains a “Syncfusion.EJ.Web” assembly (v17.1450.0.38) entry in the Web.config file, but the “Syncfusion.EJ.Web” assembly is not referred to in the project. Duplicate assembly entry will be displayed by Syncfusion® Troubleshooter. - ![Duplicate Syncfusion® reference assembly entry issue shown in Troubleshooter wizard ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) + ![Duplicate Syncfusion reference assembly entry issue shown in Troubleshooter wizard ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) **For Instance:** If a project contains multiple “Syncfusion.EJ.Web” assembly entries (v16.4460.0.54 && v17.1460.0.38) with mismatched assembly version/.NET Framework version in Web.config, Syncfusion® Troubleshooter will display the Duplicate assembly entry and Multiple Syncfusion® assembly entries. - ![Multiple version Syncfusion® reference assembly entry issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) + ![Multiple version Syncfusion reference assembly entry issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) 3. The version of the namespace entry was mismatched. If any Namespace entry version (assembly version) in ASP.NET Web Application is mismatched with the corresponding referred assembly version, Syncfusion® Troubleshooter will display Namespace entry version mismatched. @@ -137,7 +137,7 @@ The Syncfusion® Troubleshooter handles with Web.config entry-related issues in **For Instance:** If the “Syncfusion.EJ.” assembly (v17.1450.0.38) is mentioned in the project, but the “Syncfusion.JavaScript.ImageHandler” HTTP/Server handler entry version (v16.4450.0.54) is specified in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® HTTP/Server handler entry version. - ![Syncfusion® HTTP/Server handler entry mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.png) + ![Syncfusion HTTP/Server handler entry mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.png) ### Toolbox Configuration Issues @@ -147,13 +147,13 @@ The Syncfusion® Troubleshooter handles the Toolbox Configuration issues listed **For Instance:** The .NET Framework version of the project is 4.5, and Syncfusion® Toolbox is not installed. 4.6 framework assemblies only in the corresponding Visual Studio, the Syncfusion® Troubleshooter will display Syncfusion® Toolbox framework version mismatch. - ![Syncfusion® Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.png) + ![Syncfusion Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.png) 2. If the configured version of Syncfusion® Toolbox differs from the most recent Syncfusion® assembly reference version or NuGet package version in the same project, the Syncfusion® Troubleshooter will indicate that the Syncfusion® Toolbox version is mismatch. **For Instance:** If the most recent Syncfusion® assembly reference version is v17.1.0.38 but the Toolbox assemblies are configured with v17.1.0.32, the Syncfusion Troubleshooter will report Syncfusion® Toolbox version mismatch. - ![Syncfusion® Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.png) + ![Syncfusion Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.png) ### Script file issues @@ -163,36 +163,36 @@ The Syncfusion® Troubleshooter handles the following Script file issues in Sync **For Instance:** If Syncfusion® assemblies (v17.1450.0.38) and Syncfusion® script file (v16.4.0.54) are referenced in the project. The Syncfusion® Troubleshooter will display a Syncfusion® script file version (v16.4.0.54) that is incompatible with the project's/package version of Syncfusion® (v17.1.0.38). - ![Syncfusion® script file version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img16.png) + ![Syncfusion script file version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img16.png) **For Instance:** If Syncfusion® assemblies (v17.1450.0.38) are referred to in the project, but Syncfusion® script file version (v16.4.0.54) is referred to in View files when script files are referred to via a CDN link. The Syncfusion® Troubleshooter will report that the Syncfusion® script file version (v16.4.0.54) is incompatible with the project's Syncfusion® assembly/package version (v17.1.0.38) from CDN. - ![Syncfusion® script file version mismatched issue based on CDN link shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img17.png) + ![Syncfusion script file version mismatched issue based on CDN link shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img17.png) 2. Syncfusion® script files that are duplicates. When a Syncfusion® script file is presented in the project location, which is referred to in View files by CDN link, or when Syncfusion® script files are presented in multiple locations in the same project, Syncfusion® Troubleshooter will display duplicate script files. **For Instance:** If the project has a “ej.web.all.min.js” script file entry in the View file and a “ej.web.all.min.js” script file in the project location (Scripts\ej), the Syncfusion® Troubleshooter will show duplicate Syncfusion® script files presented in Scripts\ej due to this script file being referred from CDN. - ![Syncfusion® script file duplicate issue by CDN with local script](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img18.png) + ![Syncfusion script file duplicate issue by CDN with local script](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img18.png) **For Instance:** If a project has the “ej.web.all.min.js” script file available in multiple project locations ("\Scripts\ej" and "\Scripts\"), the Syncfusion® Troubleshooter will display Duplicate Syncfusion® script files in Scripts. - ![Syncfusion® script file duplicate issue by mulitple location ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img19.png) + ![Syncfusion script file duplicate issue by mulitple location ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img19.png) ## Apply the solution 1. Check the corresponding check box of the issue to be resolved after loading the Syncfusion® Troubleshooter dialog. Then, check “Fix Issue(s)” button. - ![Syncfusion® Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img20.png) + ![Syncfusion Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img20.png) 2. A dialog appears, prompting you to create a backup of the project before proceeding with the troubleshooting process. Click the "Yes" button if you need to backup the project before troubleshooting. - ![Syncfusion® Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img21.jpeg) + ![Syncfusion Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img21.jpeg) 3. Wait a moment while the Syncfusion® Troubleshooter resolves the issues you selected. When the troubleshooting process is finished, a message will appear in the Visual Studio status bar that says, "Troubleshooting process completed successfully." - ![Syncfusion® Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img22.jpeg) + ![Syncfusion Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img22.jpeg) 4. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img23.jpeg) \ No newline at end of file + ![Syncfusion license registration required information dialog in Syncfusion Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img23.jpeg) \ No newline at end of file diff --git a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md index 9eb4e55d..4934c3c9 100644 --- a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md +++ b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md @@ -24,6 +24,6 @@ The following steps help you install the Syncfusion® Web Sample Creator setup t Refer to the following screenshot for more information. - ![Command line arguments to install Syncfusion® web sample creator from command prompt](Command-Line-installation_images/Command-Line-installation-img1.png) + ![Command line arguments to install Syncfusion web sample creator from command prompt](Command-Line-installation_images/Command-Line-installation-img1.png) I> The syncfusionessentialextension.exe setup has renamed to syncfusionwebsamplecreator.exe from 2015 Volume 4 release. \ No newline at end of file diff --git a/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md b/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md index 60f50cf3..4301c80e 100644 --- a/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md +++ b/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md @@ -13,7 +13,7 @@ documentation: ug Refer the following screenshot for more information. - ![Download link for Syncfusion® Essential Studio® Web Sample Creator](Download-ASPNET-MVC-Extension_images/Download-ASPNET-MVC-Extension-img1.jpeg) + ![Download link for Syncfusion Essential Studio Web Sample Creator](Download-ASPNET-MVC-Extension_images/Download-ASPNET-MVC-Extension-img1.jpeg) I> It is a prerequisite to have the complete Essential Studio® suite or ASP.NET MVC or ASP.NET MVC (Classic) installed while using Syncfusion® ASP.NET MVC Extension. This is applicable from v.12.1.0.43. @@ -23,7 +23,7 @@ documentation: ug * Navigate to the “ASP.NET MVC” tab available on the left side. * Click the “SAMPLE CREATOR” button. It downloads the corresponding version of Syncfusion® Web Sample Creator setup. When you have already installed the Syncfusion® Web Sample Creator setup then it will launch the “Sample Creator” utility instead of downloading. - ![Syncfusion® Essential studio® control panel to launch the Sample Creator](Download-ASPNET-MVC-Extension_images/Download-ASPNET-MVC-Extension-img2.jpeg) + ![Syncfusion Essential studio control panel to launch the Sample Creator](Download-ASPNET-MVC-Extension_images/Download-ASPNET-MVC-Extension-img2.jpeg) I> The syncfusionessentialextension.exe setup has renamed to syncfusionwebsamplecreator.exe from 2015 Volume 4 release. diff --git a/Extension/ASPNET-MVC-Extension/Overview.md b/Extension/ASPNET-MVC-Extension/Overview.md index 20d63d2c..0a47fb76 100644 --- a/Extension/ASPNET-MVC-Extension/Overview.md +++ b/Extension/ASPNET-MVC-Extension/Overview.md @@ -23,15 +23,15 @@ The Syncfusion® provides the following extension supports in Visual Studio: **No project selected in Visual Studio** -![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Microsoft ASP.NET MVC application in Visual Studio** -![Syncfusion® Menu when Selected Microsoft ASP.NET MVC application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) +![Syncfusion Menu when Selected Microsoft ASP.NET MVC application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) **Selected Syncfusion® ASP.NET MVC (Essential® JS1) application in Visual Studio** -![Syncfusion® Menu when Selected Synfusion ASP.NET MVC EJ1 application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) +![Syncfusion Menu when Selected Synfusion ASP.NET MVC EJ1 application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. diff --git a/Extension/ASPNET-MVC-Extension/Project-Conversion.md b/Extension/ASPNET-MVC-Extension/Project-Conversion.md index 75b1d3af..3f473a29 100644 --- a/Extension/ASPNET-MVC-Extension/Project-Conversion.md +++ b/Extension/ASPNET-MVC-Extension/Project-Conversion.md @@ -42,18 +42,18 @@ The following steps help you use the Syncfusion® Project Conversion in the exis **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Convert to Syncfusion® ASP.NET MVC Application…** in **Visual Studio**. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project Conversion via Synfusion® menu](Convert-into-Syncfusion-MVC-project_images/Syncfusion_Menu_Project_Conversion.png) + ![Syncfusion Essential JS 1 ASP.NET MVC Web Project Conversion via Synfusion menu](Convert-into-Syncfusion-MVC-project_images/Syncfusion_Menu_Project_Conversion.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Right-click the Project from Solution Explorer, select **Syncfusion® Essential® JS 1**, and choose **Convert to Syncfusion® MVC (Essential® JS 1) Application...** Refer to the following screenshot for more information. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project Conversion add-in](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img1.png) + ![Syncfusion Essential JS 1 ASP.NET MVC Web Project Conversion add-in](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img1.png) 3. Project Conversion Wizard opens so that you can configure the project. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project Conversion wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img2.jpg) + ![Syncfusion Essential JS 1 ASP.NET MVC Web Project Conversion wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img2.jpg) The following configurations are used in the Project Conversion Wizard. @@ -77,7 +77,7 @@ The following steps help you use the Syncfusion® Project Conversion in the exis The master page of the project will be updated based on required Syncfusion® CDN links. - ![Choose CDN Support to refer the Syncfusion® assets from CDN for ASP.NET MVC project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img20.jpeg) + ![Choose CDN Support to refer the Syncfusion assets from CDN for ASP.NET MVC project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img20.jpeg) **Choose Copy Global Resources:** @@ -87,20 +87,20 @@ The following steps help you use the Syncfusion® Project Conversion in the exis 4. Choose the required controls from Components section and Click the **Convert** button to convert it into a Syncfusion Project. - ![Select the required components from the Components section in the Syncfusion® ASP.NET MVC Project Conversion Wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img5.jpg) + ![Select the required components from the Components section in the Syncfusion ASP.NET MVC Project Conversion Wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img5.jpg) 5. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before converting it to Syncfusion® project. If click No it will convert the project to Syncfusion® project without backup. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project Conversion backup dialog](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img6.jpg) + ![Syncfusion Essential JS 1 ASP.NET MVC Web Project Conversion backup dialog](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img6.jpg) 6. The required Syncfusion® Reference Assemblies, Scripts and CSS are included in the MVC Project. Refer to the following screenshots for more information. - ![Syncfusion® Essential® JS 1 ASP.NET MVC scripts and themes](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img7.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC scripts and themes](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img7.jpeg) - ![Syncfusion® Essential® JS 1 ASP.NET MVC required reference assemblies](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img8.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC required reference assemblies](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img8.jpeg) - ![Syncfusion® Essential® JS 1 ASP.NET MVC Web.config entries](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img9.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Web.config entries](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img9.jpeg) 6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. @@ -112,11 +112,11 @@ The following steps help you use the Syncfusion® Project Conversion in the exis 2. Right-click on Project and select Syncfusion® VS Extensions and choose the Convert to Syncfusion® MVC (Web) Application. Refer the following screenshot for more information. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project Conversion add-in](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img10.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project Conversion add-in](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img10.jpeg) 3. Project Conversion Wizard opens so that you can configure the project. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project Conversion wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img11.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project Conversion wizard](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img11.jpeg) The following configurations are used in the Project Conversion Wizard. @@ -140,7 +140,7 @@ The following steps help you use the Syncfusion® Project Conversion in the exis The master page of the project will be updated based on required Syncfusion® CDN links. - ![Choose CDN Support to refer the Syncfusion® assets from CDN for ASP.NET MVC Mobile project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img20.jpeg) + ![Choose CDN Support to refer the Syncfusion assets from CDN for ASP.NET MVC Mobile project](Convert-into-Syncfusion-MVC-project_images/Project-Conversion-img20.jpeg) **Choose Copy Global Resources:** @@ -152,13 +152,13 @@ The following steps help you use the Syncfusion® Project Conversion in the exis 5. The required Syncfusion® Reference Assemblies, Scripts and CSS are included in the MVC Project. Refer to the following screenshots for more information. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project required reference assemblies](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img13.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project required reference assemblies](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img13.jpeg) - ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project required scripts](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img14.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project required scripts](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img14.jpeg) - ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile Project required themes](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img15.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Mobile Project required themes](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img15.jpeg) - ![Syncfusion® assembly reference entry in Webconfig file of the Essential® JS 1 ASP.NET MVC Mobile Project](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img16.jpeg) + ![Syncfusion assembly reference entry in Webconfig file of the Essential JS 1 ASP.NET MVC Mobile Project](Convert-into-Syncfusion-MVC-project_images/ProjectConversion-img16.jpeg) ## Rendering Control after Syncfusion® MVC (Web/Mobile) Conversion: @@ -171,9 +171,9 @@ Once you convert your ASP.NET MVC project to Syncfusion® MVC Project, perfor 3. Now, include the Syncfusion® controls to your project. Refer to the following screenshot for more information. - ![Syncfusion® Essential® JS 1 ASP.NET MVC datepicker control snippet](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img18.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC datepicker control snippet](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img18.jpeg) 4. Run the project and the following output is displayed. - ![Syncfusion® Essential® JS 1 ASP.NET MVC datepicker control output](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img19.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC datepicker control output](Convert-into-Syncfusion-MVC-project_images\ProjectConversion-img19.jpeg) diff --git a/Extension/ASPNET-MVC-Extension/Project-Migration.md b/Extension/ASPNET-MVC-Extension/Project-Migration.md index 2399ba3c..2d700dc1 100644 --- a/Extension/ASPNET-MVC-Extension/Project-Migration.md +++ b/Extension/ASPNET-MVC-Extension/Project-Migration.md @@ -40,18 +40,18 @@ The following steps help you migrate from one version to another version of your **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Migrate Project…** in **Visual Studio**. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Project Migration via Syncfusion® menu](Migrate-Syncfusion-Project_images/SyncfusionMenu_ProjectMigration_img.png) + ![Syncfusion Essential JS 1 ASP.NET MVC Project Migration via Syncfusion menu](Migrate-Syncfusion-Project_images/SyncfusionMenu_ProjectMigration_img.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Right-click the **Syncfusion® ASP.NET MVC Application** from Solution Explorer and select **Syncfusion® Essential® JS 1**. Choose **Migrate the Essential® JS 1 Project to Another Version...** - ![Syncfusion® Essential® JS 1 ASP.NET MVC Project Migration add-in](Migrate-Syncfusion-Project_images/ProjectMigration_img.png) + ![Syncfusion Essential JS 1 ASP.NET MVC Project Migration add-in](Migrate-Syncfusion-Project_images/ProjectMigration_img.png) 2. The Project Migration window appears. You can choose the required Syncfusion® version that is installed in the machine that is either Syncfusion® ASP.NET MVC or Syncfusion® ASP.NET MVC (Classic). - ![Syncfusion® Essential® JS 1 ASP.NET MVC Project Migration wizard](Migrate-Syncfusion-Project_images/ProjectMigration-img2.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Project Migration wizard](Migrate-Syncfusion-Project_images/ProjectMigration-img2.jpeg) 3. The Project Migration window allows you to configure the following options: @@ -65,7 +65,7 @@ The following steps help you migrate from one version to another version of your 4. Click the Migrate Button. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before migrate the Syncfusion® project. If click No it will migrate the project to required Syncfusion® version without backup. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Project Migration backup dialog](Migrate-Syncfusion-Project_images/ProjectMigration-img3.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Project Migration backup dialog](Migrate-Syncfusion-Project_images/ProjectMigration-img3.jpeg) 5. The Syncfusion® Reference Assemblies, Scripts and CSS are updated to the corresponding version in the project. diff --git a/Extension/ASPNET-MVC-Extension/Sample-Creator.md b/Extension/ASPNET-MVC-Extension/Sample-Creator.md index 79dd62bf..b7f5530f 100644 --- a/Extension/ASPNET-MVC-Extension/Sample-Creator.md +++ b/Extension/ASPNET-MVC-Extension/Sample-Creator.md @@ -20,30 +20,30 @@ The following steps help you to create the Syncfusion® ASP.NET MVC Project via **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Launch Sample Creator…** in **Visual Studio**. - ![launch the Essential® JS 1 ASP.NET MVC Sample Creator via Syncfusion® menu](Sample-Creator_images/Syncfusion_Menu_SampleCreator.png) + ![launch the Essential JS 1 ASP.NET MVC Sample Creator via Syncfusion menu](Sample-Creator_images/Syncfusion_Menu_SampleCreator.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Launch the Syncfusion® Essential Studio® Dashboard and select the ASP.NET MVC (Essential® JS 1)/ASP.NET MVC (Classic) platform. Select the Sample Creator button to launch the ASP.NET MVC (Essential® JS 1) Sample Creator application. Refer to the following screenshot for more information. - ![Syncfusion® Essential Studio® control panel to launch the Essential® JS 1 ASP.NET MVC Sample Creator](Sample-Creator_images/Sample-Creator-img1.png) + ![Syncfusion Essential Studio control panel to launch the Essential JS 1 ASP.NET MVC Sample Creator](Sample-Creator_images/Sample-Creator-img1.png) 2. Syncfusion® Sample Creator Wizard displaying the **Controls and its Feature Selection** section. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator Wizard](Sample-Creator_images/Sample-Creator-img2.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Sample Creator Wizard](Sample-Creator_images/Sample-Creator-img2.jpeg) ### Controls Selection Listed here are the Syncfusion® ASP.NET MVC controls so you can choose the required controls. And the controls are grouped product wise. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator Controls Selection](Sample-Creator_images/Sample-Creator-img3.png) + ![Syncfusion Essential JS 1 ASP.NET MVC Sample Creator Controls Selection](Sample-Creator_images/Sample-Creator-img3.png) ### Feature Selection Based on the controls, the Feature is enabled to choose the features of the corresponding controls. -![Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator Feature Selection](Sample-Creator_images/Sample-Creator-img4.png) +![Syncfusion Essential JS 1 ASP.NET MVC Sample Creator Feature Selection](Sample-Creator_images/Sample-Creator-img4.png) ### Project Configuration @@ -60,7 +60,7 @@ You can configure the following project details in the Sample Creator. * Location – Choose the target location of your project. * Theme Selection – Choose the required theme. The Theme Preview section shows the controls preview before create the Syncfusion® project. -![Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator Project Configuration section](Sample-Creator_images/Sample-Creator-img6.jpeg) +![Syncfusion Essential JS 1 ASP.NET MVC Sample Creator Project Configuration section](Sample-Creator_images/Sample-Creator-img6.jpeg) When you click the Create button, the new Syncfusion® ASP.NET MVC project is created. The following is added in the project: @@ -70,16 +70,16 @@ When you click the Create button, the new Syncfusion® ASP.NET MVC project is cr * Included the required Syncfusion® ASP.NET MVC scripts and themes files. - ![Required Syncfusion® ASP.NET MVC scripts and themes files added in the project](Sample-Creator_images/Sample-Creator-img8.png) + ![Required Syncfusion ASP.NET MVC scripts and themes files added in the project](Sample-Creator_images/Sample-Creator-img8.png) * The required Syncfusion® assemblies are added for selected controls under Project Reference. - ![Required Syncfusion® assemblies added in the project for the selected controls](Sample-Creator_images/Sample-Creator-img9.png) + ![Required Syncfusion assemblies added in the project for the selected controls](Sample-Creator_images/Sample-Creator-img9.png) * Configure the Web.Config file by adding the Syncfusion® reference assemblies. - ![Required Syncfusion® assemblies configured in Web.config file for the selected controls](Sample-Creator_images/Sample-Creator-img10.jpeg) + ![Required Syncfusion assemblies configured in Web.config file for the selected controls](Sample-Creator_images/Sample-Creator-img10.jpeg) * Once the project is created you can open the project by clicking the Yes button. Refer the following screenshot for more information. - ![The project successfully created using Syncfusion® Essential® JS 1 ASP.NET MVC Sample Creator](Sample-Creator_images/Sample-Creator-img11.jpeg) \ No newline at end of file + ![The project successfully created using Syncfusion Essential JS 1 ASP.NET MVC Sample Creator](Sample-Creator_images/Sample-Creator-img11.jpeg) \ No newline at end of file diff --git a/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md b/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md index d0d23186..14c704a1 100644 --- a/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md +++ b/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md @@ -19,33 +19,33 @@ The following procedure illustrates how to install Syncfusion® Web Sample Creat 1. Double-click the Syncfusion® Web Sample Creator Setup file. The Self-Extractor Wizard opens and extracts the package automatically. - ![Syncfusion® Web Sample Creator Setup Self-Extractor Wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img1.jpeg) + ![Syncfusion Web Sample Creator Setup Self-Extractor Wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img1.jpeg) N> The WinZip Self-Extractor extracts the syncfusionwebsamplecreator_(version).exe dialog, displaying the unzip operation of the package. If complete Essential Studio® suite or any of the required Essential Studio® platform setups are installed, Syncfusion® Web Sample Creator setup will be installed. - ![Syncfusion® Web Sample Creator setup installation wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img2.jpeg) + ![Syncfusion Web Sample Creator setup installation wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img2.jpeg) If complete Essential Studio® suite or any of the required Essential Studio® platform setups are not installed, Syncfusion® Web Sample Creator setup will show the below message. - ![Syncfusion® Web Sample Creator setup validation message](Step-by-Step-Installation_images/Step-by-Step-Installation-img7.jpeg) + ![Syncfusion Web Sample Creator setup validation message](Step-by-Step-Installation_images/Step-by-Step-Installation-img7.jpeg) 2. After reading the terms, click the I accept the terms and conditions check box. 3. Click the Next button. The Installation location window opens. It shows the Syncfusion® Essential Studio® setup installed location. - ![Syncfusion® Web Sample Creator setup install location wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img4.jpeg) + ![Syncfusion Web Sample Creator setup install location wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img4.jpeg) N> It does not allow you to change the install path since its Add on setup for Syncfusion® Essential Studio®. 4. To install it in the displayed default location, click the Install button. - ![Syncfusion® Web Sample Creator setup installation progress](Step-by-Step-Installation_images/Step-by-Step-Installation-img5.jpeg) + ![Syncfusion Web Sample Creator setup installation progress](Step-by-Step-Installation_images/Step-by-Step-Installation-img5.jpeg) 5. The Completed screen will be displayed once the selected package is installed. - ![Syncfusion® Web Sample Creator setup installation completed wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img6.jpeg) + ![Syncfusion Web Sample Creator setup installation completed wizard](Step-by-Step-Installation_images/Step-by-Step-Installation-img6.jpeg) 5. Select the `Run Syncfusion® Control Panel` check box to launch the `Syncfusion® Control Panel` after installed. diff --git a/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md index c4cfd0de..94f45901 100644 --- a/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md +++ b/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md @@ -42,20 +42,20 @@ The following steps help you create the Syncfusion® ASP.NET MVC (Essential® JS **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion® ASP.NET MVC Web Application from Visual Studio new project dialog via Syncfusion® menu](Create-Syncfusion-MVC-Project_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion ASP.NET MVC Web Application from Visual Studio new project dialog via Syncfusion menu](Create-Syncfusion-MVC-Project_images/Syncfusion_Menu_ProjectTemplate.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Choose **File > New > Project** and navigate to **Syncfusion® > Web > Syncfusion® ASP.NET MVC (Essential® JS 1) Application** in **Visual Studio**. - ![Choose Syncfusion® ASP.NET MVC Web Application from Visual Studio new project dialog](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img1.png) + ![Choose Syncfusion ASP.NET MVC Web Application from Visual Studio new project dialog](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img1.png) 2. Name the Project, choose the destination location as required and set the Framework of the project then click OK. The Project Configuration Wizard appears.   3. Choose the options to configure the Syncfusion® ASP.NET MVC Application by using the following Project Configuration window. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Project configuration wizard](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img2.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Web Project configuration wizard](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img2.jpeg) ### Project configurations: @@ -87,7 +87,7 @@ The following steps help you create the Syncfusion® ASP.NET MVC (Essential® JS 5. By choosing the Add Samples option you can add the code examples for your selected controls and its features. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Web Feature selection](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img8.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Web Feature selection](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img8.jpeg) **Select Control:** Choose the control based on your need. @@ -103,7 +103,7 @@ The following steps help you create the Syncfusion® ASP.NET MVC (Essential® JS 7. Syncfusion® references, Scripts, CSS and required Web.config entries are added to the Project. - ![Required Syncfusion® assemblies added in the project created for the selected controls](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img12.jpeg) + ![Required Syncfusion assemblies added in the project created for the selected controls](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img12.jpeg) ![Required scripts and themes added in the project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img13.jpeg) @@ -111,7 +111,7 @@ The following steps help you create the Syncfusion® ASP.NET MVC (Essential® JS 8. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required message box for Syncfusion® Essential® JS 1 ASP.NET MVC web projects](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img29.jpeg) + ![Syncfusion license registration required message box for Syncfusion Essential JS 1 ASP.NET MVC web projects](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img29.jpeg) ## Create Syncfusion® MVC (Mobile) Project @@ -119,12 +119,12 @@ The following steps help you create the Syncfusion® ASP.NET MVC (Mobile) Projec 1. To create a Syncfusion® Project, choose **New Project -> Syncfusion® -> Mobile -> Syncfusion® ASP.NET MVC(Mobile) Application** from Visual Studio. - ![Choose Syncfusion® ASP.NET MVC Mobile Application from Visual Studio new project dialog](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img15.jpeg) + ![Choose Syncfusion ASP.NET MVC Mobile Application from Visual Studio new project dialog](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img15.jpeg) 2. Name the Project, choose the destination location as required and set the Framework of the project then click OK. The Project Configuration Wizard appears.   3. Choose the options to configure the Syncfusion® ASP.NET MVC Application by using the following Project Configuration window. - ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile project configuration wizard](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img16.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Mobile project configuration wizard](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img16.jpeg) ### Project configurations: @@ -154,7 +154,7 @@ The following steps help you create the Syncfusion® ASP.NET MVC (Mobile) Projec 4. Once the Project Configuration Wizard is done, the Syncfusion® MVC Project is created. - ![Required view and controller files added in the Syncfusion® Essential® JS 1 ASP.NET MVC Mobile project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img23.jpeg) + ![Required view and controller files added in the Syncfusion Essential JS 1 ASP.NET MVC Mobile project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img23.jpeg) 5. Syncfusion® references, Scripts, CSS and required Web.config entries are added to the Project. @@ -162,8 +162,8 @@ The following steps help you create the Syncfusion® ASP.NET MVC (Mobile) Projec ![Required themes and scripts added to the project created](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img25.jpeg) - ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile project required scripts](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img26.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Mobile project required scripts](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img26.jpeg) - ![Syncfusion® Essential® JS 1 ASP.NET MVC Mobile project Web.config configuration](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img27.jpeg) + ![Syncfusion Essential JS 1 ASP.NET MVC Mobile project Web.config configuration](Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img27.jpeg) diff --git a/Extension/ASPNETCore-Extension/Overview.md b/Extension/ASPNETCore-Extension/Overview.md index d308eb48..11597029 100644 --- a/Extension/ASPNETCore-Extension/Overview.md +++ b/Extension/ASPNETCore-Extension/Overview.md @@ -25,15 +25,15 @@ The Syncfusion® provides the following extension supports in Visual Studio: **No project selected in Visual Studio** -![Syncfusion® Menu when No project selected in Visual Studio](Overview_images/Syncfusion_Menu_OverView1.png) +![Syncfusion Menu when No project selected in Visual Studio](Overview_images/Syncfusion_Menu_OverView1.png) **Selected Microsoft ASP.NET Core application in Visual Studio** -![Syncfusion® Menu when Selected Microsoft ASP.NET Core application in Visual Studio](Overview_images/Syncfusion_Menu_OverView2.png) +![Syncfusion Menu when Selected Microsoft ASP.NET Core application in Visual Studio](Overview_images/Syncfusion_Menu_OverView2.png) **Selected Syncfusion® ASP.NET Core (Essential® JS1) application in Visual Studio** -![Syncfusion® Menu when Selected Synfusion ASP.NET Core EJ1 application in Visual Studio](Overview_images/Syncfusion_Menu_OverView3.png) +![Syncfusion Menu when Selected Synfusion ASP.NET Core EJ1 application in Visual Studio](Overview_images/Syncfusion_Menu_OverView3.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. diff --git a/Extension/ASPNETCore-Extension/Project-Conversion.md b/Extension/ASPNETCore-Extension/Project-Conversion.md index 631de03b..e7d560f8 100644 --- a/Extension/ASPNETCore-Extension/Project-Conversion.md +++ b/Extension/ASPNETCore-Extension/Project-Conversion.md @@ -26,18 +26,18 @@ The following steps help you to use the Syncfusion® Project Conversion in the e **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Convert to Syncfusion® ASP.NET Core Application…** in **Visual Studio**. - ![Syncfusion® Essential® JS 1 ASP.NET Core Project Conversion via Syncfusion® menu](Project-Conversion_images/Syncfusion_Menu_Project_Conversion.png) + ![Syncfusion Essential JS 1 ASP.NET Core Project Conversion via Syncfusion® menu](Project-Conversion_images/Syncfusion_Menu_Project_Conversion.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Right-click the Project from Solution Explorer, select **Syncfusion® Essential® JS 1**, and then choose **Convert to Syncfusion® ASP.NET Core (Essential® JS 1) Application...** Refer to the following screenshot for more information. - ![Syncfusion® Essential® JS 1 ASP.NET Core Project Conversion add-in](Project-Conversion_images/Project-Conversion_img1.png) + ![Syncfusion Essential JS 1 ASP.NET Core Project Conversion add-in](Project-Conversion_images/Project-Conversion_img1.png) 3. Project Conversion Wizard opens to configure the project. - ![Syncfusion® Essential® JS 1 ASP.NET Core Project Conversion wizard](Project-Conversion_images/Project-Conversion-img2.jpg) + ![Syncfusion Essential JS 1 ASP.NET Core Project Conversion wizard](Project-Conversion_images/Project-Conversion-img2.jpg) **Choose the assets from:** @@ -47,7 +47,7 @@ The following steps help you to use the Syncfusion® Project Conversion in the e * Installed Location - Refer to the assets from Syncfusion® installed locations. - ![Choose the required assets for Syncfusion® Essential® JS 1 ASP.NET Core project](Project-Conversion_images/Project-Conversion-img3.jpeg) + ![Choose the required assets for Syncfusion Essential JS 1 ASP.NET Core project](Project-Conversion_images/Project-Conversion-img3.jpeg) **Choose the Theme:** @@ -62,17 +62,17 @@ The following steps help you to use the Syncfusion® Project Conversion in the e ![Choose Copy Global Resources to ship the localization culture files for ASP.NET Core project](Project-Conversion_images/Project-Conversion-img14.jpeg) 4. Choose the required controls from Components section and Click the **Convert** button to convert it into a Syncfusion® Project. - ![Select the required components from the Components selection in the Syncfusion® ASP.NET Core Project Conversion Wizard](Project-Conversion_images/ProjectConversion-img5.jpg) + ![Select the required components from the Components selection in the Syncfusion ASP.NET Core Project Conversion Wizard](Project-Conversion_images/ProjectConversion-img5.jpg) The **Project Backup** dialog will be opened. If click Yes it will backup the current project before converting it to Syncfusion® project. If click No it will convert the project to Syncfusion® project without backup. - ![Syncfusion® Essential® JS 1 ASP.NET Core Project converson backup dialog](Project-Conversion_images/Project-Conversion-img6.jpg) + ![Syncfusion Essential JS 1 ASP.NET Core Project converson backup dialog](Project-Conversion_images/Project-Conversion-img6.jpg) 5. The required Syncfusion® NuGet/Bower packages, Scripts and CSS are included in the ASP.NET Core Web Application. Refer to the following screenshots for more information. - ![Required Syncfusion® Essential® JS 1 ASP.NET Core NuGet/Bower packages](Project-Conversion_images/Project-Conversion-img7.jpeg) + ![Required Syncfusion Essential JS 1 ASP.NET Core NuGet/Bower packages](Project-Conversion_images/Project-Conversion-img7.jpeg) - ![Required Syncfusion® Essential® JS 1 ASP.NET Core themes and scripts](Project-Conversion_images/Project-Conversion-img8.jpeg) + ![Required Syncfusion Essential JS 1 ASP.NET Core themes and scripts](Project-Conversion_images/Project-Conversion-img8.jpeg) 6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®. @@ -82,11 +82,11 @@ Once you converted your ASP.NET Core Web Application to Syncfusion® ASP.NET Cor 1. Include the Syncfusion® control snippets to any of the view page of your project. Refer the following screenshot for more information. - ![Syncfusion® Essential® JS 1 ASP.NET Core datepicker control code snippet](Project-Conversion_images\Project-Conversion-img11.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core datepicker control code snippet](Project-Conversion_images\Project-Conversion-img11.jpeg) 2. Then run the project and the following output will be displayed. - ![Syncfusion® Essential® JS 1 ASP.NET Core datepicker control output](Project-Conversion_images\Project-Conversion-img12.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core datepicker control output](Project-Conversion_images\Project-Conversion-img12.jpeg) I> Refer all the required external and internal scripts only once in the page with proper order. Refer this [link](https://help.syncfusion.com/js/control-initialization#adding-the-required-javascript-files) to know about order of script reference. \ No newline at end of file diff --git a/Extension/ASPNETCore-Extension/Project-Migration.md b/Extension/ASPNETCore-Extension/Project-Migration.md index 1a9792b2..9fd43764 100644 --- a/Extension/ASPNETCore-Extension/Project-Migration.md +++ b/Extension/ASPNETCore-Extension/Project-Migration.md @@ -24,18 +24,18 @@ The following steps help you to migrate your existing Syncfusion® ASP.NET Core **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Migrate Project…** in **Visual Studio**. - ![Syncfusion® Essential® JS 1 ASP.NET Core Project Migration via Syncfusion® menu](Project-Migration_images/Syncfusion_Menu_Project_Migration.png) + ![Syncfusion Essential JS 1 ASP.NET Core Project Migration via Syncfusion menu](Project-Migration_images/Syncfusion_Menu_Project_Migration.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Right-click the **Syncfusion® ASP.NET Core Web Application** from Solution Explorer and select **Syncfusion® Essential® JS 1**. Choose **Migrate the Essential® JS 1 Project to Another Version...** - ![Syncfusion® Essential® JS 1 ASP.NET Core Project Migration add-in](Project-Migration_images/Project-Migration_img1.png) + ![Syncfusion Essential JS 1 ASP.NET Core Project Migration add-in](Project-Migration_images/Project-Migration_img1.png) 2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine. - ![Syncfusion® Essential® JS 1 ASP.NET Core Project Migration window](Project-Migration_images/Project-Migration-img2.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core Project Migration window](Project-Migration_images/Project-Migration-img2.jpeg) 3. The **Project Migration** window allows you to configure the following options: @@ -45,7 +45,7 @@ The following steps help you to migrate your existing Syncfusion® ASP.NET Core 4. Click the Migrate Button. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before migrate the Syncfusion® project. If click No it will migrate the project to required Syncfusion® version without backup - ![Syncfusion® Essential® JS 1 ASP.NET Core Project Migration backup dialog](Project-Migration_images/Project-Migration-img3.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core Project Migration backup dialog](Project-Migration_images/Project-Migration-img3.jpeg) 5. The Syncfusion® NuGet/Bower Packages, Scripts and CSS are updated to the corresponding version in the project. diff --git a/Extension/ASPNETCore-Extension/Sample-Creator.md b/Extension/ASPNETCore-Extension/Sample-Creator.md index 862a093b..372dec0d 100644 --- a/Extension/ASPNETCore-Extension/Sample-Creator.md +++ b/Extension/ASPNETCore-Extension/Sample-Creator.md @@ -22,31 +22,31 @@ The following steps help you to create the Syncfusion® ASP.NET Core Web Applica **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Launch Sample Creator…** in **Visual Studio**. - ![launch the Sample Creator via Syncfusion® menu](Sample-Creator_images/Syncfusion_Menu_SampleCreator.png) + ![launch the Sample Creator via Syncfusion menu](Sample-Creator_images/Syncfusion_Menu_SampleCreator.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Launch the Syncfusion® ASP.NET Core (Essential® JS 1) Control Panel. Select the Sample Creator button to launch the ASP.NET Core (Essential® JS 1) Sample Creator application. Refer to the following screenshot for more information. - ![Syncfusion® Essential Studio® Essential® JS 1 ASP.NET Core control panel to launch the Sample Creator](Sample-Creator_images/SampleCreator-img1.png) + ![Syncfusion Essential Studio Essential JS 1 ASP.NET Core control panel to launch the Sample Creator](Sample-Creator_images/SampleCreator-img1.png) 2. Syncfusion® Sample Creator Wizard displaying the **Controls and its Feature Selection** section - ![Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator wizard](Sample-Creator_images/SampleCreator-img2.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core Sample Creator wizard](Sample-Creator_images/SampleCreator-img2.jpeg) ### Controls Selection Listed here are the Syncfusion® ASP.NET Core controls so you can choose the required controls. - ![Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator Controls selection](Sample-Creator_images/SampleCreator-img3.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core Sample Creator Controls selection](Sample-Creator_images/SampleCreator-img3.jpeg) ### Feature Selection Based on the controls, the Feature is enabled to choose the features of the corresponding controls. - ![Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator Features selection](Sample-Creator_images/SampleCreator-img4.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core Sample Creator Features selection](Sample-Creator_images/SampleCreator-img4.jpeg) ### Project Configuration @@ -69,7 +69,7 @@ Based on the controls, the Feature is enabled to choose the features of the corr * Theme Selection – Choose the required theme.The Theme Preview section shows the controls preview before create the Syncfusion® project. - ![Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator project configuration section](Sample-Creator_images/SampleCreator-img6.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core Sample Creator project configuration section](Sample-Creator_images/SampleCreator-img6.jpeg) 2. When you click the Create button, the new Syncfusion® ASP.NET Core project is created. The following resources are added in the project: @@ -84,8 +84,8 @@ Based on the controls, the Feature is enabled to choose the features of the corr * Restored the required Syncfusion® NuGet/Bower packages for selected controls under dependencies. - ![Required NuGet/Bower packages restored for the selected Syncfusion® Essential® JS 1 ASP.NET Core controls](Sample-Creator_images/SampleCreator-img9.jpeg) + ![Required NuGet/Bower packages restored for the selected Syncfusion Essential JS 1 ASP.NET Core controls](Sample-Creator_images/SampleCreator-img9.jpeg) 3. Once the project is created you can open the project by clicking the Yes button. If you click No button the corresponding location of the project will be opened. Refer the following screenshot for more information. - ![The project successfully created using Syncfusion® Essential® JS 1 ASP.NET Core Sample Creator](Sample-Creator_images/SampleCreator-img11.jpeg) + ![The project successfully created using Syncfusion Essential JS 1 ASP.NET Core Sample Creator](Sample-Creator_images/SampleCreator-img11.jpeg) diff --git a/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md index df0171da..9bb771c3 100644 --- a/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md +++ b/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md @@ -24,14 +24,14 @@ The following steps help you to create the **Syncfusion®** **ASP****.****NET** **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion® ASP.NET Core Application from Visual Studio New Project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion ASP.NET Core Application from Visual Studio New Project dialog via Syncfusion menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) N>In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Choose **File > New > Project** and navigate to **Syncfusion® > .NET Core > Syncfusion® ASP.NET Core (Essential® JS 1) Web Application** in **Visual Studio**. - ![Choose Syncfusion® ASP.NET Core Application from Visual Studio New Project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates_img1.png) + ![Choose Syncfusion ASP.NET Core Application from Visual Studio New Project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates_img1.png) 2. Name the **Project**, choose the destination location when required and set the Framework of the project, then click **OK**. The Project Configuration Wizard appears. @@ -51,18 +51,18 @@ The following steps help you to create the **Syncfusion®** **ASP****.****NET** **Components:** Choose the Required Syncfusion® components to configure. - ![Syncfusion® Essential® JS 1 ASP.NET Core Project Configuration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img2.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Core Project Configuration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img2.jpeg) 4. Once you click Create button, the Syncfusion® ASP.NET Core Application is created. 5. Required Syncfusion® NuGet/Bower packages, Scripts and CSS are added to the Project. - ![Required Syncfusion® NuGet/Bower packages added to the Syncfusion® Essential® JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img3.jpeg) + ![Required Syncfusion NuGet/Bower packages added to the Syncfusion Essential JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img3.jpeg) - ![Required Syncfusion® Scripts and Themes added to the Syncfusion® Essential® JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.jpeg) + ![Required Syncfusion Scripts and Themes added to the Syncfusion Essential JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.jpeg) 6. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration information for Syncfusion® Essential® JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) + ![Syncfusion license registration information for Syncfusion Essential JS 1 ASP.NET Core project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Overview.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Overview.md index e2d0899e..9bc7df6a 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Overview.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Overview.md @@ -37,6 +37,6 @@ Syncfusion® provides the following supports in Visual Studio: ### Selected Syncfusion® ASP.NET MVC (Essential® JS2) application in Visual Studio -![selected syncfusion® aspnetmvc](images/selected-syncfusion-mvc-application.png) +![selected syncfusion aspnetmvc](images/selected-syncfusion-mvc-application.png) > From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. \ No newline at end of file diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Conversion.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Conversion.md index 0dd252a1..126669a4 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Conversion.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Conversion.md @@ -51,9 +51,9 @@ The steps below help you to convert the ASP.NET MVC application to the Syncfusio 5. The required Syncfusion® NuGet packages, Scripts and CSS are included in the ASP.NET MVC Web Application. Refer to the following screenshots for more information. - ![syncfusion® assemblies](images/syncfusion-reference.png) + ![syncfusion assemblies](images/syncfusion-reference.png) - ![syncfusion® layout](images/layout.png) + ![syncfusion layout](images/layout.png) ![web-config](images/web-config.png) diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Migration.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Migration.md index baffab2e..b40aa89f 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Migration.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Project-Migration.md @@ -33,7 +33,7 @@ The steps below will assist you to upgrade the Syncfusion® version in the Syncf Right-click the **Syncfusion® ASP.NET MVC Application** from Solution Explorer and select **Syncfusion® Web**. Choose **Migrate the Syncfusion® ASP.NET MVC Project to Another Version…** - ![migrate the essential® js2](images/migrate-essentialJs2.png) + ![migrate the essential js2](images/migrate-essentialJs2.png) 3. The Syncfusion® Project Migration window will appear. You can choose the required version of Syncfusion® ASP.NET MVC to migrate. diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Sample-Creator.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Sample-Creator.md index 00451b16..ef1d5fe7 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Sample-Creator.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Sample-Creator.md @@ -77,4 +77,4 @@ Use the following steps to create the Syncfusion® ASP.NET MVC (Essential® JS 2 * The required Syncfusion® assemblies are added for selected controls under Project Reference. - ![syncfusion® assemblies](images/syncfusion-assemblies.png) + ![syncfusion assemblies](images/syncfusion-assemblies.png) diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Scaffolding.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Scaffolding.md index 8d12d83e..19c76a67 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Scaffolding.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Scaffolding.md @@ -23,19 +23,19 @@ The following steps explain you how to add a scaffolded item to your ASP.NET MVC 2. In the **Add Scaffold** dialog, select **Syncfusion® ASP.NET MVC UI Scaffolder**, and then click **‘Add’**. - ![syncfusion® aspnetmvc ui scaffolder](images/mvc-ui-scaffolder.png) + ![syncfusion aspnetmvc ui scaffolder](images/mvc-ui-scaffolder.png) 3. In the Syncfusion® UI Scaffolding dialog, select the desired control to perform scaffolding, and then click **Next**. - ![syncfusion® ui scaffolding](images/syncfusion-ui-scaffolding.png) + ![syncfusion ui scaffolding](images/syncfusion-ui-scaffolding.png) 4. Selected control model dialogue will be launched in the Syncfusion® UI Scaffolder. Enter the **Controller Name** and **View Name** as application requirements, and then select the required **Model Class** of the active project and its relevant **Data Context Class**, and then click **Next**. - ![syncfusion® ui scaffolding for datagrid](images/ui-scaffolding-datagrid.png) + ![syncfusion ui scaffolding for datagrid](images/ui-scaffolding-datagrid.png) 5. Selected control feature dialogue will be launched in the Syncfusion® UI Scaffolder. Select the required features, update the required data field, and then click **Add**. - ![syncfusion® scaffolding add button](images/scaffolding-add-button.png) + ![syncfusion scaffolding add button](images/scaffolding-add-button.png) 6. The **Controller** and the corresponding **View** files are now generated with the selected features of Syncfusion® control code snippet. diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md index 9361dc85..9313b372 100644 --- a/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md +++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md @@ -23,7 +23,7 @@ Use the following steps to create the **Syncfusion® ASP.NET MVC (Essential® JS Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ2) > Create New Syncfusion® Project…** in **Visual Studio 2019 earlier**. - ![create new syncfusion® project](images/new-syncfusion-project.png) + ![create new syncfusion project](images/new-syncfusion-project.png) > From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. @@ -33,11 +33,11 @@ Use the following steps to create the **Syncfusion® ASP.NET MVC (Essential® JS Choose **File > New > Project** and navigate to **Syncfusion® > Web > Syncfusion® ASP.NET MVC (Essential® JS 2) Application** in **Visual Studio 2019 earlier**. - ![syncfusion® asp.net mvc](images/syncfusion-aspmvc-application.png) + ![syncfusion asp.net mvc](images/syncfusion-aspmvc-application.png) > In Visual Studio 2019, Syncfusion® ASP.NET MVC will be shown like below in solution explores. - ![Syncfusion® MVC Project Wizard](images/SyncfusionMvcProjectWizard.png) + ![Syncfusion MVC Project Wizard](images/SyncfusionMvcProjectWizard.png) 2. Name the **Project**, choose the destination location, and set the .NET Framework of the project, and then click **OK**. The Project Configuration Wizard appears. @@ -67,4 +67,4 @@ Use the following steps to create the **Syncfusion® ASP.NET MVC (Essential® JS 5. Then, the Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post to learn more about the licensing changes introduced in Essential Studio®. - ![syncfusion® license](images/syncfusion-license.png) + ![syncfusion license](images/syncfusion-license.png) diff --git a/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md b/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md index 3790909a..60ed0253 100644 --- a/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md +++ b/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md @@ -60,6 +60,6 @@ The Syncfusion® Blazor snippet simply inserts the code into the razor file. You 4. Open the **~/Startup.cs** file for server application and the **~/Program.cs** file for client application then register the Syncfusion® Blazor Service. - ![Syncfusion® Configuration](images/Configuration-Snippet.png) + ![Syncfusion Configuration](images/Configuration-Snippet.png) 5. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/Blazor-Extension/Visual-Studio/scaffolding.md b/Extension/Blazor-Extension/Visual-Studio/scaffolding.md index 863232df..19956cb4 100644 --- a/Extension/Blazor-Extension/Visual-Studio/scaffolding.md +++ b/Extension/Blazor-Extension/Visual-Studio/scaffolding.md @@ -33,7 +33,7 @@ The steps below assist you to how to add a scaffolded item to your Blazor applic 2. In the **Add New Scaffolded item** dialog, select **Syncfusion® Blazor Scaffolder** and then click **‘Add’**. - ![Choose Syncfusion® Scaffolding from Visual Studio Add scaffold dialog](images/Syncfusion_scaffolder.png) + ![Choose Syncfusion Scaffolding from Visual Studio Add scaffold dialog](images/Syncfusion_scaffolder.png) 3. In the Syncfusion® UI Scaffolder dialog, select the desired control to perform scaffolding, and then click **Next**. diff --git a/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md b/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md index 7ca1b55b..4e4248b4 100644 --- a/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md +++ b/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md @@ -18,7 +18,7 @@ When dragging and dropping a Syncfusion® control from either the **Syncfusion® The following alert message will be displayed if multiple versions of the same Syncfusion® NuGet package (e.g., Syncfusion.Xamarin.SfChart **v24.1.xx** and **v24.2.xx**(xamarin) / Syncfusion.MAUI.Buttons **v24.1.xx** and **24.2.xx**(Maui)) are already installed in your project. Recommend maintaining the same version NuGet reference. -![Syncfusion® Xamarin toolbox alert message when multiple version of the same Syncfusion® Xamarin NuGet package already installed in the project](Alert-message-in-Syncfusion-Xamarin-Toolbox_images\Same-NuGet-Multiple-Version-Installed.jpg) +![Syncfusion Xamarin toolbox alert message when multiple version of the same Syncfusion Xamarin NuGet package already installed in the project](Alert-message-in-Syncfusion-Xamarin-Toolbox_images\Same-NuGet-Multiple-Version-Installed.jpg) To resolve this, follow these steps: 1. Uninstall the multiple versions of the same Syncfusion® NuGet package currently installed in your project. @@ -28,7 +28,7 @@ To resolve this, follow these steps: The following alert message will be displayed when different versions of Syncfusion® NuGet packages are installed in your project. Hence, you are not aware of which version of the Syncfusion® NuGet package you need to install in your project. -![Syncfusion® Xamarin toolbox alert message when different Syncfusion® Xamarin NuGet packages are installed with multiple version in the project](Alert-message-in-Syncfusion-Xamarin-Toolbox_images\Diferent-NuGet-Multiple-Version-Installed.jpg) +![Syncfusion Xamarin toolbox alert message when different Syncfusion Xamarin NuGet packages are installed with multiple version in the project](Alert-message-in-Syncfusion-Xamarin-Toolbox_images\Diferent-NuGet-Multiple-Version-Installed.jpg) To resolve this, manually install all the required versions of Syncfusion® NuGet packages in the same version of your project. Then, drag the required Syncfusion® component from the Syncfusion® Toolbox (Xamarin/.NET MAUI) and drop the render code snippet in the XAML file of your project. Please refer to the following help topics to use the Syncfusion® Toolbox: diff --git a/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md b/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md index ca2fab58..5dfee0d3 100644 --- a/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md +++ b/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md @@ -23,7 +23,7 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension - ![Syncfusion® ASP.NET MVC Extension installed location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img1.png) + ![Syncfusion ASP.NET MVC Extension installed location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img1.png) **On or After 17.1.0.32-beta version** @@ -33,7 +33,7 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension Refer the following screenshot for more information. - ![Syncfusion® ASP.NET MVC Extension installed location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img4.png) + ![Syncfusion ASP.NET MVC Extension installed location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img4.png) 2. When the above path exists, it means that the ASP.NET MVC Extension build has already been installed in the machine. So now you can install the following Syncfusion® @@ -54,7 +54,7 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\VS2017_ - ![Syncfusion® ASP.NET MVC Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img2.png) + ![Syncfusion ASP.NET MVC Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img2.png) **On or After 17.1.0.32-beta version** @@ -67,7 +67,7 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\ASP.NET MVC - EJ1\18.1.0.52\Utilities\Extensions_ - ![Syncfusion® ASP.NET MVC Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img4.png) + ![Syncfusion ASP.NET MVC Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img4.png) ## To Install Syncfusion® Visual Studio Extension: @@ -81,7 +81,7 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\Project Conversion\VS2017_ - ![Syncfusion® Web Conversion and Migration VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img3.png) + ![Syncfusion Web Conversion and Migration VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img3.png) **On or After 17.1.0.32-beta version** diff --git a/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md b/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md index 2dd12e96..fc7b8cf4 100644 --- a/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md +++ b/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md @@ -21,7 +21,7 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension - ![Syncfusion® Installed location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img1.png) + ![Syncfusion Installed location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img1.png) 2. When the above path exists, it means that the ASP.NET MVC Extension build has already been installed in the machine. So now you can install the following Syncfusion® @@ -38,7 +38,7 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\VS2017_ - ![Syncfusion® Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img2.png) + ![Syncfusion Project Template VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img2.png) ## To Install Syncfusion® Visual Studio Extension: Navigate to the following Location and run the “Syncfusion® Web Conversion and Migration.vsix” extension. @@ -49,7 +49,7 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension _Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\Project Conversion\VS2017_ - ![Syncfusion® Visual Studio extension VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img3.png) + ![Syncfusion Visual Studio extension VSIX file location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img3.png) From 5705f98b113d7ceab8bf723936e417b2a026e5dc Mon Sep 17 00:00:00 2001 From: Kesavaraman Date: Wed, 22 Jan 2025 19:14:21 +0530 Subject: [PATCH 3/7] Trademark added --- .../WindowsForms-Extension/Add-References.md | 18 +++++++------- .../Check-for-Updates.md | 4 ++-- Extension/WindowsForms-Extension/Overview.md | 6 ++--- ...fusion-Item-Templates-for-Windows-Forms.md | 12 +++++----- ...ion-Project-Templates-for-Windows-Forms.md | 18 +++++++------- .../WindowsForms-Extension/Template-Studio.md | 24 +++++++++---------- 6 files changed, 41 insertions(+), 41 deletions(-) diff --git a/Extension/WindowsForms-Extension/Add-References.md b/Extension/WindowsForms-Extension/Add-References.md index b07fc0c8..eeb02833 100644 --- a/Extension/WindowsForms-Extension/Add-References.md +++ b/Extension/WindowsForms-Extension/Add-References.md @@ -24,49 +24,49 @@ Follow the given steps to add the Syncfusion® references in Visual Studio: **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms > Add References…** or any other Form in **Visual Studio**. - ![Syncfusion® Reference Manager via Syncfusion® Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png) + ![Syncfusion Reference Manager via Syncfusion Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. **Option 2:** Right-click the selected project file from Solution Explorer, then select **Syncfusion® Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio. - ![Syncfusion® Reference Manager add-in](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img1.png) + ![Syncfusion Reference Manager add-in](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img1.png) 3. The Syncfusion® Reference Manager Wizard that contains the list of Syncfusion® WinForms controls that are loaded. - ![Syncfusion® Reference Manger Wizard](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img2.png) + ![Syncfusion Reference Manger Wizard](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img2.png) **Platform Selection:** If launched the Syncfusion® Reference Manager from Console/Class Library project, Platform selection option will be appeared as option in Syncfusion® Reference Manager. Choose the required platform. - ![Platform selection option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img3.png) + ![Platform selection option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img3.png) **Assembly From:** Choose the assembly location, either from NuGet packages, the build installed location, or by using the GAC location. N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® Winforms setup has been installed. - ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img4.png) + ![Assembly location option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img4.png) N> The GAC option will not be available if you have selected a WinForms (.NET 8.0, .NET 7.0, and .NET 6.0) application in Visual Studio 2022. **Version:** Choose the build version to add the corresponding version assemblies to the project. - ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger1-img4.png) + ![Assembly location option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger1-img4.png) 4. Choose the required controls that you want to include in the project. Then, click Done to add the required assemblies for the selected controls into the project. The following screenshot shows the list of required assemblies for the selected controls to be added. - ![Syncfusion® Reference Manager new assemblies add information dialog](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img5.png) + ![Syncfusion Reference Manager new assemblies add information dialog](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img5.png) 5. Click **OK**. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar. - ![Syncfusion® Reference Manager success status in Visual Studio status bar](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img6.png) + ![Syncfusion Reference Manager success status in Visual Studio status bar](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img6.png) 6. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusio.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® Reference Manager](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img7.png) + ![Syncfusion license registration required information dialog in Syncfusion® Reference Manager](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img7.png) N> Syncfusion® provides Reference Manager support for specific .NET Framework, which is shipped (assemblies) in Syncfusion® Essential Studio® setup. So, if you try to add Syncfusion® assemblies in the project and project framework is not supported with selected Syncfusion® version assemblies, the dialog appears along with **“Current build v{version} is not supported this framework v{Framework Version}”** message. diff --git a/Extension/WindowsForms-Extension/Check-for-Updates.md b/Extension/WindowsForms-Extension/Check-for-Updates.md index 60f98b60..c86606c8 100644 --- a/Extension/WindowsForms-Extension/Check-for-Updates.md +++ b/Extension/WindowsForms-Extension/Check-for-Updates.md @@ -17,12 +17,12 @@ You can check updates availability in Visual Studio, and then install the update 1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu - ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) + ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. 2. When there is an update, **Update** dialog box opens. - ![Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) + ![Syncfusion check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) 3. You can download the latest Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. diff --git a/Extension/WindowsForms-Extension/Overview.md b/Extension/WindowsForms-Extension/Overview.md index 548c23e3..0fc6471e 100644 --- a/Extension/WindowsForms-Extension/Overview.md +++ b/Extension/WindowsForms-Extension/Overview.md @@ -27,15 +27,15 @@ The Syncfusion® provides the following extension supports in Visual Studio: **No project selected in Visual Studio** -![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Microsoft Windows Forms application in Visual Studio** -![Syncfusion® Menu when Selected Microsoft Windows Forms application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) +![Syncfusion Menu when Selected Microsoft Windows Forms application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) **Selected Syncfusion® Windows Forms application in Visual Studio** -![Syncfusion® Menu when Selected Synfusion Windows Forms application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) +![Syncfusion Menu when Selected Synfusion Windows Forms application in Visual Studio](Overview-images/Syncfusion_Menu_OverView3.png) N> From Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. diff --git a/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md b/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md index 65dc77fc..ed5c2cfa 100644 --- a/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md +++ b/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md @@ -25,18 +25,18 @@ The following steps will guide you in adding the Syncfusion® WinForms component 2. From the **Solution Explorer, right-click** on the WinForms application. Choose **Add Syncfusion® Item...**. - ![Choose Add Syncfusion® Item option from right click project](Item-Template-images/Add-Syncfusion-item.png) + ![Choose Add Syncfusion Item option from right click project](Item-Template-images/Add-Syncfusion-item.png) **Option 2:** 3. Click **Extensions > Essential Studio® for WinForms > Add Syncfusion® Item…** in Visual Studio. - ![Choose Add Syncfusion® Item option from menu](Item-Template-images/Add-item.png) + ![Choose Add Syncfusion Item option from menu](Item-Template-images/Add-item.png) 4. The Syncfusion® WinForms Item Template wizard will be launched as follows. - ![Syncfusion® WinForms Item template Components](Item-Template-images/Add-Syncfusion-ui.png) + ![Syncfusion WinForms Item template Components](Item-Template-images/Add-Syncfusion-ui.png) 5. Select the WinForms Components from the Component list within your WinForms Item Template. The features associated with the selected Component will be presented. From here, choose the specific features that are essential for your project. @@ -46,12 +46,12 @@ The following steps will guide you in adding the Syncfusion® WinForms component 7. Click **Add**, and a pop-up will appear providing information about adding Component **files** and **NuGet/Assemblies** details. - ![Syncfusion® WinForms Item template details](Item-Template-images/Add-Syncfusion-item-3.png) + ![Syncfusion WinForms Item template details](Item-Template-images/Add-Syncfusion-item-3.png) 8. Click **OK** to incorporate the chosen Components into the WinForms application, along with the necessary Syncfusion® assemblies. - ![Syncfusion® WinForms Item template Gallery](Item-Template-images/Add-Syncfusion-item-details.png) + ![Syncfusion WinForms Item template Gallery](Item-Template-images/Add-Syncfusion-item-details.png) 9. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® WinForms Item template Gallery](Item-Template-images/Syncfusion-Item-Template-Gallery-7.png) \ No newline at end of file + ![Syncfusion WinForms Item template Gallery](Item-Template-images/Syncfusion-Item-Template-Gallery-7.png) \ No newline at end of file diff --git a/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md b/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md index 3fd82125..64a9ceac 100644 --- a/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md +++ b/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md @@ -24,18 +24,18 @@ Use the following steps to create the Syncfusion® Windows Forms project through **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion® Windows Forms Application via Syncfusion® menu](Project-Template-images\Syncfusion-menu.png) + ![Choose Syncfusion Windows Forms Application via Syncfusion menu](Project-Template-images\Syncfusion-menu.png) N> In Visual Studio 2015 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. **Option 2:** Choose **File -> New -> Project**. Opens a new dialog to create a new project. You can obtain the templates provided by Syncfusion® for WinForms by filtering the project type with Syncfusion® or by using the Syncfusion® keyword in the search option - ![Choose Syncfusion® Windows Forms Application from Visual Studio new project dialog](Project-Template-images\Syncfusion-Project-Template-Gallery2019-1.png) + ![Choose Syncfusion Windows Forms Application from Visual Studio new project dialog](Project-Template-images\Syncfusion-Project-Template-Gallery2019-1.png) In Visual Studio 2015 or lower, Select File > New > Project and navigate to Syncfusion® > Windows > Syncfusion® Windows Forms Application in Visual Studio. - ![Choose Syncfusion® Windows Forms Application from Visual Studio new project dialog](Project-Template-images\Syncfusion-Project-Template-Gallery-1.png) + ![Choose Syncfusion Windows Forms Application from Visual Studio new project dialog](Project-Template-images\Syncfusion-Project-Template-Gallery-1.png) 2. Name the **Project**, choose the destination location when required, select the project type, and choose the reference from where the assembly is added to the project then click **OK**. @@ -43,11 +43,11 @@ Use the following steps to create the Syncfusion® Windows Forms project through 3. Choose the options to configure the Syncfusion® WinForms Application by using the following Project Configuration Wizard. - ![Syncfusion® Windows Forms project configuration wizard](Project-Template-images\Syncfusion-Project-Template-Gallery2019-2.png) + ![Syncfusion Windows Forms project configuration wizard](Project-Template-images\Syncfusion-Project-Template-Gallery2019-2.png) In Visual Studio 2015 or lower, Syncfusion® Windows Forms Application project configuration wizard. - ![Syncfusion® Windows Forms project configuration wizard](Project-Template-images\Syncfusion-Project-Template-Gallery-2.png) + ![Syncfusion Windows Forms project configuration wizard](Project-Template-images\Syncfusion-Project-Template-Gallery-2.png) **Project Configurations** @@ -67,12 +67,12 @@ Use the following steps to create the Syncfusion® Windows Forms project through 4. After choosing above project configuration options in the Project Configuration Wizard, click the create button then Syncfusion® WinForms project is created with the necessary XAML files and required Syncfusion® WinForms assemblies/NuGet packages. - ![Syncfusion® Windows Forms project created with required references](Project-Template-images\Syncfusion-Project-Template-Gallery-6.png) + ![Syncfusion Windows Forms project created with required references](Project-Template-images\Syncfusion-Project-Template-Gallery-6.png) - ![Syncfusion® Windows Forms project created with required forms](Project-Template-images\Syncfusion-Project-Template-Gallery-7.png) + ![Syncfusion Windows Forms project created with required forms](Project-Template-images\Syncfusion-Project-Template-Gallery-7.png) - ![Syncfusion® Windows Forms project created with readme](Project-Template-images\Syncfusion-Project-Template-Gallery-9.PNG) + ![Syncfusion Windows Forms project created with readme](Project-Template-images\Syncfusion-Project-Template-Gallery-9.PNG) 5. Then, the Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post to learn more the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® Windows Forms Project](Project-Template-images\Syncfusion-Project-Template-Gallery-8.png) \ No newline at end of file + ![Syncfusion license registration required information dialog in Syncfusion Windows Forms Project](Project-Template-images\Syncfusion-Project-Template-Gallery-8.png) \ No newline at end of file diff --git a/Extension/WindowsForms-Extension/Template-Studio.md b/Extension/WindowsForms-Extension/Template-Studio.md index fa2a9997..ad4be1e8 100644 --- a/Extension/WindowsForms-Extension/Template-Studio.md +++ b/Extension/WindowsForms-Extension/Template-Studio.md @@ -27,22 +27,22 @@ Create the Syncfusion® WinForms project using the Visual Studio Project Templat **Option 1:** Choose **Extension -> Syncfusion® -> Essential Studio® for WinForms -> Create New Syncfusion® Project…** from the Visual Studio menu. - ![Choose Syncfusion® WinForms Application from Visual Studio new project dialog via Syncfusion® menu](Template-Studio-Images/WF-1.png) + ![Choose Syncfusion WinForms Application from Visual Studio new project dialog via Syncfusion menu](Template-Studio-Images/WF-1.png) N> In Visual Studio 2017, you can see the Syncfusion® menu directly in the Visual Studio menu. **Option 2:** Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by Syncfusion® or typing Syncfusion® as a keyword in the search option can help you find the Syncfusion® templates for WinForms. - ![Choose Syncfusion® WinForms Application from Visual Studio new project dialog](Template-Studio-Images/WF-2.png) + ![Choose Syncfusion WinForms Application from Visual Studio new project dialog](Template-Studio-Images/WF-2.png) 3. Select the **Syncfusion® WinForms Template Studio** and click Next. - ![Choose Syncfusion® WinForms Application from Visual Studio new project dialog](Template-Studio-Images/WF-3.png) + ![Choose Syncfusion WinForms Application from Visual Studio new project dialog](Template-Studio-Images/WF-3.png) 4. When you launch the **Syncfusion® WinForms Template Studio**, you will encounter a configuration wizard that allows you to set up your Syncfusion® WinForms application. Within this wizard, you will have the option to specify your preferred .NET Core Version or .NET Framework Version, select the desired language(CSharp or Visual Basic), and choose the reference type according to your requirements. - ![Syncfusion® WinForms project configuration wizard](Template-Studio-Images/WF-5.png) + ![Syncfusion WinForms project configuration wizard](Template-Studio-Images/WF-5.png) N> The installed location and GAC options will be available only after the Syncfusion® Essential WinForms setup has been installed. Use the NuGet option instead of installing the Syncfusion® Essential WinForms setup. Also, the GAC option will not be available when you choose .NET 6.0, .NET 7.0, and .NET 8.0 from the project type option in Visual Studio. @@ -50,17 +50,17 @@ Create the Syncfusion® WinForms project using the Visual Studio Project Templat 5. Navigate to the **Type** tab and choose the Syncfusion® WinForms application type you want. When selecting the type of template for your application, you have two options: - ![Syncfusion® WinForms project type selection wizard](Template-Studio-Images/WF-4.png) + ![Syncfusion WinForms project type selection wizard](Template-Studio-Images/WF-4.png) **Predefined template:** Choose this option to select from 5 predefined templates, including Calendar, Contact, Outlook, Docking Manager, and Spreadsheet. By choosing one of these templates, you can create your application without needing to follow any further steps. - ![Syncfusion® WinForms Predefined template wizard](Template-Studio-Images/WF-10.png) + ![Syncfusion WinForms Predefined template wizard](Template-Studio-Images/WF-10.png) **Project type:** Choose this option to select from 4 project types, including Blank, Menu Bar, Ribbon, and Tabbed Form. 6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion® WinForms components you can add to the application. - ![Syncfusion® WinForms pages selection wizard](Template-Studio-Images/WF-6.png) + ![Syncfusion WinForms pages selection wizard](Template-Studio-Images/WF-6.png) To unselect the added control(s), Click ‘x’ for the corresponding control in the control list from the Project Details. @@ -68,11 +68,11 @@ Create the Syncfusion® WinForms project using the Visual Studio Project Templat 7. Click **Next** or navigate to the **Control Features** tab to view the listed features for the selected controls. From here, choose the features needed. - ![Syncfusion® WinForms control features selection wizard](Template-Studio-Images/WF-15.png) + ![Syncfusion WinForms control features selection wizard](Template-Studio-Images/WF-15.png) 8. Click **Next** or navigate the **App Features** tab to select the desired application features. - ![Syncfusion® WinForms app features selection wizard](Template-Studio-Images/WF-7.png) + ![Syncfusion WinForms app features selection wizard](Template-Studio-Images/WF-7.png) N> The App Features option is not accessible for .NET Framework. @@ -80,11 +80,11 @@ Create the Syncfusion® WinForms project using the Visual Studio Project Templat In the **Project Details** section, modify configurations and project types. Additionally, you can remove one or more controls from the selected list and remove the chosen application feature. - ![Syncfusion® WinForms project details selection and unselection wizard](Template-Studio-Images/WF-8.png) + ![Syncfusion WinForms project details selection and unselection wizard](Template-Studio-Images/WF-8.png) 9. Click **Create** to generate the Syncfusion® WinForms application. Once you've created the project, the relevant Syncfusion® NuGet packages will be automatically added to your project for the chosen components. For example, if you add an **DataGrid** control, the corresponding Syncfusion® NuGet packages required for that control will be installed. - ![Syncfusion® WinForms project created with readme](Template-Studio-Images/WF-9.png) + ![Syncfusion WinForms project created with readme](Template-Studio-Images/WF-9.png) ![NuGetEntry](Template-Studio-Images/NuGetEntry.png) @@ -154,4 +154,4 @@ Here's a simple explanation: 13. If you install the trial setup or NuGet packages from nuget.org, you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from the 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® WinForms project](Template-Studio-Images/Syncfusion-Project-Template-Gallery-8.png) \ No newline at end of file + ![Syncfusion license registration required information dialog in Syncfusion WinForms project](Template-Studio-Images/Syncfusion-Project-Template-Gallery-8.png) \ No newline at end of file From ff7af75b55c5d91629648d08ab83073068ad90f0 Mon Sep 17 00:00:00 2001 From: Kesavaraman Date: Wed, 22 Jan 2025 19:26:12 +0530 Subject: [PATCH 4/7] TradeMark Added --- .../Visual-Studio/Toolbox-Control.md | 6 ++-- .../NuGet-Packages.md | 6 ++-- .../Register-the-Syncfusion-License-key.md | 2 +- .../Syncfusion-NuGet-Manager.md | 16 +++++----- ...erences-via-Syncfusion-Reference-Manger.md | 18 +++++------ ...ion-assemblies-in-Visual-Studio-project.md | 4 +-- .../Migrate-the-Syncfusion-assemblies.md | 4 +-- .../Syncfusion-Troubleshooter.md | 26 +++++++-------- Extension/UWP-Extension/Overview.md | 4 +-- Extension/UWP-Extension/Project-Templates.md | 12 +++---- Extension/WPF-Extension/Add-Item.md | 12 +++---- Extension/WPF-Extension/Add-References.md | 24 +++++++------- Extension/WPF-Extension/Check-for-Updates.md | 6 ++-- Extension/WPF-Extension/Create-Project.md | 18 +++++------ .../Download-and-Installation.md | 4 +-- Extension/WPF-Extension/Overview.md | 6 ++-- Extension/WPF-Extension/Template-Studio.md | 24 +++++++------- .../WPF-Extension/Toolbox-Configuration.md | 4 +-- Extension/WPF-Extension/Troubleshooting.md | 22 ++++++------- .../Xamarin-Extension/Check-for-Updates.md | 6 ++-- Extension/Xamarin-Extension/Create-Project.md | 32 +++++++++---------- .../Download-and-Installation.md | 2 +- .../Xamarin-Extension/Essential-UI-Kit.md | 2 +- Extension/Xamarin-Extension/Overview.md | 4 +-- Extension/Xamarin-Extension/Toolbox.md | 10 +++--- 25 files changed, 137 insertions(+), 137 deletions(-) diff --git a/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md b/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md index d73b2f6a..aff8baee 100644 --- a/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md +++ b/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md @@ -25,7 +25,7 @@ To launch the Syncfusion® .NET MAUI Toolbox from the Syncfusion® menu in Visua 5. From the **Essential Studio® for .NET MAUI** submenu, select **Launch .NET MAUI Toolbox**. This toolbox provides a set of tools and features to easily incorporate Syncfusion® .NET MAUI components into your .NET MAUI application. - ![Syncfusion® .NET MAUI Custom Toolbox via Syncfusion® menu](images/ToolboxSyncfusionMenu.png) + ![Syncfusion .NET MAUI Custom Toolbox via Syncfusion® menu](images/ToolboxSyncfusionMenu.png) ## Launching Syncfusion® .NET MAUI Toolbox from the View menu @@ -36,12 +36,12 @@ To launch the Syncfusion® .NET MAUI Toolbox from the View menu in Visual Studio 4. In the sub-menu that appears, click on **Syncfusion® .NET MAUI Toolbox**. This toolbox provides a set of tools and features to easily incorporate Syncfusion® .NET MAUI components into your .NET MAUI application. - ![Syncfusion® .NET MAUI Custom Toolbox view menu](images/ToolboxViewMenu.png) + ![Syncfusion .NET MAUI Custom Toolbox view menu](images/ToolboxViewMenu.png) ## Add Syncfusion® .NET MAUI Toolbox Components To incorporate Syncfusion® .NET MAUI components into your XAML design file, you can easily add them by dragging and dropping them from the toolbox. This intuitive approach automatically inserts the component's code sample and namespace into your XAML file, while also taking care of installing necessary NuGet packages. - ![Syncfusion® .NET MAUI Toolbox Wizard](images/ToolboxComponents.gif) + ![Syncfusion .NET MAUI Toolbox Wizard](images/ToolboxComponents.gif) Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file diff --git a/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md b/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md index 13178a59..98f4dd9d 100644 --- a/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md +++ b/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md @@ -279,7 +279,7 @@ You should get the private Syncfusion® NuGet feed URL to install or upgrade the 2. Click the Copy URL label under required platform to copy the Syncfusion® required platform NuGet feed to clipboard. - ![Syncfusion® Essential® JS 2 ASP.NET Core NuGet feed URL](NuGet_Packages_Images/img1.png) + ![Syncfusion Essential JS 2 ASP.NET Core NuGet feed URL](NuGet_Packages_Images/img1.png) 3. Now, use this NuGet feed URL to access the Syncfusion® NuGet Packages in Visual Studio. @@ -303,7 +303,7 @@ You should get the private Syncfusion® NuGet feed URL to install or upgrade the 5. Click the **Update** button to add the name and source details to package sources. - ![NuGet Package Manager dialog with Syncfusion® Essential® JS 2 NuGet feed URL for reference](NuGet_Packages_Images/img2.png) + ![NuGet Package Manager dialog with Syncfusion Essential JS 2 NuGet feed URL for reference](NuGet_Packages_Images/img2.png) #### macOS @@ -325,7 +325,7 @@ You should get the private Syncfusion® NuGet feed URL to install or upgrade the For example, Name: Syncfusion® ASP.NET Core Packages, Source: [https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore](https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore). - ![Add Package Source dialog to add Syncfusion® NuGet feed](NuGet_Packages_Images/img5.png) + ![Add Package Source dialog to add Syncfusion NuGet feed](NuGet_Packages_Images/img5.png) 5. Now, click **Add Source** and then click **OK**. diff --git a/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md b/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md index d589801a..e291b862 100644 --- a/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md +++ b/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md @@ -37,4 +37,4 @@ While using Syncfusion® NuGet package of version that is **prior to 13.2.0.29** N> You should provide the unlock key which is started with "@" and ended with "=" as a parameter for this Syncfusion® License tool. - ![Command for register the Syncfusion® Unlock key](Register-the-Syncfusion-License-key_images/Register-the-Syncfusion-License-key-img1.png) + ![Command for register the Syncfusion Unlock key](Register-the-Syncfusion-License-key_images/Register-the-Syncfusion-License-key-img1.png) diff --git a/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md b/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md index 93a751d9..b1627eef 100644 --- a/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md +++ b/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md @@ -19,29 +19,29 @@ The following steps directs you to add the Syncfusion® NuGet Package sources fr 1. Run the SyncfusionNuGetManager.exe from Syncfusion® NuGet Manager extracted location. - ![Syncfusion® NuGet Manager extracted location](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img1.png) + ![Syncfusion NuGet Manager extracted location](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img1.png) 2. Syncfusion® NuGet Manager Window will be opened. - ![Syncfusion® NuGet Manager main window](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img2.png) + ![Syncfusion NuGet Manager main window](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img2.png) 3. Select the required platforms needed to be configured from “Select platforms to add” (Left side of the window) column and click Add>> button. - ![Selected platforms NuGet feed configure option in Syncfusion® NuGet Manager](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img3.png) + ![Selected platforms NuGet feed configure option in Syncfusion NuGet Manager](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img3.png) 4. Now selected platforms will be added under “Selected platforms to remove” (Right side of the window) column. Click “Configure” button to add the required Syncfusion® Package sources to NuGet Package Manager. - ![Selected platforms NuGet feed remove option in Syncfusion® NuGet Manager](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img4.png) + ![Selected platforms NuGet feed remove option in Syncfusion NuGet Manager](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img4.png) 5. Once Syncfusion® NuGet Manager added the Syncfusion® NuGet sources, the changes will be reflected in package sources of your Visual Studio. - ![NuGet package manager dialog with Syncfusion® NuGet feeds](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img5.png) + ![NuGet package manager dialog with Syncfusion NuGet feeds](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img5.png) ## Remove Syncfusion® NuGet Package sources 1. If any configured Syncfusion® NuGet Package sources are no longer required, Select the unwanted platforms from “Select platforms to remove” (Right side of the window) column and click < Platform selection option will be appeared only if Essential Studio® for Enterprise Edition with the platforms WPF and Windows Forms has been installed or both Essential Studio® for WPF and Essential Studio® for Windows Forms has been installed. @@ -28,38 +28,38 @@ To add the assemblies: [https://help.syncfusion.com/wpf/themes/skin-manager](https://help.syncfusion.com/wpf/themes/skin-manager) - ![Themes selection option in Syncfusion® Reference Manger](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img4.png) + ![Themes selection option in Syncfusion Reference Manger](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img4.png) N> Themes option will be enabled only if selected SfSkinManager supported controls. - ![Tooltip information for Syncfusion® Reference Manager themes option](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img5.png) + ![Tooltip information for Syncfusion Reference Manager themes option](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img5.png) 5. Reference assemblies * You can add Syncfusion® assemblies from NuGet packages, the build installed location, or by using the GAC location. This option determines the location of the assemblies that are referenced in the project. N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® setup has been installed. - ![Options for assembly location in Syncfusion® Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img8.png) + ![Options for assembly location in Syncfusion Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img8.png) N> The GAC option will not be available if you have selected a .NET 7.0 or .NET 6.0 application in Visual Studio 2022. * Select the Syncfusion® Essential Studio® versions that were previously installed on your machine.This option determines the assembly version that is referenced in the project. - ![Versions for assemblies in Syncfusion® Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img9.png) + ![Versions for assemblies in Syncfusion Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img9.png) * Choose the required controls that you want include in project 6. Click Done to add the required assemblies for the selected controls into the project. The following screenshot shows the list of required assemblies for the selected controls to be added. - ![Syncfusion® Reference Manager new assemblies add information dialog](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img2.png) + ![Syncfusion Reference Manager new assemblies add information dialog](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img2.png) 7. Click OK. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar. - ![Syncfusion® Reference Manager success status in Visual Studio status bar](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img3.png) + ![Syncfusion Reference Manager success status in Visual Studio status bar](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img3.png) 8. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img7.png) + ![Syncfusion license registration required information dialog in Syncfusion® Reference Manager](Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger_images/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger-img7.png) N> We are providing Syncfusion® Reference Manager support for specific framework which is shipped (assemblies) in our Syncfusion® Essential Studio® setup. So, if we try to add Syncfusion® assemblies in project and project framework is not supported with selected Syncfusion® version assemblies, the dialog will be appeared along with **“Current build v{version} is not supported this framework v{Framework Version}”** message. diff --git a/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md b/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md index d2f9d394..1d24c369 100644 --- a/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md +++ b/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md @@ -13,7 +13,7 @@ To open Syncfusion® Reference Manager Wizard, follow either one of the options **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms/WPF > Add References…** or any other Form in **Visual Studio**. -![Syncfusion® Reference Manager via Syncfusion® Menu](Configure-Syncfusion-assemblies-in-Visual-Studio-project_images/Syncfusion_Menu_AddReference.png) +![Syncfusion Reference Manager via Syncfusion Menu](Configure-Syncfusion-assemblies-in-Visual-Studio-project_images/Syncfusion_Menu_AddReference.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. @@ -22,7 +22,7 @@ Right-click the selected project file from Solution Explorer, then select **Sync -![Syncfusion® Reference Manager add-in](Configure-Syncfusion-assemblies-in-Visual-Studio-project_images/Configure-Syncfusion-assemblies-in-Visual-Studio-project-img1.png) +![Syncfusion Reference Manager add-in](Configure-Syncfusion-assemblies-in-Visual-Studio-project_images/Configure-Syncfusion-assemblies-in-Visual-Studio-project-img1.png) diff --git a/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md b/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md index 8631ac87..53a67401 100644 --- a/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md +++ b/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md @@ -18,14 +18,14 @@ To migrate the Syncfusion® assemblies, 3. The dialog Syncfusion® Reference Manager is opened. Then choose the required Syncfusion® Essential Studio® version to migrate the project. Refer the following screenshots for more information. - ![Syncfusion® Reference Manager version selection option](Migrate-the-Syncfusion-assemblies_images/Migrate-the-Syncfusion-assemblies-img1.png) + ![Syncfusion Reference Manager version selection option](Migrate-the-Syncfusion-assemblies_images/Migrate-the-Syncfusion-assemblies-img1.png) 4. When you want to add controls additionally, select controls while the migration is in process. Otherwise, do not select any control. 5. Click Done. The following screenshot shows the list of assemblies to be migrated. - ![Syncfusion® Reference Manager backup dialog with the migrating assembly details](Migrate-the-Syncfusion-assemblies_images/Migrate-the-Syncfusion-assemblies-img2.png) + ![Syncfusion Reference Manager backup dialog with the migrating assembly details](Migrate-the-Syncfusion-assemblies_images/Migrate-the-Syncfusion-assemblies-img2.png) diff --git a/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md b/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md index 6c43f35a..7d65784e 100644 --- a/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md +++ b/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md @@ -24,14 +24,14 @@ The following steps help you to utilize the Syncfusion® Troubleshooter by Visua **Option 1:** Open an existing Syncfusion® Application, choose **Syncfusion® menu**. Then select corresponding platform menu and click **Troubleshoot…** - ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) + ![Syncfusion Troubleshooter via Syncfusion menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. **Option 2:** Right-click the Project file in Solution Explorer, then select the command **Syncfusion® Troubleshooter…** Refer to the following screenshot for more information. - ![Syncfusion® Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.jpeg) + ![Syncfusion Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1.jpeg) 2. Now it’s analyze the project and it will report the project configuration issues of Syncfusion® controls in the Troubleshooter dialog if any issues found. If the project doesn’t have any configuration issue, the dialog box will show there is no configuration changes required in following areas, @@ -87,17 +87,17 @@ The Syncfusion® Troubleshooter deals with below web.config issues in Syncfusion **For Instance:** If “Syncfusion.EJ.Export” assembly (v15.2450.0.46) referred in project, But “Syncfusion.EJ.Export” assembly entry version (v15.2450.0.33) in Web.config file. Syncfusion® Troubleshooter will be shown Syncfusion® assembly entry version mismatched. - ![Syncfusion® reference assembly entry version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.jpg) + ![Syncfusion reference assembly entry version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.jpg) 2. Multiple version and Duplicate Syncfusion® assembly entry. Syncfusion® Troubleshooter will show the duplicate assembly entry when Syncfusion® assembly entry presented in Web.config which is not referred in project or multiple Syncfusion® assembly entry in Web.config for same Syncfusion® assembly. **For Instance:** If project have “Syncfusion.EJ.Pivot” assembly (v15.2450.0.43) entry in Web.config file, But “Syncfusion.EJ.Pivot” assembly not referred in project. Syncfusion® Troubleshooter will be show Duplicate assembly entry. - ![Duplicate Syncfusion® reference assembly entry issue shown in Troubleshooter wizard ](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.jpg) + ![Duplicate Syncfusion reference assembly entry issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.jpg) **For Instance:** If project Multiple “Syncfusion.EJ” assembly (v15.2400.0.46 && v15.2460.0.46) entry with mismatched assembly version/.NET Framework version in Web.config, Syncfusion® Troubleshooter will show the Duplicate assembly entry and Multiple Syncfusion® assembly entries. - ![Multiple version Syncfusion® reference assembly entry issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.jpg) + ![Multiple version Syncfusion reference assembly entry issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img9.jpg) 3. Namespace entry missing. If any Syncfusion® namespaces are missing in Web.config that is related to referred Syncfusion® assemblies in project, ® Troubleshooter will show namespace entry is missing. @@ -109,13 +109,13 @@ The Syncfusion® Troubleshooter deals with below web.config issues in Syncfusion **For Instance:** If “Syncfusion.EJ” assembly (v15.2450.0.46) referred in project and “Syncfusion.JavaScript.DataVisualization” Namespace entry version (v15.2450.0.43) in Web.config file. Syncfusion® Troubleshooter will be show Syncfusion® namespace entry version mismatched. - ![Syncfusion® namespace entry version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.jpg) + ![Syncfusion namespace entry version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.jpg) 5. HTTP/Server handler entry mismatched. HTTP/Server handler entry version compare to corresponding referred assembly version in project. If any Syncfusion® HTTP/Server handler entry version mismatched, Syncfusion® Troubleshooter will show HTTP/Server handler entry mismatched. **For Instance:** If “Syncfusion.EJ.” assembly (v15.2450.0.46) referred in project, But “Syncfusion.JavaScript.ImageHandler” HTTP/Server handler entry version (v15.2450.0.43) in Web.config file. Syncfusion® Troubleshooter will be show Syncfusion® HTTP/Server handler entry version mismatched. - ![Syncfusion® HTTP/Server handler entry mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.jpg) + ![Syncfusion HTTP/Server handler entry mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.jpg) ### NuGet Issues @@ -125,13 +125,13 @@ The Syncfusion® Troubleshooter deals with below NuGet package related issues in **For Instance:** Syncfusion.Web,Base package installed multiple version(v15.2.0.43 & v15.2.0.46), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched. - ![Syncfusion® NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpg) + ![Syncfusion NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpg) 2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version. **For Instance:** Syncfusion.Calculate.Base NuGet package version(v15.2.0.46 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, Syncfusion® Troubleshooter will be show Syncfusion® package Framework version is mismatched. - ![Syncfusion® NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpg) + ![Syncfusion NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpg) 3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. @@ -145,16 +145,16 @@ I> Internet connection is required to restore the missing dependent packages. If 1. Once the Syncfusion® Troubleshooter dialog loads, check the corresponding check box of the issue which you need to resolve. Then click the "Fix Issue(s)" button. - ![Syncfusion® Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img16.jpeg) + ![Syncfusion Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img16.jpeg) 2. A dialog appears, which will ask to take a backup of the project before perform the troubleshooting process. If you need to backup the project before troubleshooting click “Yes” button. - ![Syncfusion® Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img17.jpeg) + ![Syncfusion Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img17.jpeg) 3. Wait for a while, the Syncfusion® Troubleshooter is being resolve the selected issues. Once the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully.” - ![Syncfusion® Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img18.jpeg) + ![Syncfusion Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img18.jpeg) 4. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img19.jpeg) \ No newline at end of file + ![Syncfusion license registration required information dialog in Syncfusion Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img19.jpeg) \ No newline at end of file diff --git a/Extension/UWP-Extension/Overview.md b/Extension/UWP-Extension/Overview.md index 93d9c32e..1f67e8a2 100644 --- a/Extension/UWP-Extension/Overview.md +++ b/Extension/UWP-Extension/Overview.md @@ -22,11 +22,11 @@ The Syncfusion® provides the following extension supports in Visual Studio: **No project selected in Visual Studio** -![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Syncfusion® UWP application in Visual Studio** -![Syncfusion® Menu when Selected Syncfusion® UWP application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) +![Syncfusion Menu when Selected Syncfusion® UWP application in Visual Studio](Overview-images/Syncfusion_Menu_OverView2.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. diff --git a/Extension/UWP-Extension/Project-Templates.md b/Extension/UWP-Extension/Project-Templates.md index 70642fd6..b2710627 100644 --- a/Extension/UWP-Extension/Project-Templates.md +++ b/Extension/UWP-Extension/Project-Templates.md @@ -24,14 +24,14 @@ The following steps help you to create the **Syncfusion®** **UWP** **Applicatio **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for UWP > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion® Universal Windows Application from Visual Studio new project dialog via Syncfusion menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion Universal Windows Application from Visual Studio new project dialog via Syncfusion menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) N> In Visual Studio 2019, Syncfusion® menu under Extension in Visual Studio menu. **Option 2:** Choose **File > New > Project** and navigate to **Syncfusion® > Windows Universal> Syncfusion® Universal Windows Application** in **Visual Studio**. - ![Choose Syncfusion® Universal Windows Application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1.jpeg) + ![Choose Syncfusion Universal Windows Application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1.jpeg) 2. Name the **Project** and choose the destination location if required, then click **OK**. @@ -51,7 +51,7 @@ The following steps help you to create the **Syncfusion®** **UWP** **Applicatio **Components:** Choose the required Syncfusion® components to configure. - ![Syncfusion® UWP Project configuration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.jpeg) + ![Syncfusion UWP Project configuration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.jpeg) N> If SDK is chosen as the reference type, then all the Syncfusion® UWP controls will be added. So, you no need to select any components. @@ -59,12 +59,12 @@ The following steps help you to create the **Syncfusion®** **UWP** **Applicatio 5. Once the Project Configuration Wizard is done, the Syncfusion® UWP Application is created with required SDK/references and pages. - ![Syncfusion® UWP Project created with SDK reference](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) + ![Syncfusion UWP Project created with SDK reference](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) - ![Syncfusion® UWP Project created with readme](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img7.PNG) + ![Syncfusion UWP Project created with readme](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img7.PNG) 6. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® UWP Project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img6.jpeg) + ![Syncfusion license registration required information dialog in Syncfusion® UWP Project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img6.jpeg) diff --git a/Extension/WPF-Extension/Add-Item.md b/Extension/WPF-Extension/Add-Item.md index 780ec37e..a57fa661 100644 --- a/Extension/WPF-Extension/Add-Item.md +++ b/Extension/WPF-Extension/Add-Item.md @@ -26,18 +26,18 @@ The following steps will guide you to add the Syncfusion® WPF Components to you 2. From the **Solution Explorer, right-click** on the WPF application. Choose **Add Syncfusion® Item...**. - ![Choose Add Syncfusion® Item option from right click project](Add-Item-images/Add-Syncfusion-item.png) + ![Choose Add Syncfusion Item option from right click project](Add-Item-images/Add-Syncfusion-item.png) **Option 2:** 3. Click **Extensions > Essential Studio® for WPF > Add Syncfusion® Item…** in Visual Studio. - ![Choose Add Syncfusion® Item option from menu](Add-Item-images/Add-item.png) + ![Choose Add Syncfusion Item option from menu](Add-Item-images/Add-item.png) 4. The Syncfusion® WPF Item Template wizard will be launched as follows. - ![Syncfusion® WPF Item template Components](Add-Item-images/Add-Syncfusion-ui.png) + ![Syncfusion WPF Item template Components](Add-Item-images/Add-Syncfusion-ui.png) 5. Select the WPF Components from the Component list within your WPF Item Template. The features associated with the selected Component will be presented. From here, choose the specific features that are essential® for your project. @@ -47,12 +47,12 @@ The following steps will guide you to add the Syncfusion® WPF Components to you 7. Click **Add**, and a pop-up will appear providing information about adding Component **files** and **NuGet/Assemblies** details. - ![Syncfusion® WPF Item template details](Add-Item-images/Add-Syncfusion-item-3.png) + ![Syncfusion WPF Item template details](Add-Item-images/Add-Syncfusion-item-3.png) 8. Click **OK** to incorporate the chosen Components into the WPF application, along with the necessary Syncfusion® assemblies. - ![Syncfusion® WPF Item template Gallery](Add-Item-images/Add-Syncfusion-item-details.png) + ![Syncfusion WPF Item template Gallery](Add-Item-images/Add-Syncfusion-item-details.png) 9. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® WPF Item template Gallery](Add-Item-images/LicensePage.png) \ No newline at end of file + ![Syncfusion WPF Item template Gallery](Add-Item-images/LicensePage.png) \ No newline at end of file diff --git a/Extension/WPF-Extension/Add-References.md b/Extension/WPF-Extension/Add-References.md index 221b5a47..88640ee2 100644 --- a/Extension/WPF-Extension/Add-References.md +++ b/Extension/WPF-Extension/Add-References.md @@ -24,25 +24,25 @@ To add the Syncfusion® assembly references in Visual Studio, follow the steps b **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for WPF > Add References…** in **Visual Studio**. - ![Syncfusion® Reference Manager via Syncfusion® Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png) + ![Syncfusion Reference Manager via Syncfusion Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Syncfusion® Reference Manager via Syncfusion® Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference_2019.png) + ![Syncfusion Reference Manager via Syncfusion Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference_2019.png) **Option 2:** Right-click the selected project file from Solution Explorer, then select **Syncfusion® Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio. - ![Syncfusion® Reference Manager add-in](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img1.png) + ![Syncfusion Reference Manager add-in](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img1.png) 3. The Syncfusion® Reference Manager Wizard displays a list of loaded Syncfusion® WPF controls. - ![Syncfusion® Reference Manger Wizard](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img2.png) + ![Syncfusion Reference Manger Wizard](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img2.png) **Platform Selection:** Platform selection option will appear as an option in Syncfusion® Reference Manager if opened from a Console/Class Library project. Select the appropriate platform. - ![Platform selection option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img3.png) + ![Platform selection option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img3.png) N> The platform selection option will appear only if Essential Studio® for Enterprise Edition with the platforms WPF and Windows Forms has been installed, or if both Essential Studio® for WPF and WinForms has been installed. @@ -50,38 +50,38 @@ To add the Syncfusion® assembly references in Visual Studio, follow the steps b N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® WPF setup has been installed. - ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img4.png) + ![Assembly location option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img4.png) N> The GAC option will not be available when you select the WPF (.NET 8.0, .NET 7.0, and.NET 6.0) application in Visual Studio 2022. **Version:** To add the corresponding version assemblies to the project, select the build version. - ![Assembly location option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger1-img4.png) + ![Assembly location option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger1-img4.png) **Themes Option:** Choose the necessary themes based on your requirements. To learn more about built-in themes and their available assembly, click the link below. [https://help.Syncfusion.com/wpf/themes/](https://help.Syncfusion.com/wpf/themes/) - ![Themes selection option in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img5.png) + ![Themes selection option in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img5.png) N> Themes option will be enabled only if we selected theme supported controls. - ![Themes selection option notification in Syncfusion® Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img6.png) + ![Themes selection option notification in Syncfusion Reference Manger](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img6.png) 4. Select the required controls you want to add in your project. Then click ****Done** to add the project's required assemblies for the specified controls. The list of required assemblies for the selected controls to be added is shown in the screenshot below. - ![Syncfusion® Reference Manager new assemblies add information dialog](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img7.png) + ![Syncfusion Reference Manager new assemblies add information dialog](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img7.png) 5. Click **OK**. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar. - ![Syncfusion® Reference Manager success status in Visual Studio status bar](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img8.png) + ![Syncfusion Reference Manager success status in Visual Studio status bar](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img8.png) 6. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® Reference Manager](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img9.png) + ![Syncfusion license registration required information dialog in Syncfusion Reference Manager](Syncfusion-Reference-Manger_images/Syncfusion-Reference-Manger-img9.png) N> Reference Manager support is provided by Syncfusion® for select versions of the.NET Framework that are included (as assemblies) in the Syncfusion® Essential Studio® installation. If you try to add Syncfusion® assemblies to a project and the project framework isn't compatible with the specified Syncfusion® version assemblies, a dialogue box shows with the message "**Current build v{version} isn't compatible with this framework v{Framework} Version**". diff --git a/Extension/WPF-Extension/Check-for-Updates.md b/Extension/WPF-Extension/Check-for-Updates.md index 100e8c7c..01404c46 100644 --- a/Extension/WPF-Extension/Check-for-Updates.md +++ b/Extension/WPF-Extension/Check-for-Updates.md @@ -17,14 +17,14 @@ You can check the availability of updates in Visual Studio and then install the 1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu. - ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) + ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1_2019.png) + ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1_2019.png) 2. When an update is available, the Update dialog box appears. - ![Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) + ![Syncfusion check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) 3. Syncfusion® Essential Studio® can be downloaded from the Syncfusion® website by clicking the **Download** button. diff --git a/Extension/WPF-Extension/Create-Project.md b/Extension/WPF-Extension/Create-Project.md index 705e5bba..75471378 100644 --- a/Extension/WPF-Extension/Create-Project.md +++ b/Extension/WPF-Extension/Create-Project.md @@ -25,18 +25,18 @@ Create the Syncfusion® WPF project using the Visual Studio Project Template by **Option 1:** Click **Syncfusion®** Menu and choose **Essential Studio® for WPF > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion® WPF Application from Visual Studio new project dialog via Syncfusion® menu](Project-Template-images/Syncfusion-Menu.png) + ![Choose Syncfusion WPF Application from Visual Studio new project dialog via Syncfusion menu](Project-Template-images/Syncfusion-Menu.png) N> In Visual Studio 2015 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. **Option 2:** Choose **File -> New -> Project**. Opens a new dialog to create a new project. By filtering the project type with Syncfusion® or using the Syncfusion® keyword in the search option, you can get the templates offered by Syncfusion® for WPF. - ![Choose Syncfusion® WPF Application from Visual Studio new project dialog](Project-Template-images/Syncfusion-Project-Template-Gallery2019-1.png) + ![Choose Syncfusion WPF Application from Visual Studio new project dialog](Project-Template-images/Syncfusion-Project-Template-Gallery2019-1.png) In Visual Studio 2015 or lower, Select **File > New > Project** and navigate to **Syncfusion® > Windows > Syncfusion® WPF Application** in Visual Studio. - ![Choose Syncfusion® WPF Application from Visual Studio new project dialog](Project-Template-images/Syncfusion-Project-Template-Gallery-1.png) + ![Choose Syncfusion WPF Application from Visual Studio new project dialog](Project-Template-images/Syncfusion-Project-Template-Gallery-1.png) 2. Name the **Project**, select the destination location when required, and specify the Framework of the project, then click **OK**. @@ -44,11 +44,11 @@ Create the Syncfusion® WPF project using the Visual Studio Project Template by 3. Using the following Project Configuration Wizard, choose the options to configure the Syncfusion® WPF Application. - ![Syncfusion® WPF project configuration wizard](Project-Template-images/Syncfusion-Project-Template-Gallery2019-2.png) + ![Syncfusion WPF project configuration wizard](Project-Template-images/Syncfusion-Project-Template-Gallery2019-2.png) In Visual Studio 2015 or lower, Syncfusion® WPF Application project configuration wizard. - ![Syncfusion® WPF project configuration wizard](Project-Template-images/Syncfusion-Project-Template-Gallery-2.png) + ![Syncfusion WPF project configuration wizard](Project-Template-images/Syncfusion-Project-Template-Gallery-2.png) **Project Configurations** @@ -74,12 +74,12 @@ Create the Syncfusion® WPF project using the Visual Studio Project Template by 4. After choosing above project configuration options in the Project Configuration Wizard, click the create button then Syncfusion® WPF project is created with the necessary XAML files and required Syncfusion® WPF assemblies/NuGet packages. - ![Syncfusion® WPF project created with required Syncfusion® WPF assemblies](Project-Template-images/Syncfusion-Project-Template-Gallery-7.png) + ![Syncfusion WPF project created with required Syncfusion WPF assemblies](Project-Template-images/Syncfusion-Project-Template-Gallery-7.png) - ![Syncfusion® WPF project created with required Syncfusion® XAML files](Project-Template-images/Syncfusion-Project-Template-Gallery-8.png) + ![Syncfusion WPF project created with required Syncfusion XAML files](Project-Template-images/Syncfusion-Project-Template-Gallery-8.png) - ![Syncfusion® WPF project created with readme](Project-Template-images/Syncfusion-Project-Template-Gallery-10.png) + ![Syncfusion WPF project created with readme](Project-Template-images/Syncfusion-Project-Template-Gallery-10.png) 5. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® WPF project](Project-Template-images/Syncfusion-Project-Template-Gallery-9.png) \ No newline at end of file + ![Syncfusion license registration required information dialog in Syncfusion WPF project](Project-Template-images/Syncfusion-Project-Template-Gallery-9.png) \ No newline at end of file diff --git a/Extension/WPF-Extension/Download-and-Installation.md b/Extension/WPF-Extension/Download-and-Installation.md index 23ede8b4..e4a6aa53 100644 --- a/Extension/WPF-Extension/Download-and-Installation.md +++ b/Extension/WPF-Extension/Download-and-Installation.md @@ -30,7 +30,7 @@ The steps below assist you to how to install the Syncfusion® WPF extensions fro 7. When the installation is finished, launch the Visual Studio. 8. Now, you can use the Syncfusion® extensions from Visual Studio under the Extensions menu. - ![Syncfusion® WPF Menu](Download-and-Installation-images/SyncfusionWpfMenu.png) + ![Syncfusion WPF Menu](Download-and-Installation-images/SyncfusionWpfMenu.png) ## Install from the Visual Studio Marketplace @@ -44,4 +44,4 @@ The steps below illustrate how to download and install the Syncfusion® WPF exte 4. Click the **Install** button. 5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the Extensions menu. - ![Syncfusion® WPF Menu](Download-and-Installation-images/SyncfusionWpfMenu.png) \ No newline at end of file + ![Syncfusion WPF Menu](Download-and-Installation-images/SyncfusionWpfMenu.png) \ No newline at end of file diff --git a/Extension/WPF-Extension/Overview.md b/Extension/WPF-Extension/Overview.md index efa0de32..766578fa 100644 --- a/Extension/WPF-Extension/Overview.md +++ b/Extension/WPF-Extension/Overview.md @@ -30,14 +30,14 @@ The Syncfusion® provides the following extension supports in Visual Studio: **No project selected in Visual Studio** -![Syncfusion® Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) +![Syncfusion Menu when No project selected in Visual Studio](Overview-images/Syncfusion_Menu_OverView1.png) **Selected Microsoft WPF application in Visual Studio** -![Syncfusion® Menu when Selected Microsoft WPF application in Visual Studio](Overview-images/WPF-1.png) +![Syncfusion Menu when Selected Microsoft WPF application in Visual Studio](Overview-images/WPF-1.png) **Selected Syncfusion® WPF application in Visual Studio** -![Syncfusion® Menu when Selected Synfusion WPF application in Visual Studio](Overview-images/WPF-1.png) +![Syncfusion Menu when Selected Synfusion WPF application in Visual Studio](Overview-images/WPF-1.png) N> In Visual Studio 2017 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu. diff --git a/Extension/WPF-Extension/Template-Studio.md b/Extension/WPF-Extension/Template-Studio.md index 79191054..03f2b05f 100644 --- a/Extension/WPF-Extension/Template-Studio.md +++ b/Extension/WPF-Extension/Template-Studio.md @@ -27,22 +27,22 @@ Create the Syncfusion® WPF project using the Visual Studio Project Template by **Option 1:** Choose **Extension -> Syncfusion® -> Essential Studio® for WPF -> Create New Syncfusion® Project…** from the Visual Studio menu. - ![Choose Syncfusion® WPF Application from Visual Studio new project dialog via Syncfusion® menu](Template-Studio-Images/WPF-1.png) + ![Choose Syncfusion WPF Application from Visual Studio new project dialog via Syncfusion® menu](Template-Studio-Images/WPF-1.png) N> In Visual Studio 2017, you can see the Syncfusion® menu directly in the Visual Studio menu. **Option 2:** Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by Syncfusion® or typing Syncfusion® as a keyword in the search option can help you find the Syncfusion® templates for WPF. - ![Choose Syncfusion® WPF Application from Visual Studio new project dialog](Template-Studio-Images/WPF-2.png) + ![Choose Syncfusion WPF Application from Visual Studio new project dialog](Template-Studio-Images/WPF-2.png) 3. Select the Syncfusion® WPF Template Studio and click Next. - ![Choose Syncfusion® WPF Application from Visual Studio new project dialog](Template-Studio-Images/WPF-3.png) + ![Choose Syncfusion WPF Application from Visual Studio new project dialog](Template-Studio-Images/WPF-3.png) 4. When you launch the **Syncfusion® WPF Template Studio**, you will encounter a configuration wizard that allows you to set up your Syncfusion® WPF application. Within this wizard, you will have the option to specify your preferred .NET Core Version or .NET Framework Version, select the desired language(CSharp or Visual Basic), and choose the reference type according to your requirements. - ![Syncfusion® WPF project configuration wizard](Template-Studio-Images/WPF-4.png) + ![Syncfusion WPF project configuration wizard](Template-Studio-Images/WPF-4.png) N> The installed location and GAC options will be available only after the Syncfusion® Essential® WPF setup has been installed. Use the NuGet option instead of installing the Syncfusion® Essential® WPF setup. Also, the GAC option will not be available when you choose .NET 6.0, .NET 7.0, and .NET 8.0 from the project type option in Visual Studio. @@ -50,17 +50,17 @@ Create the Syncfusion® WPF project using the Visual Studio Project Template by 5. Click **Next** or navigate to the **Type** tab, then select the desired Syncfusion® WPF application type. When selecting the type of template for your application, you have two options: - ![Syncfusion® WPF project type selection wizard](Template-Studio-Images/WPF-4.png) + ![Syncfusion WPF project type selection wizard](Template-Studio-Images/WPF-4.png) **Predefined template:** Choose this option to select from 5 predefined templates, including Calendar, Contact, Outlook, Docking Manager, Spreadsheet, Tile view, and Word. By choosing one of these templates, you can create your application without needing to follow any further steps. - ![Syncfusion® WPF Predefined template wizard](Template-Studio-Images/WPFTemplate-6.png) + ![Syncfusion WPF Predefined template wizard](Template-Studio-Images/WPFTemplate-6.png) **Project type:** Choose this option to select from 4 project types, including Navigation Pane, Blank, Menu Bar, and Ribbon . 6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion® WPF components you can add to the application. - ![Syncfusion® WPF pages selection wizard](Template-Studio-Images/WPF-6.png) + ![Syncfusion WPF pages selection wizard](Template-Studio-Images/WPF-6.png) To unselect the added control(s), Click ‘x’ for the corresponding control in the control list from the Project Details. @@ -68,21 +68,21 @@ Create the Syncfusion® WPF project using the Visual Studio Project Template by 7. Click **Next** or navigate to the **Control Features** tab to view the listed features for the selected controls. From here, choose the features needed. - ![Syncfusion® WPF control features selection wizard](Template-Studio-Images/WPF-2.gif) + ![Syncfusion WPF control features selection wizard](Template-Studio-Images/WPF-2.gif) 8. Click **Next** or navigate the **App Features** tab to select the desired application features. - ![Syncfusion® WPF app features selection wizard](Template-Studio-Images/WPF-7.png) + ![Syncfusion WPF app features selection wizard](Template-Studio-Images/WPF-7.png) **Project Details Section** In the **Project Details** section, you can modify configurations and project types. Additionally, you can remove one or more controls from the selected list and remove the chosen application feature. -![Syncfusion® WPF project details selection and unselection wizard](Template-Studio-Images/WPF-8.png) +![Syncfusion WPF project details selection and unselection wizard](Template-Studio-Images/WPF-8.png) 9. Click **Create** to generate the Syncfusion® WPF application. Once you've created the project, the relevant Syncfusion® NuGet packages will be automatically added to your project for the chosen components. For example, if you add an **DataGrid** control, the corresponding Syncfusion® NuGet packages required for that control will be installed. - ![Syncfusion® WPF project created with readme](Template-Studio-Images/WPF-9.png) + ![Syncfusion WPF project created with readme](Template-Studio-Images/WPF-9.png) ![NuGetEntry](Template-Studio-Images/NuGetEntry.png) @@ -153,4 +153,4 @@ In the **Project Details** section, you can modify configurations and project ty 13. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® WPF project](Template-Studio-Images/Syncfusion-Project-Template-Gallery-9.png) \ No newline at end of file + ![Syncfusion license registration required information dialog in Syncfusion WPF project](Template-Studio-Images/Syncfusion-Project-Template-Gallery-9.png) \ No newline at end of file diff --git a/Extension/WPF-Extension/Toolbox-Configuration.md b/Extension/WPF-Extension/Toolbox-Configuration.md index 291c7759..b5d421da 100644 --- a/Extension/WPF-Extension/Toolbox-Configuration.md +++ b/Extension/WPF-Extension/Toolbox-Configuration.md @@ -27,11 +27,11 @@ To add the Syncfusion® WPF components via the Syncfusion® Toolbox Installer, p **Option 2:** Click **Syncfusion® menu** and choose **Essential Studio® for WPF > Toolbox Configuration...** in **Visual Studio** - ![Toolbox Installer via Syncfusion® menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) + ![Toolbox Installer via Syncfusion menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Toolbox Installer via Syncfusion® menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox_2019.png) + ![Toolbox Installer via Syncfusion menu](Toolbox-Configuration_images/Syncfusion_Menu_Toolbox_2019.png) 2. Toolbox Installer will be opened. diff --git a/Extension/WPF-Extension/Troubleshooting.md b/Extension/WPF-Extension/Troubleshooting.md index 189b0d07..f7e7795d 100644 --- a/Extension/WPF-Extension/Troubleshooting.md +++ b/Extension/WPF-Extension/Troubleshooting.md @@ -25,17 +25,17 @@ The steps below will assist you in using the Syncfusion® Troubleshooter by Visu **Option 1** Open an existing Syncfusion® WPF Application, Click **Syncfusion® Menu** and choose **Essential Studio® for WPF > Troubleshoot…** in Visual Studio. - ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) + ![Syncfusion Troubleshooter via Syncfusion menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Syncfusion® Troubleshooter via Syncfusion® menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter_2019.png) + ![Syncfusion Troubleshooter via Syncfusion menu](SyncfusionTroubleshooter_images/Syncfusion_Menu_Troubleshooter_2019.png) **Option 2** **Right-click the Project file in Solution Explorer**, then select the command **Syncfusion® Troubleshooter…** - ![Syncfusion® Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1_2019.png) + ![Syncfusion Troubleshooter add-in](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img1_2019.png) 2. Analyze the project now, and if any Syncfusion® controls project configuration errors are discovered, they will be reported in the Troubleshooter dialog. If there are no configuration issues with the project, the dialog box will indicate that no modifications are required in the following areas: @@ -89,13 +89,13 @@ The Syncfusion® Troubleshooter addressed following NuGet package related issues **For Instance:** Syncfusion® WPF platform packages installed multiple version (v16.4.0.54 & v17.1.0.38), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched. - ![Syncfusion® NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) + ![Syncfusion NuGet Packages version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img7.png) 2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version. **For Instance:** If “Syncfusion.SfBulletGraph.WPF40” NuGet package version(v15.4.0.17 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, the Syncfusion® Troubleshooter will show Syncfusion® package Framework version is mismatched. - ![Syncfusion® NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.png) + ![Syncfusion NuGet packages Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img8.png) 3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing. @@ -113,28 +113,28 @@ In Syncfusion® projects, the Syncfusion® Troubleshooter addresses the followin **For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched. - ![Syncfusion® Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) + ![Syncfusion Toolbox Framework version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img10.png) 2. If the configured version of Syncfusion® Toolbox differs from the latest Syncfusion® assembly reference version or NuGet package version in the same project, the Syncfusion® Troubleshooter will indicate that the Syncfusion® Toolbox version is mismatched. **For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched. - ![Syncfusion® Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) + ![Syncfusion Toolbox version mismatched issue shown in Troubleshooter wizard](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img11.png) ## Apply the solution 1. After loading the Syncfusion® Troubleshooter dialog, check the corresponding check box of the issue to be resolved. Then click the “Fix Issue(s)” button. - ![Syncfusion® Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.png) + ![Syncfusion Troubleshooter wizard with project configuration issues](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img12.png) 2. A dialog appears, which will ask to take a backup of the project before performing the troubleshooting process. If you need to backup the project before troubleshooting, click “Yes” button. - ![Syncfusion® Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpeg) + ![Syncfusion Troubleshooter backup dialog](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img13.jpeg) 3. Wait for a while, the Syncfusion® Troubleshooter is resolving the selected issues. After the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully”. - ![Syncfusion® Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpeg) + ![Syncfusion Troubleshooter process success status message in visual studio status bar](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img14.jpeg) 4. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.jpeg) \ No newline at end of file + ![Syncfusion license registration required information dialog in Syncfusion Troubleshooter](SyncfusionTroubleshooter_images/SyncfusionTroubleshooter-img15.jpeg) \ No newline at end of file diff --git a/Extension/Xamarin-Extension/Check-for-Updates.md b/Extension/Xamarin-Extension/Check-for-Updates.md index 00dee5b8..ee62184c 100644 --- a/Extension/Xamarin-Extension/Check-for-Updates.md +++ b/Extension/Xamarin-Extension/Check-for-Updates.md @@ -17,14 +17,14 @@ You can check updates availability in Visual Studio, and then install the update 1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu - ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) + ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Syncfusion® check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1_2019.png) + ![Syncfusion check for updates menu](Check-for-Updates_images/Check-for-Updates_images-img1_2019.png) 2. When an update is available, the Update dialog box appears. - ![Syncfusion® check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) + ![Syncfusion check for updates wizard](Check-for-Updates_images/Check-for-Updates_images-img2.png) 3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**. diff --git a/Extension/Xamarin-Extension/Create-Project.md b/Extension/Xamarin-Extension/Create-Project.md index 61193053..95cf71e9 100644 --- a/Extension/Xamarin-Extension/Create-Project.md +++ b/Extension/Xamarin-Extension/Create-Project.md @@ -22,26 +22,26 @@ To create the **Syncfusion® Xamarin Application** in Visual Studio 2017, follow **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for Xamarin > Create New Syncfusion® Project…** in **Visual Studio**. - ![Choose Syncfusion® Xamarin application from Visual Studio new project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) + ![Choose Syncfusion Xamarin application from Visual Studio new project dialog via Syncfusion menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate.png) N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu. - ![Choose Syncfusion® Xamarin application from Visual Studio new project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate_2019.png) + ![Choose Syncfusion Xamarin application from Visual Studio new project dialog via Syncfusion® menu](Syncfusion-Project-Templates_images/Syncfusion_Menu_ProjectTemplate_2019.png) **Option 2:** Choose **File > New > Project** and navigate to **Syncfusion® > Cross-Platform > Syncfusion® Xamarin Project Template** in **Visual Studio**. - ![Choose Syncfusion® Xamarin application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1.jpeg) + ![Choose Syncfusion Xamarin application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1.jpeg) In Visual Studio 2019, Syncfusion® Xamarin project creation wizard like below. - ![Choose Syncfusion® Xamarin application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1_2019.png) + ![Choose Syncfusion Xamarin application from Visual Studio new project dialog](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img1_2019.png) 2. Click **OK** once you've given the **project name**, selected a destination location, and set the project's Framework. The Project Configuration Wizard is now displayed. 3. Choose the Project, Android, iOS, and UWP by on/off in the following Project Configuration window to configure the Syncfusion® Xamarin Application. - ![Syncfusion® Xamarin project configuaration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img2.jpeg) + ![Syncfusion Xamarin project configuaration wizard](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img2.jpeg) **Project Configuration:** @@ -63,42 +63,42 @@ To create the **Syncfusion® Xamarin Application** in Visual Studio 2017, follow N> If you want to add other Syncfusion® Xamarin controls in the created Syncfusion® Xamarin application, you can use our [Syncfusion® Xamarin toolbox](https://help.syncfusion.com/xamarin/visual-studio-integration/toolbox-control) - ![Choose Syncfusion® Xamarin control](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.png) + ![Choose Syncfusion Xamarin control](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img4.png) 4. The Syncfusion® Xamarin Application has been created when you click **Create**. N> Choose any one of the project type and controls from Project Configuration Wizard. - ![Selected Syncfusion® Xamarin control assemblies added to the UWP project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img13.PNG) + ![Selected Syncfusion Xamarin control assemblies added to the UWP project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img13.PNG) 5. Based on the control selected, required Syncfusion® NuGet/Assemblies and configuration have been added to the project. **Net Standard /PCL** - ![Selected Syncfusion® Xamarin control NuGet package installed in project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img3.jpeg) + ![Selected Syncfusion Xamarin control NuGet package installed in project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img3.jpeg) - ![Selected Syncfusion® Xamarin control assemblies added to the project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) + ![Selected Syncfusion Xamarin control assemblies added to the project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img5.jpeg) **Android** - ![Selected Syncfusion® Xamarin control Android NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img6.jpeg) + ![Selected Syncfusion Xamarin control Android NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img6.jpeg) - ![Selected Syncfusion® Xamarin control assemblies added to the Android project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img7.jpeg) + ![Selected Syncfusion Xamarin control assemblies added to the Android project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img7.jpeg) **iOS** - ![Selected Syncfusion® Xamarin control iOS NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img8.jpeg) + ![Selected Syncfusion Xamarin control iOS NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img8.jpeg) - ![Selected Syncfusion® Xamarin control assemblies added to the iOS project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img9.jpeg) + ![Selected Syncfusion Xamarin control assemblies added to the iOS project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img9.jpeg) **UWP** - ![Selected Syncfusion® Xamarin control UWP NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img10.jpeg) + ![Selected Syncfusion Xamarin control UWP NuGet package](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img10.jpeg) - ![Selected Syncfusion® Xamarin control assemblies added to the UWP project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img11.jpeg) + ![Selected Syncfusion Xamarin control assemblies added to the UWP project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img11.jpeg) 6. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![Syncfusion® license registration required information dialog in Syncfusion® Xamarin Project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img12.jpeg) + ![Syncfusion license registration required information dialog in Syncfusion Xamarin Project](Syncfusion-Project-Templates_images/Syncfusion-Project-Templates-img12.jpeg) diff --git a/Extension/Xamarin-Extension/Download-and-Installation.md b/Extension/Xamarin-Extension/Download-and-Installation.md index 7448ce7a..773b61c3 100644 --- a/Extension/Xamarin-Extension/Download-and-Installation.md +++ b/Extension/Xamarin-Extension/Download-and-Installation.md @@ -44,4 +44,4 @@ The steps below illustrate how to download and install the Syncfusion® Xamarin 4. Click the **Install** button. 5. After the installation is complete, open Visual Studio 2019. You can now use Syncfusion® extensions from the Visual Studio under the Extensions menu. - ![Syncfusion® Xamarin Menu](Download-and-Installation-images/SyncfusionXamarinMenu.png) \ No newline at end of file + ![Syncfusion Xamarin Menu](Download-and-Installation-images/SyncfusionXamarinMenu.png) \ No newline at end of file diff --git a/Extension/Xamarin-Extension/Essential-UI-Kit.md b/Extension/Xamarin-Extension/Essential-UI-Kit.md index d3d14276..949212cf 100644 --- a/Extension/Xamarin-Extension/Essential-UI-Kit.md +++ b/Extension/Xamarin-Extension/Essential-UI-Kit.md @@ -21,7 +21,7 @@ Install the appropriate [Xamarin UI Kit Extension](https://marketplace.visualstu 2. Select the **Essential® UI Kit for Xamarin.Forms** from the **Solution Explorer** by right-clicking on your **Xamarin.Forms** project - ![Syncfusion® Essential® UI Kit Context menu](Essential-UI-Kit-images/Context-Menu.png) + ![Syncfusion Essential UI Kit Context menu](Essential-UI-Kit-images/Context-Menu.png) N> The Essential® UI Kit for Xamarin.Forms add-in will be shown when the project has the Xamarin.Forms NuGet package as a reference and also, Xamarin.Forms project should be a NET Standard project. diff --git a/Extension/Xamarin-Extension/Overview.md b/Extension/Xamarin-Extension/Overview.md index b7b47a29..6aff85ff 100644 --- a/Extension/Xamarin-Extension/Overview.md +++ b/Extension/Xamarin-Extension/Overview.md @@ -25,10 +25,10 @@ The Syncfusion® provides the following extension supports in Visual Studio: **No project selected in Visual Studio** -![Syncfusion® Menu when No project selected in Visual Studio](Overview_images/Syncfusion_Menu_OverView1.png) +![Syncfusion Menu when No project selected in Visual Studio](Overview_images/Syncfusion_Menu_OverView1.png) **Selected Microsoft/Syncfusion® Xamarin (Xamarin.Forms) application in Visual Studio** -![Syncfusion® Menu when Selected Microsoft/Syncfusion® Xamarin in Visual Studio](Overview_images/Syncfusion_Menu_OverView2.png) +![Syncfusion Menu when Selected Microsoft/Syncfusion Xamarin in Visual Studio](Overview_images/Syncfusion_Menu_OverView2.png) N> From Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. diff --git a/Extension/Xamarin-Extension/Toolbox.md b/Extension/Xamarin-Extension/Toolbox.md index 576f0a7b..7910a0a2 100644 --- a/Extension/Xamarin-Extension/Toolbox.md +++ b/Extension/Xamarin-Extension/Toolbox.md @@ -21,29 +21,29 @@ I> The Syncfusion® Xamarin Toolbox is available from Essential Studio® 2018 Vo To launch the Syncfusion® Toolbox from Visual Studio 2019 and later, click **Extensions** in Visual Studio menu and choose **Syncfusion® > Essential Studio® for Xamarin > Launch Toolbox…** - ![Syncfusion® Xamarin Custom Toolbox via Syncfusion® menu](Toolbox_images/Syncfusion_Menu_Toolbox_2019.png) + ![Syncfusion Xamarin Custom Toolbox via Syncfusion menu](Toolbox_images/Syncfusion_Menu_Toolbox_2019.png) **Visual Studio 2017** To launch the Syncfusion® Toolbox from Visual Studio 2017, click **Syncfusion®** in Visual Studio menu and choose **Essential Studio® for Xamarin > Launch Toolbox...** - ![Syncfusion® Xamarin Custom Toolbox via Syncfusion® menu](Toolbox_images/Syncfusion_Menu_Toolbox.png) + ![Syncfusion Xamarin Custom Toolbox via Syncfusion menu](Toolbox_images/Syncfusion_Menu_Toolbox.png) ## Launching Syncfusion® Xamarin Toolbox from View menu To launch the Visual Studio Toolbox from Visual Studio menu in Visual Studio 2017 and later, click **View > Other Windows > Syncfusion® Toolbox** in Visual Studio. - ![Syncfusion® Xamarin Custom Toolbox menu](Toolbox_images/Toolbox-img1.png) + ![Syncfusion Xamarin Custom Toolbox menu](Toolbox_images/Toolbox-img1.png) > You can also find the Syncfusion® Toolbox option by typing "Syncfusion® Toolbox" into the Quick Launch search field (top right corner in Visual Studio). - ![Syncfusion® Xamarin Custom Toolbox menu](Toolbox_images/quick-launchToolbox-img.png) + ![Syncfusion Xamarin Custom Toolbox menu](Toolbox_images/quick-launchToolbox-img.png) ## Render Syncfusion® components 1. When you click the Syncfusion® Toolbox window, the Syncfusion® Toolbox wizard is launched, and Syncfusion® components are enabled once you access your application's designer page (XAML). Syncfusion® components will not appear until open the appropriate design (XAML) file from the Xamarin shared/.NET Standard/PCL project. The rendering of the Syncfusion® Xamarin components is made as simple as possible. All you need to do simply dragging and dropping the Syncfusion® Xamarin component from the Syncfusion® toolbox into the designer. The selected component's code snippet and namespace will be added to the designer page(XAML) and the required Syncfusion® Xamarin NuGet packages will be installed. - ![Syncfusion® Xamarin Toolbox wizard](Toolbox_images/toolbox-gif.gif) + ![Syncfusion Xamarin Toolbox wizard](Toolbox_images/toolbox-gif.gif) 2. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. \ No newline at end of file From 232bbb0254f925b4f76e46bcdedd5695744ecc94 Mon Sep 17 00:00:00 2001 From: Kesavaraman Date: Wed, 22 Jan 2025 20:04:51 +0530 Subject: [PATCH 5/7] TradeMark Updated --- Extension/ASPNET-Extension/Sample-Creator.md | 4 ++-- .../Visual-Studio/Overview.md | 2 +- .../Visual-Studio/Project-Conversion.md | 2 +- .../Visual-Studio/Scaffolding.md | 4 ++-- .../Visual-Studio/Syncfusion-Project-Templates.md | 4 ++-- Extension/ASPNETCore-Extension/Project-Conversion.md | 2 +- 6 files changed, 9 insertions(+), 9 deletions(-) diff --git a/Extension/ASPNET-Extension/Sample-Creator.md b/Extension/ASPNET-Extension/Sample-Creator.md index edcadbff..1d92c2db 100644 --- a/Extension/ASPNET-Extension/Sample-Creator.md +++ b/Extension/ASPNET-Extension/Sample-Creator.md @@ -29,11 +29,11 @@ To create the Syncfusion® ASP.NET (Essential® JS 1) Application using the Samp 2. The Syncfusion® components and their features are listed in the ASP.NET (Essential JS 1) Sample Creator. - ![Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator wizard](Create-Samples_images/SampleCreator-img2.png) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator wizard](Create-Samples_images/SampleCreator-img2.png) **Components Selection:** Choose the required components. The components are grouped with Syncfusion® products, and the components are grouped by product. - ![Syncfusion® Essential JS 1 ASP.NET Web Forms Sample Creator controls selection](Create-Samples_images/SampleCreator-img3.jpeg) + ![Syncfusion Essential JS 1 ASP.NET Web Forms Sample Creator controls selection](Create-Samples_images/SampleCreator-img3.jpeg) **Feature Selection:** Based on the components, the feature is enabled to choose the features of the corresponding components. diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Overview.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Overview.md index 4fc61d0d..0946db22 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Overview.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Overview.md @@ -36,6 +36,6 @@ The Syncfusion® provides the following supports in Visual Studio: ### Selected Syncfusion® ASP.NET Core (Essential® JS2) application in Visual Studio -![selected syncfusion®](images/selected-syncfusion-project.png) +![selected syncfusion](images/selected-syncfusion-project.png) > From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu. diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Conversion.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Conversion.md index 199cd8e6..2bad6be8 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Conversion.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Project-Conversion.md @@ -33,7 +33,7 @@ The steps below help you to convert the ASP.NET Core application to the Syncfusi Right-click the **Project** from Solution Explorer, select **Syncfusion® Web**, and choose the **Convert to Syncfusion® ASP.NET Core Application…** - ![convert to syncfusion®](images/convert-to-syncfusion-ASpnet-core.png) + ![convert to syncfusion](images/convert-to-syncfusion-ASpnet-core.png) 3. The Syncfusion® ASP.NET Core Project Conversion window will appear. You can choose the required version of Syncfusion® ASP.NET Core, Assets from, and Themes to convert the application. diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md index 3ecc6eb6..c2006bb8 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md @@ -25,11 +25,11 @@ The following steps explain you how to add a scaffolded item to your ASP.NET Cor 1. Right-click the **Controllers** folder in the Solution Explorer, click **Add**, and then select **New Scaffolded Item…** - ![Syncfusion® Scaffolded add-in](images/Scaffolding_Add_Item1.png) + ![Syncfusion Scaffolded add-in](images/Scaffolding_Add_Item1.png) 2. In the **Add Scaffold dialog**, select **Syncfusion® ASP.NET Core UI Scaffolder**, and then click **‘Add’**. - ![Choose Syncfusion® Scaffolding from Visual Studio Add scaffold dialog](images/Scaffolding_Add_Item2.png) + ![Choose Syncfusion Scaffolding from Visual Studio Add scaffold dialog](images/Scaffolding_Add_Item2.png) 3. In the Syncfusion® UI Scaffolder dialog, select the desired Syncfusion® control to perform scaffolding, and then click **Next**. diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Project-Templates.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Project-Templates.md index c112e86c..ec37884a 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Project-Templates.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Syncfusion-Project-Templates.md @@ -33,7 +33,7 @@ The following steps is used to create the **Syncfusion® ASP.NET Core (Essential Choose **File > New > Project** and navigate to **Syncfusion® > .NET Core > Syncfusion® ASP.NET Core (Essential® JS 2) Web Application** in **Visual Studio**. - ![syncfusion® template](images/syncfusion-template.png) + ![syncfusion template](images/syncfusion-template.png) 2. Name the **Project**, choose the destination location, and then click **OK**. The Project Configuration Wizard appears. @@ -106,7 +106,7 @@ The following steps is used to create the **Syncfusion® ASP.NET Core (Essential 6. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post for understanding the licensing changes introduced in Essential Studio®. - ![syncfusion® license](images/syncfusion-license.png) + ![syncfusion license](images/syncfusion-license.png) ## Authentication Configuration diff --git a/Extension/ASPNETCore-Extension/Project-Conversion.md b/Extension/ASPNETCore-Extension/Project-Conversion.md index e7d560f8..d5c7c586 100644 --- a/Extension/ASPNETCore-Extension/Project-Conversion.md +++ b/Extension/ASPNETCore-Extension/Project-Conversion.md @@ -26,7 +26,7 @@ The following steps help you to use the Syncfusion® Project Conversion in the e **Option 1:** Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Convert to Syncfusion® ASP.NET Core Application…** in **Visual Studio**. - ![Syncfusion Essential JS 1 ASP.NET Core Project Conversion via Syncfusion® menu](Project-Conversion_images/Syncfusion_Menu_Project_Conversion.png) + ![Syncfusion Essential JS 1 ASP.NET Core Project Conversion via Syncfusion menu](Project-Conversion_images/Syncfusion_Menu_Project_Conversion.png) N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu. From 3e82b2540df3f6ae2308592bfec9d1913335f5ce Mon Sep 17 00:00:00 2001 From: Kesavaraman Date: Thu, 23 Jan 2025 10:49:22 +0530 Subject: [PATCH 6/7] Conflict Resolved --- .../Command-Line-installation.md | 2 +- .../CreateSyncfusionMVCProject-img1.png | Bin 109546 -> 50678 bytes .../Step-by-Step-Installation.md | 2 +- .../download-and-installation.md | 2 +- .../download-and-installation.md | 2 +- 5 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md index 4934c3c9..06a6e00f 100644 --- a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md +++ b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md @@ -1,7 +1,7 @@ --- layout: post title: Command Line installation | Extension | Syncfusion -description: command line installation +description: To install the Syncfusion Web Sample Creator via command line, follow these simple steps for setup. platform: extension control: Syncfusion Extensions documentation: ug diff --git a/Extension/ASPNET-MVC-Extension/Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img1.png b/Extension/ASPNET-MVC-Extension/Create-Syncfusion-MVC-Project_images/CreateSyncfusionMVCProject-img1.png index 14a279a9c4838a6e61edf349811126bbe6e0cff5..23d685a558b33203844c6801bc1d8eb3054ced2e 100644 GIT binary patch literal 50678 zcmeFZcU)81)-W9Gz+gd;4x{uSAV_F}&Y+ZpAwU`sii3y{kP;w(R2>DCra}S=2@Zq+ zAp`^xI-)2rfPjP~NbkJ~QWPm4&N%nEckbNh`R03{_kEx5_q!*5oRhWJUhS;2_S$Rj zb9UbC3;~WpOu!}p9v&XRFS|d$PA}jhK=2!ZqXPVbM-LwrIxZ+Iaau}3R8&G+QTf}` z-|1btctP*Hp{dn18&h*<3&ZnvH_*-)FF$`jV`O-Am`~I-UqA0JM0k!12}y`ZXh}(F zd4tb`z5nvD^8#?}(4Mk=&-U`10_-`)v-cR!&TD`KfCsQ=@2<4}aqQj4vuFQ-gS(C9 zM*(|y_5uzZ*w1@l-~N4H(0KOj-FIxi;PI0h)tz!w8frk3n7r0ISY5_W zz0gk{Y4~YFdT^n(HANnF6z`(fpqcg>9_+Pcl6|fFUJPQ!LS~_8De~ACT$hn;`PSgs z8Bf(PH=A=yZ{DRrX88=kyD`6@Vt2kW*U zYwvv>R0KKoA%QC-$OHbL%tL*O{c?x2dAi1hZD@4seo`P zx-YX!B%4l;>kQ$X5=w&zY9tVoX6dFwVm;tS@$(^$$GO6+IUH+ZU!p_eRU7S53uL@` z3fKt2F|e-=!RdH!tT(B@OlC|Jzs0RS55S+mR;eo`iz~2%=BFE;ww9&W7%uvceoR(V zo$h-}5T~6<5hn69){t8FW3#4vSArmeFpb=iz5%~9j+b-LTJadov8pog5zPV-&~L|P zH=FB%PwxOU$6J}_XqdNoX*r3Mx=vWB8N!$D`)sM! zz@ z{CAno|M^ScG;bF|mf!WmjK#&vHv0FMl6k#yjd})1;x{-y)wN?%87}s4yCx5?g+~*8 z_9tGrM(d0f8v}(VorGPbFfT!pH7&D^XY{zC#y2eU zS4%5v%l#S(1vYg&w~6PVMN%O`3(ER9)Ri5;fu~w#Wv2m3n8A#Nh?&ifu#B9DyA_{l zAB-CrE#&W;RFC=8gs6XTop=A>q^N!|T-ay*@e@!I2+r)Yz&d)x=0k?(lTF{|X( z;P_n}Ie_*5|E>>+X1M&W42lPZ`>Kn4z*U&y7X?APfQLNBIse1135#>{S!8UGQCw;> z5~x&Kd&0O&{Oq<1W_vS2F>b4B13I_^aN7Zt7<34)rk8g-{UBkvKDs1@C104(e!AE= z684zqufen9L9h@yvns|;Vd~LZ;Zd+FLS<34@M-O!2kawxtAA_1_jk09 zkG(jO|DQDd9aUBS&*z@#_V&M}%N29!I`x;P;#T9Y6Sg zthdTL=KFEC+9k!}^CLOqS7Pmd_dbGl(GI|d@Ne+{IGb2^CR$!{@NtUS?0C+-Ftc1- zkdl~uub}Io47+?coMs2;bf9);o7>luXV&7=vS=+xWO}AgG?p}mmYAYNR_*|_Z90>3 zcb(q?HP~X$zdR86S!b6>RP}PcJu1#6nKKtVew)b&2VAUMp22&B5nS|FC zjLCl16VmGZzH#K>RmsW}8!fF!3zAtoS~<@{A}LH~DY!}4{&OX2{jh$g?;QsZLSn>yt2p*c2`>}@LVrG*esfkqOwMmH zub-Vx7l+54`beoMo~NJ*nC*?UJ6%$}PZU_v#Y<WkcGhmDz`_Qq&f5h_K9S^?oxnQTn;jA7jQj(-3G(X zzI!Hx2``%3<6B!reE5neF-;A8dT*|h@lQcjGeRqOW=(p8GNhPDMco$NpAsfF-~XiA z@6DvI%Zz#YkmqxJps+hc%D%z&6v?2+^uo75F9c%E$KECy`|kU!4DnR)0byCOI{44T ztHr6@2SW1B{xq*}V)gRJ1Uhrg??cN7tfGue_BlOc2an$m%cejAlJl=U8$jC^S3K&$ zbm36_FFOJjuI^Sl%5=TG^nB(Uhw<0ADb5&YSk`nW7C$}eq>SVYO#^FT1H5JXbuwHe(~KT;HJL5_w3yFwk!k%n&wD#TQ7mnz11x zS*S_E{qsI|y3JMN%>mr&~0YF1NY;a;`lzV`%$eB_R0n!=Uu_i!V11{%0^o zRnW0gB3+gjWv&tT;qIz%fMM%azZkN%Eb6(F?0%B>+Q9_MX9*mVUEeB9)j5d&EHF4{ z++(qlr_P^bh)n@&FY`>>s1dCL?6N{+opnIbJzev&?Wzr~pU;NnXZZfy zi)T6-+R$a_xH)~-!cGuZvJ^(0DRN4A^3T& z$41D-8csla_-qz{FYL9yY;-xCz^zHbQV+2+^d=p#u|CYeH6ION_2G~jntmcdw<(vy zW+Qr=Ed^#>Wb9IctZkyR8PkyL?9x2zO`XY4Kk`o$QxCNrO?sU}LbmS*27$(X#41eD z6jSI09lrr?#78Gq%OcamBj>*I-t$_|!O?69a=g7*`fXW)0)?1<4RR8r^rbjS>u@D4PgN>75sJyy=ZydHR;~x%RV2zEU6S zb`Wl@BuvnpS18~&sCZ+k-?T#X2JlObH+lR}Q+=~?d38?0ehYyWWNm+Bnp$$G#?%=u zO6I`TV@Oi`K`-c__1yIEOJ%Lm1c{F^C@uGvGjQ{WQxkot;9-giJO>6=8o<(0u3pd5bv4$rG-@%qoc6e2gm$X)#Ue?|Z898!Fr_ z&6&8E^>&TD`3wCwdS6kD^H)-(d!9ZyoOH1l{^3-aaoL(s^}PW5NN4k3qE3{s+(SJg zuIgJH@v?jq)BpEWh0yKbjCty(htpby%nO<-zje9$TYqcM|6wc{#U73)vr}=|oyK=x z4!u^cOMNXXTA*uw;DuFG$rNX3&fU~8rv%=Aeycb3L_n$bQgnk5cH7K=viV3C0Aps) zqF4c)4b_xvcdowhS6!4{6+-`^gtJCBp0LGdAH0uuWeB*&-{w1#Hcxu{K|#)L37}2FL6>q zmD-2Hk33;2flDn)jia(d-i3X( z(Dvy;d=N-mBN)`hf+f({wogr3qxUVC4_>#P^9bm3K$Prby-BM(^()6;k@-{&l#PfE zSIWSpU6IH1&rpq7_=u~?H1oibU+KL1Rl>|}s^{k?@EpCcIfZfU_f^=$X0Tj}v(4X$ zkKXV2h3{8}l7)WAAKP&wkDjSdPF~ z*-Plm18+pPeuktw8`Jj`{Ce@LajiW~Wx!hkm#cOFMWJ65)37wJzj(T9^&R-HLk;p{TvqwLXOnb>sTMTT3JygwQ*1(Ko&6u^gTMb&v8qG*1@ z;YR(&Ak^8U8^dv7=HCML|Ctx={iZ1zEcxm8VE;{x&VU7G+Ppl5Q7%~{o8#gV3LDIv zopG7;(jex)Z{*@c_BL(5-2!2E06seap`f9t@DZ5@!()EoAuB-1=9PME>u|^uJ&0e{=Zn z^*-6({CMA2cYQm0h_N1+c7600_|WIp2dNtmyWFHNx=CLWUWq3$El8nNA#nRuH@#j zm}tHv2WS62K1_Z z?LXGM{`og*C-qE@?iMCogp+&g%-&q32rDr<2U6$v?lSy)p8q7o|0>{AH1Q7VUO6U` z5aB+B*IInLegPNZUcUAu;O^Jp+<>1h;53?=9A=bxLTs%aJ~w>L=Tj^!F%K+tKI>!@ zGQzh!)(g}zlCGAj)nhBLmCM*?@+wiTUg9~{OIjq@M?n*mLM78jzpLd0A~QUX@>on7NCbbrM_4<`->L?E@_Mj3c)c2!!& z-k1pa_8<|lpnc|D10JH=k2N3Lxgh{0Y;FT* zIu>jPv;K(!M_WhBK23|;a=ZF3W}iIKS6|5`g#8}>qn*+g6&Nd&K4Y}Q5&6#-S2&GZ zwVT$nHhY^Q{v-T{)TV6?SkCSM4xXC*=viH8`SH=BG3~zYOWhCOM%h)=yJE*4K#?U+ z1-2tn5!-TA-Pc;n8||>L=945lYLh~l&bx%@dw0C$K}b($@44|`CewqLM)h1fv!5(q zaycBuoC7uri^nAnHsK2v97ED-_P-SIw0j#bo)~wAZEvamsKp@iRpZO_8-7cTI{^Fb z0chBng!AAXz>tXSzBL@#2gjF`z__wrFd%73Gd%AgOVWF(s0&ek-~2Lzg^H>CRCbmI zy}=%g&WX$F+=%y@%Wc-^g=8jCfOKPelkc3y#>GhD4uG;(Yq~9;tz6%1StR1(3dwip z+$LgLEt<5`(ADV+dfG*V=gc5JoXvtFk$ss*Z)3$odaGg?s)-Fv?R)8`jURVn@wS>& zS}fYx4+;!g#Zwf$lpCG$xuwN%iN1{oxSCzqpxa%sQj74xGl0x*SAy73<%=-$j0c$(9N{_x~_zsFh?T1y_D=hpWm_IS)Z2PL~f5c&Zs4xsmRgP%25W1 zf|>Plu2y-y5d1p!Q~nI6AGLlqUw zziFSI?E`)KJm1odV0W>T3+eFO`~qNlC+q*vfA`(I?gM`c`eV`2$l)%41~M2qU-lN;)j z(~zSC@RehJ!EGY4yxQ-R?e*DSm=2OYgF=9jE^$js#U0*PEbFaZ9(9jgF#TX0x4`l( z=x88L^xTnGD9rr2WOi6fsndWMA$Fn&r4|2wr4bJLGY}>TPn6Cm#;Dn_Dwwh4(%8Yw=cIYTV!F>4`C^icKV*grT4L;9l} zQ{dT`-2Bazak1)`IkGI1B@Vfj^z&S<5oiXAlstK;jaMtJWoTWvP{}Bcst-jIl&KWOE*YLwm2knqquB|G@9U`+|5{s=2zi>*ebIgPd%c-_W^EvNQC&KUg^;B} z(;v{G_8I#nEl#ib>!*~W)>jBBd7);?%JRu&1(Js&h#l+VFa$jiLC7Pz=@+N8^}kD* zeW+v#!GLjBrO=4UkcnP`L2lz_RmJEH%HG!z1ZW~HNtYpPRNVCO&{OEY^EZFeJ3$!*&A zr5W&!WR&!FV-q14%U zHnk0#Mr8Yw>^v4M1Gg1T$(_@D&kGk3Afe)qZo1o-938z%?g;A$9~c)AYu1eQ zQ5P^+y9GhacCt3whMTQRecqa1&`l=IW2`z@Ue|^xhJ6v9uFZiAOe<6)q*?rlpVz3~ z{HYwWsxte|DAX>yH`)W7yRPv5CWXIpA*!x2osNU}1%Ak81_kD9yNa0#N4nd(Ky$A)?HZ@+=4zVb3Ti5@42$;!sdPpDKG2#a)_D+`wb8x(3pf- zbR4qI2*=$xXKR9`6pE*rkV#9)nk8?l$ewLAB{;PIo$&*#2H&MbTeMYKh6I6&2Np>x<{mz?*Phn05OIhLpRiW zWU>n`%UQ zWVXZ0h|Yzl*$wMe-;|LToUc)|S3CQEA;Ui=E?yhli2Pi8F+F&c2-P#qv3=5zE#H-% zLO}^;XMT_yDf_U=N8yWn{UAjB$mH;=7=<%2*zM}&cBLM#BoF`YR&$hQLlD?id@pOM zz`Bx4(rxz5fCzTIKDEx=*a6527v{hgn8ET=nZBIHL(I5f;qT*5&C@5ShUY37qYw=Y z(1KZ&5Ip&!5t8WV8>Q=M{4%$o@%0@MTMNpy_*FD8Js;DIsNsd^VL?%S!zVKMJS;#3 zDQ&MtKM~%<|JZ{Po=2?Dl+OUYRb92puLkr~c3?R%aSkp*WpW=0al07ym8<|+@F+^t z&v6bx*T+*klR=oAyp*ojZ(n-w6B1H%4mJ4ZSR3in>|96nMqCGwT`)9NNmq$dq4+wV zH($a$#6O_dLn9e}SH54Ta*v3Q?WO*y8$_ix$$BZTr zw0TU!(O^$r?}4I?M|(W^8TW_Bid1@7grNN7{wu)_kfD-ehL6rl$q{Zeb$aD@f=#6+ zI171w4)c?z5&d_i-Zg%6^p=&E@{A)SFPRBMvqnLZ=eJFika5b$9IaIk)pri!Lq-RR z5MG8kv>+hWla)1=nMt`zRDa!4os^K513AOxVy*iXR|&U3w=s4$99g9qB@+z`5BU%1 zF#mRiycz3Xjs5+uu^WsIJo8eX9zbU0<}yDg_XYWnCY`CFS-i3~0tzsN%6x3y^LH^+ zythm9Wku^WeoBmq3zGZz@NNE-C0ZjkacHdMZtF2IwP#+Msie-IE>}{NjmII@gImAk zL6Ja+{|$V){Y2|`xj&7ob)ki(*^yPZef$P%@2AByGvDOp4r@PqDqj&Pcj-rjh;p6- zg6g**u{D}pYU82`-BxQOI$+weS#Z3oNEFd!RcR0Om{t+KZcaUNxInuA1mqB%|T0vSL-Uvsk)7>BBHQ3ryT&T zYDww#**J47es>vV4R?|d6Ay7%HY@bVsYO})T46o?&7&bND(k$IDOg3`mnIrSn5ig~K3h&7%y)XpMVWI2QM^vavOEmKu) z3=6(1?!>^fZnu5L$S_I~>%&L2A$qnBO!$eZ^1%m;dJIq!D>z$r2oQk6?Z zzyrpq27%|lgYfn1cXPV)o+OtRjPJ<)Ro8*%_oN78L{+V0%RD|$LtOpjfox54$ z7AjH7cA?!faqzEq+fPo*4De%6(d1EO-K^=lb18>;{q%R;red`xXt)y?si z&hRmAI=-6(wPfLhn{fU&lv6KK|&cq{{6P~JMDa!Ra&+E65z#6jCN$|hZr#IOs z`3SarK|#I7M*@2&q68evWR5MvYg`Ue74) znW1Nca8=k}u45`^O7nV@W~hOq2|Q{B1q&g0A;u0MrBaRnl6Gf__DXLv_(>&81-6Kzq&0h-)k+A&UX~&pI`i*SW%mBh(3qQa2zlZB;1&7KIWA> zEca~PZ?v4RsQh_chEWMgmEvWKOed#j7ldk-5XqqV8C8v|q<&0TPg+kxsE)7tib{BF z=CtC0)o1IAlaJndtvX93zLsVLRp$)schrHxDLyetcNd4JMxSz@IE_qf2Z_i!!IOJNs)SnrmA5@Jw2Bc2C?yXADFWZ20bSIyAO4lY^LU6b`?z>b+YtdBLq= z0O56UxY2{6=k1J4HKXd;r&q$?EKpF$K3QGedgEEud1p732lwd|%nAgxB5#c(L5e>W zC_7tBs^+v8i7+DK$Zkf_m{(rV)Y!xpy9S9%#m|^T7cuLEQ@xIl+hvZ)KJtVy=fg#u z=rlHLgR)B0TP zdh;Qt7n{rlKow;AzT=fp%R1et#*`uTy?&z@P5bybx;=f<~EgU@VR`kK)COPfi zw3+=%USf{88u?SvoAfg81^bvakuna4pK4UlO!m%9ZigLvHGG$jXN|6s&?ts`6NCg3 zQ<}-?jhmEKcvf5%<%ZHqO!6A{Z5dg5aoAObmYRY%!OG0Q@s`i-u4bRkPPDH*(Hh_| z^R}qNIv&#u^2^#C)H4T8EV#jvA27)1F`lYc{f0#AZsD~&IcS4@j(=$JEKGxP^*meA#$l`*&DgphjB`(5a;-mcN z?UXAyF5%vJ_MA*wXLlPM>jAgJEF?|r03LPIAi{~rQ(0trxu>8PND8z#hAOOz$|`yH zRB!#-~3$i1$d6RX-@~< z6&eGTPFPzFEqRejQi8z{Bbix!>F4Z6USv?FIx7eiJ{tOX-l+Tz;A#wF)?zx;++(@b zLul5-Vh8Z#if+nCExbemax9sFF*Xc>UziC^JFDWMSss4_9!nD~r;dhLKI234`*2D( z7SdbbfycR<7AtN`g|+L0WA~?QdwZK8@rEYl&eg$!ofJNA=rL>m5LTn-#DSsR{9?br zxfR3q{>!QA|FA;U@HP3n)&5rI(%XeCySHM2E^iO{s8Q|gE7t`%IVX~Whm#X`_gQPg zWAJE9es+~v{!LT9l^k zkv{$=^dIx0eaJ2OK8W#Umg5V*@vq6yYt7$xn#G#maurV5(=2!s5c9{L|6l&UJ{Q`Z zbaa04+IJb3!Pm8z{CXEBkg=gZyid8Z>08fz6c7+!L(vaeD8P*kW>kze9(fVH-E0%o z*~faP3VFP8jY8OD$!7Rq&&Oh&lHx;B#8+X1xp=w6g^#yf=ofYX4^&!H7G)pLCG7z8 zLn@!k#mv;8Sri}WVMJmN#4jYz!j1n46opHE(%q0Ym6TfHHwQNtU3zsI?pIV*-bFzn zXyzEP&fDqIf*48-Pe@YkbUnu!-mofyH-)TmE7QpSCYg7$hqYEimtNHG=E}Bh0m@A4 zm*qy84V&K0y3N9_Fq|uYJkm|K8R?vdFAHPeoQGAH(vd6*)&wWma_3rFqk*Umw;&%w z%TvqhwT{Uxe*gY`?ZF{`RU5Oi4#re3J9}!T4TcA~2qmvPJxE*=rf1Ghp-UNFGhTUJ z)cZ4G?6n7zdcL-e5kvZnMUUnhTM$^u2Ek=8gLEf@bXHGk^xK zQ9*(p#Al1n2BVvKy6xCBH}s$>yELBB--qk*7P~WEL-q6>9N9mamA@wJX*3aUW^I=i ze`#s(7jCZ^yb7Uc6yOTY^curQK699_m9e=$?-Li zkS1s2@_e@?6$^U$y^IbZj0Eh6V`fC1$oz1(m*}Q+xMsDpG+thm3eD%}jt?t*`Y2&d zg*$du1dw%}0|nb`{6V$vnxiT8yj+UTUD22AGWO;-exZt&;(<;^AV&#wOaR$le?j$% zXT+vYfBJWU9!~b~Hr5FKOixIsxv1T>eucZH(-Iz`l5Us+CU)?}cxQ2HA=wRbR|&0hK>3{Yhk@1X zKbDo(mSqj)Fr#T9dFU2_Nzo_YobJ~A|Dhtetv#}?FlQ-&a4hU{;TR-;h>Ga_{u~h^Zfb zZWp?ppE9QmCDl(b99)2v9sLyx_M6{T{uU1ZR(t;Rx7TtXU{Zc?Ka%Ml6p=qAxy7?$ zad?qK;z_w?sP~kS7#9EnTZ-pV6h5?Ij(Z*BdxUfon(k?{BSRgoR9$92y`qk!@V#Zz z_Un!tqKb>tZ9bUw#Yl=TURemZ?j%)@EV(?L?oh2ETYd2y`gmp38)^%7WUmF zg6c03+pJAgzMg0uha;aT8#TBb@k2*-?!xtHlM#wp8%`GPd8on8diRqQz8kTe)42%z zq!Lq^F|O2FU+p{a<(?RNpeq<`6wQd)P=RHWl98pjQVT z4QVu7l+*4KruEy=qWh*DI5{bCjGsS_28Jdib|gQdl*Fsr&d#5|p6cPSobKmkYTEOb z-ED2nP9kDSt@+yf!xd&!S_I;pmFMN7v{@@Mr}6V1%>>?_I-GOBf*ZZqdSI|EcsKe) zm*dMOt~{w;7A!gCcp1gG&CSIF zp~Aa`Pu!VuZ%?U@jt!m|v5sUG!5D3LLNkscRHAs=byVVc=0-Ihq zX=pnWde>*pIX=Bzw4c@jP|Zb=NlXsplX+(xN``Z%ENF}vy<57?^N2~bHJ`L-;q^6F z9X|diW8$g8X|)j;a655fZ;HCbdJ;MWws0~f`*RcBP&r5l?ZB^;Uw*<057=k*C!PN) z=)lR|fj5uu`h;o%B-45x&IZ>p3LFg+5bpE3ld)D?=2F^_>0YZWN=cl34}z0qnTRR- zIK=;gVziB1@POw)&guL6CJ}xBgL-KRGWP{k&x$8y^=na4eu%7`wMR$Dn%j99Ks%;aoG@N2RUjc%?;T!}XDAr03?m z^MalEr(4}QP%Uc1QQJ5e*v}++MY$K&-I0*5IUZM5Q#vR^C&*KT&rR90<3WXnW;2{O zDGH|y^_gr}8dcuJ(yKmJv`7%I+Dx8U4Uk&hzY-Y30$^f{WN`-$>3TV}l9n^0DF zBT9iP-c?7m^A6Bc54>jBB6ImTBo!JsQ|;}p#G!z97Y|m+x&^wy_8(RQf7btY5*Odl zLy*3EpBqau;Mjt(-2RHixu%5Dq}}(W-GEFFNK(S{sb=NLNYxhsx7tJC*2pLi0S7q# zM`|5-wjxB=N2Xo$)mcMX{locc?n;O#MHKKj7jB-gsk(XY+;`P1OwLQf)H^FO>}(8? zvj1KsLEg}5uI#5n7#)#=I8zrsJju4@vc2Cxr)}T+?GiIgTzw@Tfulm`T6xOa$(x|~ zcF~E0Kg2MZz=gy44oqnnH@KZ!e&KbFxfz#8H3@7^E3{}!_Hg^jQn0`3!8Nnf3{qVO zH?cfQ4^>#HiPI3N(({q1O8ha9hoTG#7*(z}vhab}nJ?-5gG>IEaCfH1!RZ@fdynp{ zd&r}f1P_>{*GMDCfB%cKB-s2nX+tXL;JcbA0QMr*%?Ga+D3q z^0z(PM>lWI-Aw}WPi!u2I`(u-~Fei7jT zPk+NI)U8u-L3W0$3ZcfzCQI(abe=u0dPe;wtcUaMs%w7n&mTecJn!~P%p{S zX#v}7L(WZ&)Q*K)U^&U9iw6P#LQ+wXlxKx#rm~5kH&BS_cK4;8TgYIOIC?6_gDtCn zPITP(x?rm1PkwEiZi)Ke@mY2BFiua;`*)`U!IP2FW=uDX$~o0LKt;JRc3+Td>3aTFSj#Tm zl5#S5ℜGF{8&OQgy_<8#MA$=jP{hN*Dw_CJmXJhsx(x#o=5koaKsl0BNp2?+>MU zKLQ@Hw{b-xhKa+V2NPa6FaD|<9l1SmRW9}6?vHtlDDm|nKph<`f*BZ!pJs75iSwAU zr-irZ7Gkgw(6~QVj7tTx;xa5zXJSXAQfimxOfT`+^<0~Y@`@b({*{fSfBX*Mm&v|& zTng@5E+V9Dgkll?L+*sSzujbzc($W zNIH|i32w`u*0=V}p@}Ls`unK+&Clrr_>hbM&+EeAYeLh_X$gjMtjo8A1w`}%+)R+} z<(1wsQzTFSK{ka9~b>Wq9qv%R;(Z{3kjxM46Q7``38}MiZ(mqH% z?cLKhyGW;n(JTPf4Fh9o4bduKQHGAD(wc4l>20>EH~+ys|Mpph$A!CCcry z%CI-d>wyvmI&xoz%>?&rm*jm|bxnC8ZjynNasp6_EXOd))& zXa@^=5@b%46K7+=(1m53G76iPHQk(qZpvEEU*32F3`$)~5vI1$$S_P+V%lyoic)3x zB7hQPbQC|10-j0EPY*tC98y-ZYR7V(}wAwy|Ny9pb$g z9peuL#4t#hR^uzGr?r#%Q(lH&(~8f5loxZe^59V>6HoUs(VK4^r>58e!lKP*C@D0) z;-A{2brf5d_ISzMkm%8*ik!gre5x)fXP`RP^4i)+r<<6k-57ZW$gN*_|DIOQ#b!h5BaYVes#7lMVW{HHSS+5cE7o)1SACKBivLS#yfBuC3 zE3$tM-}|L_^~0Cv^v~P>0R1cZ(XN1gDmr8wt;Z$`a-8-d*T8Uoc!t@V@@htZOoLe# z<(TCTL!KqM?t6Mqh=CxRFz3a~qr9r~4Be)U-zRPqRlQe6;yvJm5HEd@`gFN@u`NdX zd46^fu(zWyes}kw#w#b~(bowlPCUDlA%2vd)N|4@`X5*9XMROTvD#3<-Y{UTa6PCjhlPZ19-oNnUutxV+R4 z z8+5#kl??KIEbW3_X7{pgmdg`w{)tJxg8pyir~ttEgE5s`#nl-&R3aIi3$E8m>Un;! zwU80!8j40QhV>4wCi>l*cM(fZ*|s0}%y;2USb5EwP~?+eLe8JBdavoQvl$Un6MXxlvS9;4RS5Jxpx^Ux6*U(GE;69cAcm_P5MehMom3D zN@l{pGE=K$irj%6C~kA4f+en4zXRy~%ETnk=NOy5d3 zJhbO;NoBKm&{XKt%33Xl&>t#Yz6(Eov1--ryUD4q)v<4?G^PN@j0(TYoS*GTE{VUP zXRdxbEcQDA<%@2RGk*A06o?Y{d{g2-abLif{T=tszHIe4?C?)7%vfW5PiGbn*%|FF zrhNCWpMn3^Euvp4Emx#!=5{~Qd+^2k6!UF`!U4Ccup_*?uS|^OZB1aur@LYq0^$ra zkB)}^>EkBnEP7NpNnVs!A3)zUzXlo`E*n1vgS|0CCNVkJ#4ATKN$HdgO!E;_ABI00 zzm-v+^I~jP`rXScifGNU9f+Q=CXr5^*~48w1m4iEnuQA>LX93VKHi* z9&oO0n6>+Tv-pmzAK2+x5oIr$OTA2E&6MkRm&Alem}7m#O>Rc#^mNPU(i*NDZSR)? z$_%!B-^cJvub*0&K5PD7)>ROl@4mVN5Hnwtu3ir0-&RYxF?+=F;K%Cft($wR?tL-P zm7MqEeQzFr`Nq!~gB`%!(v+p)XM>QVe`Qsylaw=q%*o7yM43XfS*dX;*W856or8c2 z6uxPd7*QlBTqIo}XjvTH7Q{WC0r5DF|CycIrXjZjFtRtdMO$}wws=jzLi?V2UPVl* zt!*$>*wf&E&~V4fMk%kBD#^&>xqhP=qi90V?uQ4^%Sp*?4E7Dx-Q?2c8NW@+%G@X& zCG4ORHuXy7Mwtbf>g2`94Y}cf^?Iey3 zW%gnkCE*iqtSf0oGfXDCwDMt(QI^Ynh+c!ZW6isES5(_wywDDG(>;c!1EoDbmw z3!pjIH;o9)P~Kz+9Je<5WE9Vjb0WGNf``-2_0~;zg*y8O_WnQYy$4uR+qO20T~TcG zW+jx+q<2viFhN=f0Yck|h#}HDsJInGX>LOT3IT)=LJ~qv=tV?e(}DyD(gg$r1f)sF zf4R4NpMCB<_rKq{|98LgKPL|)Yt1p&Tq`4Mt~utI?|28H_+8; zUvU3WcYZ_#>7bh=iE6pET$+p8LWb;TEd*}{C$`I-)Dp$ zd!)_P55T&qt7#LVleK9VD-yTtJ*$CXEK%O1(w@Oq!f3}jM`#ga{EG(kg@aY|AtqTl z(HF=9l>ry`zI*|q%ibuG(O+?BI8eOPwpzR=ogNOdF6s0qT+C%ct|Q3g3DgWWyF3GNbNgKDROU7>w3XI6+2aR-b1 zJGC0Sd0j08YxjkmWJ4CUDy(JSpU)G3M`0SQoSr;gD{4A=GCFIKb?*~23!%WflIiDW z?gQ(7#-k5b!h!@X!Yl@{9;6Y$#%`{G7K4JK)bdt`6StH>DGRq0pRP>_Ij`@I;oJ@P|`S~YP2Jl7Cik-&D~h9QmhYh(KVE4_BDS&C#;=2uOu;9^5u%u&-~Ez zS*KA=%VX$c+*RrWpuP6sNJiw7DY#CKwm$!%%g3&l0AwDu_Wjko=@a|jIP>a8%1s!u zvO}$dlG`TmNh1$(5B!%Ndha-s5Q_*^?$QXIOoAjxWK09&NS38_Yn6kEs%sD5pK3fE%DTOJnBYNxLq7Pp|mz1ROIO_zI5&_ZG@}sW*om2BrH5{r~h0Ey39!DWVPflZ3fkAMXgN! zrGyZb#?3oruE?*?i0;4{Z9cpR9}=z3%d@>FN#d=DJ4CzVaa#jz7T!70;d`YEXA9D3 zFmtbBS-X@o$Q^MEn}$P`;=`!*EXsB(p<#+z|C9WAt!3Z2QfC61)C z_*OC4+wF?a1gctlrh{;E?!O}CrsZvFojk+T=Nh*(H*3<9YThLJ9^TU3u1S}WO8D~T z!c;9_K^~f{aeb!e^6sCR1mWlV4#HEPW@mT$gWaW64lV?d`HY-Unu=713X`e;eAjQ7 zYNH2HBG47Z`8m`Z70IsN&ejCyh;ma=^3B-?+Jl^2epAQ^Hz1CZNaecLL|nqc2CHPa zyW`1s=134Xd$zeprXso1rrSL*cgWRm*XzRAJiR>VG%WTM<}0k*t9u~TIZiaoRdYpl zT#!i&Rkw;`T=&Fjd)k&}E~HTLZu*Y#Jj20pdjA#UD*c-LmtSrwZ|@t}-+Q;g@dAg-(itn>Q%X=9@w-REu2i-! z1m2r)m7#8nwaH39)o|)eYI!3u8;vz!RM&~x`g4f)2MTP8Khc0Kzrh6MI#T7kX_H;eenKfoU0hu4h)K-s_CaN~D z?g;_3ZH=-{Dsg)|3Zvpfei>dV{2&t|(U+VbNj=SH6LVp0&W`K#r9ZhMcQpc79OeX3 zKYL69m(US~l&eG=c;3P=y@t;h9(9aULz&8+?(P4zt$0dzGim#9AOF<>>mfMRrnbTS zO?U9D)=vY@$7i*BU3g{PzHxBcx4!wtaSR}9`E)Dq3vr-T{>wLxuRD+N_|v^(?@~j7 z`O_KBKPF6$f8P7vvx-x(KTrgF(*AJvDt>N!b)qNFq%UR$krbgWQ>ONM5wJw*D#|sp z`V39uH>{H(1uG>wpQFBB<*q6wS-EIMnUm`*o5W3gT#7qPsCZ`tlW6P;D)$>ma|_KZ zdZ77w+;-TCmS5Zh9aV7=ngzYlDc$IF5K~=EjOt@e)9(2rtC{eXlSmpp?Z{-L$HiA# zH{o(9JF=#tkGY2&k|y3G&OZIYq9~A`UVfzzYv8D4Ec|1#IrD4W&D`8+gX*RxN}y)!8>!|CZ$6|>EVYYc zSVvQvbHG|J3}S7HKVXxiN9ue({}gb!*)lgLk$gee>?)R#66-G9cSMtYsHrv3LI}@mAU9npw|L}H3vJ(Tw1%b7bt1uOF*{&^*&3B^43v~L`#K&gc3 zRojj{P7HRyt#%yLSFj-0>bkWMV_)THT>N!;tB!=+47u;zGWaqBme1-@};yYPGZcG9YVt9&uo&x9(_4oK9B2c4XIyn%=ul50s^x~ktlud1`SOVIU}*x56#LG zb+dpuT8QmIejk}G)YN_B=-&{eZb=0y{WeU!68W!n)+~n9n;d^PJ*8(-GK6c${!R>5 z5*Cx__V7CPgkDBRLUYIl1N0Ov3C$TlvcRMUjjiy#=DG8E{BVDCb4R!v`zXY@u=umi|Gc!RYdw6sDTMe>~|$T~wh!(9)S&6IE!Mf)@;VHY7L z%|igRImuSNv@!I<+UjJo)J!`&@kvh_P5y*l8!*k%%XBqKHWBPH@$r6q4?e{IA+{U0 z&p!$;BgFQQMq- zbfP9*ifLT67zbGa`$j(E@xd0w%v`wI>i39xr;443J4!2DMLNJbXxBZMVY|#KTvi-^ z6JY(_6U$kP8Sa^=$V&)CkTzuoGj$H4(E8WEoGe*sk zh~7||JXlV40@OdiRk%U^OYv#2cucyW>|)EC;mQ{wsx8xL-z%R6E7JWj!HBN-jSSnH zurZ!pH;+V};+FiRLWyF*-TCa&lk4JmsFP%N)Hj+fNuNr$o}j zizU6qdUf1p(c$S-P#NQwWYex!WCLNX#6uctyf0KY4?BshU3MH`6782!Mu_8|JsE{V zEUX*YNT@ADx`3B%(M^O!FHg0RMqO;xGDQQANG#peGFH>c!Urf?#Cc zYRPz61urXfsTFkMVfRrVg(+&^FTO!@gM&=)m^Q;FnWZm@OX%+C(V;?V2eaJVv))F$ z=lQFX9phE@*lxN%3{0RRh&qc#;XNKkbZ|q}LCa@{WHO{TItWe(-@zrJMs`Q6pb4Dr zFVNy^er5YGZ&-xfgi}}~5Es3yWVHsHyT!j2wi$Ni{3F0E#od0t{Z#lrwPgBzO?Q{W z`mHEO$4@Q$LWe)(Rh|i^;HWKz6(N=&mZg=ct=6jNR{pi+hd3xOZzVUxRc53SrJO*c zHnCB07#zE%&3jp4$3w8)=WJYLR<<1ryFx(N#LZupz*bi(U1RUeHnSNTojA?>u7q4) z?6B)2+0OF#-0W^(4b%v!)!A%!?Nn@A6%_T3C^a?-BT#E6?{9zXnw{2q!p?&!c}2&- zox_Xjt3DITjMmKO3>ttg76EiIr+?JP{$lo>7Hd}xB?VT&m z(pUk(E3xlRUo^Vp{%P-SrH9wAjjasAi#kq^r2QOMNu9$qj(yQm7r08^U@M&%(2&0l zH;XA(TJIgK`QWxZXg#@e(zeX?L%@Z{$H^P<{johb-*T4q*8ROHo)$MKekhlwM&X^) zHr;Oocx6qjTSFpG=Tb;Jyx%xP6zTex|Bh9F{8hRM(C?MQPci88KJzsZE zQL3khpS}LiVf$p zjNQEKKP~m4A@;VYLly+f22SaK6PKr=CmSlh7`UoGCEX26l*v$h8nQw6pCAdUx5+Khp1T;$#>CKbsL z7MX9IU@qt8T~u006G~))j|ay}erad>Jt4DwQ*)W#)=VUbTUF(6!`|-`wI9Rbaj!67 zdIqdhjs27BROX#(D(=d6W^AWt;Zwx#poAKjtu({`kOaR8LyZbc9^?P=@mJ~@9=YWh z+B}LCs{%F>Mr|aupV+y3sTzgAPN>zl?O|I0=&!(K99&W3-t!?@I<~Fng+`AsNMk+Or9iK$Hs#hD5JAkA6pqP4HB_ZuRVmKpJK=_e$%l*^bKXKGy3`!Gxw;l`# z%{cp&zA$$$?yuY9<<^Bkd0xOKzb)NW7BgQPYhpb4@32j<9IEuq{pg9{#W_dU$2TrCfDVEPXk?{?CVYUvwRkrMQ9`|9g+3ta z0uZ4KlI%04J04zpM+TqF$@uCWeZ zn#LOy+Py!zvB(C528;@jxZ7~vxWT3;ej|C{8Y)lz)|T0C!Xw=~JQXh^c24gMzk53{zMpYwB~Bb!&zHt~ zTwS-QF-gk$gLdN%SdYZkc6t5N(S?yWJB)B znbB;KMc5mpPed%n+O~rEZqFmMi!Iu1QqS!|1=)P2l8$!}zPAP5i_HW^>YK?*CGp3)nVWha?gf8&q~R9o}j;w(05ejamf&k z_%|C1b-Ff^B1pcKSs-U5QIM%TX?4L!7H#BLFu0yPNXezyMnB4zPn2h1ErF#?CetX|v+hQs6=#Goi&(wHhSK-Yo31aaL zJDr+TD=XngQQqBmIoPK6PffmWRg;jlBUU`Gi1MyGDn(3vtrEwRU-}Z(f@TO};RUI$ zN0W^gE;$+5Fe;?;rPS(*@|hGLQwEnME%n_661MO2XHJ_q^OWzq7-L4?ewEbR!l7z{ z)P%<1gN%6hfC!$VxOdu#v;3^0P3ofD(9SmwLxbV1cj-a}Tk6=F+ts+VLC5EDMN#F& zlvgXL&aR|;l}t4Yd6GcuNOHo*2A}=<$Z$}vFQ@pOFHwEee8MO$DMm56Wt-L&MKWn_n`2{A^oL*P5z$=< zzfk$b2?wY=rD9J!a*5u-nlrvWt@nxVkyL+|KoDXg#oF=>+i&e!;{Bu;SHY(*7`Dkt zJts)T!&DI|=cxHv9ktJs9p0O*ONl++WnK}Iccv_?W5N(2y1nfgW2-N7bemc>!d46^ z{u~Ef+c-D`p8}W#`_>hDA3)m9@^UtX8wY>&8=B zE*kpfPxV4D$&b2C6N31U%2rjOOC8MG)ZeANWu$K3@ffJ!nB|=r>PXk4AqKj|2_Vr~ zwP#P;{Lu!ZAqw4OI?htv)Mn;R>T1n2DsML72FZ9vGlkK*)~8}b zv?vVvz52JeEvYIU#c7rCsX5sEk434Cb&p5=a8-jO!&0h^RSctRx{M@hN6z^&94BD= zdiqg>+jM7f$Ew^Y9SDa?*9nOwOQgIXd0(=i_3CfE>aSaWVVrm(vPnCS=%a>zk_pi9 zkSszWiEbe)QWVq|n--VLoGdUj5?L`Fk-(lI8X%OD-k8jD*TMD=uA7 zGd)`=1U5H1)DpPy@~K%&!m8X|>yvwoV}e^+8=8C*U;bR$%;ZuvpOjZp$d4;7VYUp` z|9qxNIQ>AQZGCLGKch%yHDB!aCS$R_4Gy>Vk9;}r=L~v0{;aa~GlA)F>i~8;!x#m* z=xwbLncZ0~JJ4yFEk1qO(`NLUyku!p10<_7%ZmwibX;GG$$!GJ|I`Bxj+L6CH2ubT zrKVFQUwuE7ZclhVD~aFKT`33P2jdSo_JhOzOLuP7VF^**E628KsPgWh)-pqSV`d@L zh)cXEW#U=@Wu-esAzcTx$sU1s)v>=O*~qED3|;`? z7>7(Oa6%qF)>u3O`LPvf5co4kshrQtqc9d??|3%KB$+cxN__lo!?MPw)Gy1derRCX z0e|&;gXUQT0g6}mqgDhT_eSimzn@(4`oSL?^w*InIcJpIjp+ZLqPLb+paG!$TZJBW z`g~C|NlOT@B5NuwIl$b1_!0nXwk~{n=6?mo^uo{ySXGK}WD-4HqAjEU%HCOLsW|)& zxo9=$==V3#BS*NLYI@{z!{EJ}l?T4R9euoi-{p<*mGF(P#$W<>fs%d-{>Jg2In|H;K_CqMGvAfHicXde2aobwD%H)c zk3fQ1I`hgmKH7Lf{V<`oVL4-?JRm|;?jfPOK zeILvUD)JmQ7I9D?GorbHe84y*RZTZfEKm`?v}K0K3I*sos0{nq)W2o5abm=#il zSS1Vod7`+$?bvBuq;zz{IKHM`Y^)AQmJsf=rHV?_|mchkb#8CMwgc)Ssp< z8<*5Jrj0z5M2S+O2%ZREFAHyL6R9suNB&>sECD-wxOO?oS$sl7fVo7(TYG*3D_lM~*7fUs`6x zkR}SgBuEPmu8!!7wU}OONbN=tVECy{e-#H|td)qR5$+i^R|7uBp zuhnng$J5z+-0|e_Wx{m&yW1PtoGJI*KYM6XM>RM4-wy;^y)F4(>L+xOvYX^+8!G$^ zycSno{8jCg<$~-oP%66r8RY@FhdtCV)?9r)k5&~M23||p;5u!26j0G6_z#5vlI?$1 zA`T+C4`%(~;0GiwSzv>5L>D#v&Kh-Ci~R>y+_gW`{FTH0%y>~Y ztMKVec}XBA24)1ybRB-^rEf+i_|s`xrSR@3QwM?N)C*}p=lI=oaThj3hziMiLT1!S z*s}W)SC3n!yKC~7@WL~udfb4J8;pZ+Ea}d8zzkYO( zIpiJ8yf(Y+jt{g&##{?(}ljqr(fiLO!!iJVGovm zeZYNXMhdFf=K5^Z)AW=Sx2a(>qK94_t)}E-Dx!$lKK$XRB|D00n`yu+mEGg*0gJm? z5Zf|6xYgq4PBE{dArzxYwp^ro<$NTE51q&x80x8q-|=mx@qS*Tue%D!F#8x<iie2YUu3vB~F=1u2*-plL;gTm2rnmOJovRUACh;*nYDug&4BJ zYxJ`2LO6kU??OU;e^U^rNVyQ0$jG66>W(66B8#H!Krv{!ovU=eyJYA{8HqvUL2Z+Bug`fJgMtRA`5@lzOg?dIh1?{^0X-bp# zywFoP;1EerjAz1b*V_t}0P#Rw5AkG8Gc(ge7iHJZzv6fZcPStq{M?^4mZ(1IGZuFp zzxx5lF6aDQ>(5GJ{|7~A{D-~dw`c5;U3+uK^3*#cph>Cm51UOB!@Om|`7~n_JR@UG zkrr!hP5@gH1>oW1IhhOfB^W{wPNS?D2kucskzyK;E!`ffnQC|Y`gu=0k_dGhw{2_2 zbgeVpM~YWU=0Dd)Mdkd&q7V+jvoIvfwwy|xS-JC90_~zwf-K1hye|zx6zfsJUb&N^ z)whhz{6G){i4O@ggI15D4mGo@*_ie2ks`;?t-SR@gNswH@`w_HY2NWC2JW8g?+44q zo@y|0YMzJ`PJdPJ*h+vMNSpT2){4{e{1O(3Jj9QgH_N(4c}9Ae`&Y-i&9cvx=48Ws zQ4DN;b;-ln`o4(JNI{JT<?|J|0@L2)wWEzq# z+1ZmE)C>V7^nZAsQ5I#~6+R`#TAzsvl-oVcLoqj}$?9XrWX8BWtu=ZSaZq0(B8#m| zGNwEa8W>t$s5mcj!%8Mg^ntI7jd{wnzfcs3-&FB)-N;(fyQJ)?hKU@kmC^n3Pjavqf0wcdXCkVox{ zh7nhAq8%&c8XV@8;BOl}uP=n@sxCw-btXXIk$XL}FG#ekszCb-)_A!oQX8I{RaTy;Hg{cXJ(_nij^e}nW{f0jl8MSvLygzR45*KA>VutAd|B?s}~#GlJg=P640_5H3GnMvVwAe}obXt?rM&hGk) zQabNH@SGJWZBT$LKs;1;2~oU^I8Q+4KJco8A`TK;_P^$G5oo$$ZtR0TYw<8TDhBR& zi|c_o+4 z&d*<)8@s#j^`66R1bk7_uV zpe7@?|MicYPT#FF`<(klifRBG)1ou_)O9SaHjAzOqOUQY=g%^;0U>wirr4Zdg)3et z#xrr%f{*oF|El(%E2Qr`zD&dol&XDw*10K4_>nQ7LqLI&9$bJ98vs40mns9Q7Pelz z@%Te0pngEl|L0UI`!k3)*?QYWRKr~7gjd2n-gScY_Z*eBS4+CFYG3c?lq9y2GVaF! zalM7T8_J6N< zi$kzwLUH{ChpYUHmWiKs;s4)6xBOk3UV!p~g{{q^Nw7>x)incwmLN|Cu~zXqi{70k z#bvYj+zmSpOTv})Iv~x*qdo7h z3>op$c)qX^UTe`(ra)B{*JgvcjT2KQ=5DI}AK6=T%(0WKQIy1VwKPfg+|aUHrACYIU}}mGruQ<50?8!bHPIvG3aTj zF5G_Xh>2{AtVDQ4pn}V}ABylhEM@fj_q|$DQv8)i)Rs~}+E=IT*p-M<(VzhIRc|25 zs!|re*U^6`LzJ~y`~^6e|I$Cw>))FDSJi)`0f)jdEO6Va^kh{$;kv|hR7h-neem~> zJsJSmREgur_>$n=Rv?<9)n(}d$Nwr3nV3A?yt%0hM}kqF1nJfL*#&*322VE>0g~tz z7h~>a7l0Eg;q6yL6MJ+pqOv?iB5Ii-VZ0p_T9LN9>M#+;CUkdO=HhMfc=#zT@4?q| zPOj<~M)>ka^H<0AX5qC^%t9iBjeV6nd8C$(_qT22TUf(Dqs&+WDW(J3o$K=xTU|g5 zNj`!1jda=`b=y_ht^4`vD${msnhg}54mwy4BiqyoLdL~X13!MYokn+cr!ub7GMKQS z&mW;9{4w>~UdduU7K3$5l;>>S%bDRjX_~;*i^-5@R z^0GFtck_UnB)NM9*(gEBx>MS0TOw!%Dc8E8c#0kLsKQ{(Wqnf0b{2y%=9)QI%uuDv z31_VgosYGD|1lutk7I{aztka<(@y7@ee8+Qw9WaWaI=%zt`a!KNmYQfq_1UA)PdHBc(r%2z*d4VawnuVeaq_sW{ z@Qt_jRZ8`f93no-&W)IWGsQYB-VETwPDy?$@9J;KN*==t_@kgmR#x%^i$`ioaCTV) z-9;qB+>%kWh1QHO`b63wGa>!pTv7>H@*)iO$k2G;a*p~(zbCGm73)zVF6P7Rl4`67 zVu)voR4g_M&-4N(D`Ixg=jol^bh)9QOGDO`9V-b^NIjKe~;duL+aVh-6!09IF)@lSs?oIx z370abI=G|D87iy9r9jZLk0Pk%l>rF)7N-zRymS(j-WD@4d2=9hl<4RxzFG>_1|6!d8d&V#Y;|)OyBESKiS{cx2$OihLN_E$Hfz6KLbWk&okQT6TemJI!};e zlxs0))W%y~1;Y=o_1lx@b(jUcO|lLi zsT_XQw^^kN=7SYi-n+dP8?@1}AhRs&7)Tnw^6w=Qhy)+}E3&!IGagK{)Uf?+cTr1N zC5}@G>yN<(<=(xR?gIMrvOp?Xx~{fwN*P~v8fG9n?KRu_q(wd$^Uw20)6Twf+{tLK z7nUB}`;B9T&jGN1RR0v8w?dxy#xX4uHt_6iOX)j`oNcHKDDi3iPDZompI_&?Ue*)5 zMXZr((%@2tM?%b9QR*C4AKUZ&s~UW73Ij%Jd_l~Y5nSAFtXaI;+J}w&Q+d=c-QP1fwQg33WBiXxRKDwqAOyD~ z)Qc5X)MFq0?X)3Wc@>?D>F?a{4W;1@OWFQQ@-H3y|L{JrfyzHJEqi&MYLEgX6OuGI z)WJMg(02`f!>8*}f>K00d`3Ab{ToLT0FZrjal$4t{nST@HDdc4NB%dCwqwJa$F@4| zoNR{wT|rSzajYxUQb9%5@I@ushpB-1l|eN9UiaOPdVH_x|F)nIryKTJcj?ON4iGn? zY`gp4w0Y;S6oT8w2Np+-uCr+>$O((Jn!o?J0f1fq?P>hit=(A(8;Ui7)6p)*vdb>_ z=ezl|AfGyP4a@+N?K|Wj^W*oazfPI-Oi2%K>YkIbw}Y~20}=<{BnM@U)k{Pswlbu_ zK6zk@<#`QfTZFqroN%m*lO8PoZGlA2hs+h*jh@}gaR8C26;(*(JXATqq*2Z|b4%?P z<_@LoaXZq_)#}!GHr8Uec2Yj9`{B3|Ff^2>T~tI#xj`Cj?gfpay4jo8+7XVbAq&WP zPCM4Y$^LRI%~h(Im%GyY?W+=<`#R$!UvF4!$nxaDH`q+9h;NEjjeHR(?$H&+pahVL zIn6cp&ZIhbe!4~zLo91alB^=AOWOyZ3RIyC+#w#+!%4!Uyj$F}zHA)^l0aFJIA;Me zV)Z6N;ZC%CaA9#K2?5obt~an<%gnD)Fz8D;a;Fn|!3@AjMZ7*|_NO+5?7||+tBwFw z0GMIS?QVN?$lC|&c&J&yL~3dBS$5LcmX2vTu*S+si>QwUtErq>aX!VyBke3c-^4{s zcTMd0A2UnG@EIu$LxKqyQ-_*iMAn^tDkCpH6kAdj&+d0>V`Y4t%JDY09d?oh5pK6A&oD&S z9JMek zC}W9&>N6LEuA8j~UBoShens~-Za3Y%eiy&}GVJ3{PW8FSwx5>+H&r&3H-&(Bz+Y*n zdt>*{yP+Y}d)KCKP?^OJVVAGGe)P%ntL;}H)BC!c{5KBgHKCeb(_SEiIXkCjJMF#M z`WKzeZOnFB*hV>!0r-9O{=Bccmvp!No4;{X12pN+uhi}tta(4XuQyXpR}hG#UIgM1 zo&D5qVQ2t{`s-sy?(u&WAEhhvHCmd46jCp%MSyZT9bA9|^>-RRrM5{~G{<%0Qets9 zT9wuSh11)oL4+VP?lIE%tZQ#Ri-CI2rouwHKfFpg#PS;ei6?9=*xa>}6D#3Y3s5;P z#Bj2)B&qSGQ^q74wO0uWNCkt86#HDZW}(0M$G-7|Th9<3&fZ$B`b3V%eOyKR8a7UTZ1AL zH%qZDZtFLuMf>NeqM5SA&wFbp)Z<$nmDfJP&R0~GGD?YPO%^tbs0QO>B}1H?5gN01 zjos&fU=!MSh!2USq({Np1!k>)BCA|Ow#;P`;;_!iFJ~?nQ`}whYT|apyQggs1-Qa8 zh)TI}neq~Lbzz9tA;e??r*qa@?SM%im2^qg7^293eC0HNiUW@T9qDx9S0KY6ej>l|yTim796xtuhc?o&}sb`PGO zmVkL6shIXX$O|2Qt_OsA;X_V`;2sykV4=Tc-eND(mmd*)Eu7V)+&XaL*wIq;_D7$C zG$R#{8S0H70+0GeduXnRU~R|3*Z9gCI{ROPf0g!+C6zpw5jOSQrT4F$|C$b3m}=Te zxLfpgYXDc8-r-aQy)djxjT@b`?h6e%T0sB$Me^a~l>Rr4BA^F1@j{npra)i|7&K1U z{$o~p0`6~vHzIFKa84Q*CzLgqr?l2AWMESq(hf*n@>f5Sr4WlQFgy5r-Pe8d#vP1D3uhS)vv9>pJNtRZv zHfVA@Xx{T?>2aqOFD3y zHE`Si#5H&6->m z&y2cv?)Zf` zOdajY#k-X&OF`-6dJUbM1*yWDHqlZ1yaYrl8$&dA8|n0bs6^JNPrgSBgRx)@WOs~z zx22y=y3S? z+yS_Rpo?dGd`sBNCqK+w4 z{Fufzr;-kcGNThdsL9=pUo7aY@*TCVEQ=-P%rwhE534`pyP|bKI<(yOy5Ca`*HdvY z$7j23TRd>CnnHc$O)_ITuh1q7&Gc+$OuG3M2L*Q>m)ChcJUHp6Ze(b<%D8~BQJ_pN z%c$)%i_#owZ0{zQppe?Nv{ib-vcn(!rjU$0jM9femA_*!-->smEWj3bE|Y%M4plq_$AZ*0 z`$9V0OtlsFQPH`Wj4>!wR=bI@bTd`NXfNNggdt3-GggKFgQGg-y4MU#B@oO1KuRu#8ZyeZ@d0#i7Bp?DTH&^3_V6Uz@rV22E@0r zqLO!}E${?^ro5D#(WO+8K)&fu8}Wf)UV?xfJqxeMYB+T&2!kjt!@5FK+{_7*(?qa4 zy#VMZJD03ja}&52kh?G0BoilTfuF9`VcA3t58@Lk z@1<`4YNO|&@DNyQ-R?ktxW&NG?r|<+x?`m}y&6StRfO%@Xh4opts#7z+5hdLdSvm_4XEF0vi`In11Be8BZxw~#W*g1i^-9H4DfYA2&V z?8UHP{&MG`Y@)uWtWArJ*s4TD+6gw4c-x|w0A~8(EM+qDo7r7*6f4#V5>k0g^LM~p~Lu(2R-J{_P2xW-gm=w1Etg?CyWFKDwJ@K((eq=$WT++T9=)DZkjr*4vV5b zmu4m8+DK0S$XWs!-~v6)^uLjCY2fedxPNYEA3D!C@HqG2_eF;RzbC*P`ZaqqW*CA3 zC&@KO_cb*lH|9=~(TL+V*bLTXN4w8BjoY)gr>E)Djlp6O_YSxt7Dtgc zHq@z>H^NVUb5}sf^w1*G3G*}L=!qbyGV9G*r>dh73v$Sp8QB?3hf#t3ar>5 zoMb%7kdt9mM@JY@aM;^M=va3eNHxj2`4)qIbFw%_TJJbbMPf-w_WdCK%fN2jwzXAN z;E8&$B2*p4SVGL_$$sNdY&%SX6%k?aM00&3OZsBXZlOLkv~+fPw5#`HcJ4CEsLp5b zp^=t~yOfSmP%)-W2>Eh;Xuq3%RpqA+BDgRsK2->+@u9ldtfPk$my(k;U7T$aLa|Lf z?KWYLBU%r_X?paZsA42RLoN14_Rdvhx-Cf$r)H~(bv4qg^zDE9(0b~CqPQ2yZfH(0Ckn;p4sqq> zw9vEXcv0|ZA5u{^BPeGwV0*ZgrK%F(_sN9rqL*w8Is(aDj1S)4T_g*lP}<(5Hsg%( zBwU-!Si<64Ii9&`vl!dndJUrjwc7icCkZBf>~X6kFRBJ)Zt}gd<)L?lalIvoFirP` zjiNQNy)bgDEW-a)u^&oGsw_nMzQdvPyDMZ(tb|F5)e{JPwOY{rr5gD*rJE+za)D-g zYiz}H?Rf)}UVI@BsYKEzg9Mz4OIYnjT#gD#mL*eG$jB6x$U22lkL7#D;j_5g%fV_m>Jr9N)>St>sZXOT1=5fa z1K=bh+nS@JW+!-Q+gnqtve-%oR$SK2zDA}h?&IwqvgYQsQWngM-5NCF9NFAn zlaVp*MX0{;CQg@I#m~3Y*PkN8OnTH6ccHTxEnj+wcP94Qn<_z=Z?sp7sk#k%I!Glw zQ?>s9Sc$|rGXY^V3JyIgq9QUSe36QNon~f_`H&3`tM6~A$|=vD1=ul;_P7!&PCwAk z|I5?jf7GiCP!nJJ%VFO)_h_~!E0blRzL+td-YCDh>CTujA$5%LEz^=OyX{fF&Pco7 ztT(IO=|EoP{Hm4P!D+8U5F4zC26|bMal}0JO6$%Zr_kwlOS%u1)!2!uD#W&=JM#CC zr(C}XA09?T0_mjFtLbG0G`TySKkB`A*r02-f6(DtA-2V$d~YTHUT^=8vwZRd>Y|O3 zm4DPz<*%k4Q(8NA<=#KO8sQnEWFgi>+mCu&KQ8LsFw*Wla6zaaSN-FnPCfpwUHs#F z=VFoGG@+nmw1WE=8?l4^zc=s3@vjY4H;xwfg(>IPl2iFC#jYWi@T_;J@+Mo#HGY}3jI-?emSaxLGg_pyL33fYbWS^5g8LDS_ z_5iPjWSNfj_?SFq&lwI5fu86D3Z`9V{`(HFizS?fLIU#@ccXGh*zYAbxFfDfSzxe^ z2l%o3FMTih%ZoF~_EYorFhv&k!&hQGD?zxrEeNo8yA)>qfHB<&Jx`QCOw(rF;BMyO zQrR_W#!Z#05N>L@<|2t6jn@&YPzzW*6B`3YajxV_S|qt?V(=CtjUus@hok)Fi3VU5 zFr1yW>S^sb{8Y%=s(21R$$%=eZ}y=Nzl_Ug3~zoK5AbZ6n_LrVW~=c^4NjZWHe2pp zn{}JfFw&Vn{rp|P(hO1s%a?f@depW=mCe8SlaX}!2_k1)Mps$}duvrNqWe(R7(!NZ zrZ~-2>E&UqBwL}UmPiZ*k19ojq*T+GgRlDnc%3=HLyFK0EO>^ILy$;V^_Z-CAu2i0 zfq7(k{%L))yf$pK4dq})lSTS-2er%OqF*wRnw2BI#zcVzVNJo%B&Or1n%#A==%lZU z0gD;g<0ay$zI*_R*mLKSCt`yeZqLvMfeT`iZ1We5h0D2$h@1#^o4ZQKi6OEf>0zf%6O84{f-rXD%wN3J$L?k$hG*t#Ff3Zj> zQ1yEBsa2<0yh0Y1Qg@r&n#M#N1aXcmUV1DMY!MM^MN_vx^|wR^HLri;XjxCpn1L}o z=p&j1#w7>U>lX+5x0(|ZmhzlEIr-)iXx2uqO9%>VxOVJy6;clF%3GiHTq1)<*}rYj zNGPy`F^dyqS&BFrn0q(3^GmGrX*TryKkZ$4G~4+W&veyAJ6ffJ(q#-$I%*Hbj1Fzm zA;eM=%d?e8L+zzSpFum;RwX)Z(2xjOP=wYx)rwM$kq{)-C`w9gr440%)%VAHeeaz! zZ|0rz&O2xR`+e^{-|xNW`@8phzRSIz>qDCk-C?ShKX|!XR%`Kle}8Gb3EZ|8Uqxnl z%L>_xg3-FnsYDKwX~bhfWT?qENOl&eUgx2#xt1S}FIn_2rjd`@AWL^UrdR4Ty2Ln- zK6#>-LmZQ86737U2P3rWwcOIc_X$1}TK}!H#zVCx&ubcLIvv&7 z1c(XM?pTj>Vd(I7_&I*(gI;*0qwDB7@mOx0UGCirqp)dGGPj%B$i0&N*QZITC3FW8 znqreR6VYZH)@7#UOW;?Xd+Ak@S|f0Ue`TYmm_y^AMcKd+wFlX27xvV>o+fSAa7vf$ zH(niU_O5))l}nCih#%Q!v1Id@&*~d*60uAu@fk}ayl zg|fLXAaT{LpRDiE{^|t{9p1Z7!)uB;1{DdX%XMMUpU9co>%Rxn0OO z7r;LTA#-n+C9<0$Z5{2qyP`N}DHvxIXUQ<6K;B)`5dpF!n`dB`Den#%a8+7ZE8NvI z>y|U1O@FtP{l}lGjq9Mz=o#JOQ*UJf>@uY+PeG7W{8y_ldEar@B$jvCXxPIg&S*3YLH+Pj92Y{h9gnLwT9agYW0 zCF|AZ`q_!cb4OV94q-889%0+kEa4CrmuK%DN~(ePS5jHZLq}m?0F<8Ta)jw=RXGKZ z9;#1H&Ac=`pBJr8b)sN#s@Jpy$CFFuFyo~3B z{ZT{1DK|S80lY>Q#3{F+a4F5RdCBuwns?fN3P@lTvylVJy)DwKmqUK;f!DO6 zUqP%Cn6e9U3&Wk+?o&*78404(I|AcKi=QbBB$d^jm6w})5T8l`viRXAGh}0U!;q=CkgQ2=Y~i#34`iO$3h*nnFTv1^}(HkG`;G&xen#_ zmk^ya=~P`Q^(p4Lr0gzBMSWHxoJHf~O{cJ7dif#Uup^8`rVKD2BRtHq=#!jE-S{in_&VwlxAknYYw=fgfv!;0`zvO_d$Ky zkYP5y|0V{7e7{y6;+T8>?!esS3qZ8xk0vHd0V#1kA9V+=}(kVn=H$KIQqR{GP zBkko{eg|vr@%i;JWd4JfgaG^(Hao33+ORJl9lJBuevR7i001}!Q^5EyjjUS@ZY7JV zOESy+2fb+3aAp%HA3D7<&#QG<9xpUPkp3U;NGYy#HKmZMQ>uz42)yzO@fG4^FlDD(y+Q zSEfg;t0@cw77whn#|b@TN+VzE01)3-tgrrmlVpsXfHXj{lf5mDOiI^OYW?PudHiF| z&&YIc0?Q96gT3FX=A5GDr5OM9ty4n#g~MF`%K@=IZoUQyS2M`J0ND6X!|ogs!H$F1J9gqFbNJ*^s z;t=gW?nlB3?_2?Y@x6?Ws(!d?uF`1k9E&P$d6L`=%nSUGpG%Q=SoZ}zQ&(tzljih08fB*%Sx|03#8QyzX#%Bf!a`Fz_@ z0h%up_75b3Th5l9{+D;gIzYAddLr7Aox&!_>Lzzs;?w?v9KCT7Nmk%$)G+W4(!+Jc zO$u!o#2k|!dByZv%=Kpq?wc|C*F5rnS(05X`ZzAw1pu6Yc26017rmi0>SS~^ke%f< z7)M@KnkAY;l;y6KQOCZ!htp(ec30gidQQ_@psj=2t~1S>kSo_&=(oDSt`s7OOQ0;v zzX((d_sTyB!`bXhAd=+X3@$a4Fi_Ck(Ut|>LFthRCj(+u?96HSXQU{;Kx>>gUx zO$3u2$$pTq5d_BWkqG&$3AUuwajk1>{YF1Ua4hGL!?y+ubvUf6SZQn;A~8?R+jMX; zI{fgrTnZ4+tziYxGBuhTBF3t^_41Z3&Xev_UyY1eI!~&@a~+MRBhm@aBEqv(=t-+T z;TH>xcrUw^&l8FJ(fPHZ#LxV^5q*!_lGu3_*YL7hGY8lND)MghttyU+nKyac-3{rd zBH=__;iwd~Hrm6*Cuw>0H~{6{E)D;xWhJYWqs$R1h*!iyAmYbEQTxl6JUAKTKD<@e@mrx21L zpga%-Hz=R4^O~svP zoCJc6z;V2|w*>Yeg=vh$yHSi92gZU@qYQ=dt*0?D>mbBB=*Hia&|3!;{yXV%;<#;b z;cJ#?#B5fBNI$ETA}`-L%QtU_S?tM?`gT+&8L^ed&U~#2!>k&|EWf*jKU`IKC+Rs= zZFxdXcs8Sa%@2z6p$B7)U9H9k0}d1@pJtR(lqPm_xTCKcZwp*wvKM5F=qOjG9B@UB zJTj|4pQxCzJ9P97@RR$vbc;|Ld9th6@cJn9>HW$FD<{ScvQ>Ono28&t7mJ~lQ_YUT zn)~gMKze@cwrZ$OKR+?Lvx;tK+015Y`HvbqcWiUnkfHcN6|bbM;}M3obmcQ_y@=== z=`{30R!Sm{($W{FvoZG8OvRzuidA!6>kl+tcu74fa9`iZ{8Q55Pv1w=S}q{q24Hu= zAP27@7Fz~2Nm?aK9n+@w4ycNS=9Tm5^%W}!brAFet)TS68m|qsXM?oCy}EgWw86ax r`m@8Iv-H7Q{xppZ5Bj72z?(KD%S+q^A`Vj>D~1KONq*jOV!iKI#xVe? literal 109546 zcmce;cT|&I@IM${3o6YQ3rLID5D-DSw5TW`RRO6&Pl36V|+fj|;S-Qer@x4*Oh?4CV)_MXF&`?UMa%q=tXnL9*1(%0lT#dit-0B}6i zx^D;o9E$(|j>w!i&b-3i+WC(8!{TG8c@I!JD6q~vIqG;7A*KpX>{6T;FcsTg(o;_T_1nHO`D57UmG zTCoYk4@G>GAG~!=_4TOYty{9JS4H%^pYHfPdgJp&=>s^MAgQ1JPQFK+H$6=F!@Rqo zhEytDAkr>&J8kk@tvBVMVc*PPt@1vT1RVO+8kha6};g*|J zV+h%C{>p#n02>ucuZ0mOso?!xnK`$=7h3{k4-!J;c?Z46{$6>-epib9Z~a1q4e#Ho zG<&Pm->Mz&n`eKk-BL%}|5iUdI}yS1U;SeHY4#)kRqsRy^Bzi+SzfWL|G#SZ_;NIu z`b{@O>B+t9N4X_W>qaF81cK(_bOLPN*yUx&yhrW7|MNNCL>QEY!LJ)YEjWc#uA{xo z=sQ5hWBPg)U39Sx&0`&K7r9dkdU#u4lJMtE4i(-|ztj{u9D^BMbLa>%NlsnHk%NBc zsSkqSwaN5d=R_F1sD|<%3xF6;z7wFmVRb_b3zveF8|Kf$o^wRX^vt5@eg_khp_zt? zn~`nx%^nJK$5FQXDO^4Ej`RE9cl86^pi}guwrW~@l*-GB@Z{K;Go0IR2)ADR_^;t^ zCsXUdJpSl3RY>)h+diFo_Ho8-=mgHU6BonK2HhfR!uS$Oa?j^($v!m+12v+)Pg}ee zS&1{HrvUnI^0uU!d*|r)9p7n;#(!P#s%)i4BrA~wXV5&vD)!EE#z#CdN?$~9aum$46Q&7{N?Y1iN(EpOm48K`rD}@j}=uc?mbJ2h#Z<1FQSaG z)$CyKr8e`ZJMKuwl&jw-Fq82m9Ge?t&MPrU2LC}G|C0pUYlW$9DXc>Z;}!ldJy!*% zZ-&+_mtL;Tth?3#PY0H-9+XhN?fxZlME?jHz8?+$$@R5iF;01IuKz5MGd}r|S)MTO z zlts2bLFf(XMMg45oM&>RgX)=Sf5qY^*g(jXQzr>@4JW&p70@X$JH>GQJGmmpGF2g$ zvVW?*;w(dNJDq&{#Ny2}OGi>q*HT84+Pl)n&GZ&^e4l~JW%zz2I2PeX3Y0M14B|&o zLJz{Jh8zF%Y|~LxL$#gHTNDNELi+Y5*Rtgf+CwbU>Y4(`j!5d)h??I!gV%k!P2Mc0 zELq}$b%|XQoX!4=p^`@pg0e-Q7VK;)Rm5$9R%%JT8voe**MBjO!3;8DIXhD5(pkCkX+7Aw-P<>PQoU25hL?7i8Hp~prvJx3L$WpVB7*E_&uq90Y1&-XP|6iLnUq)uyz|`M7^TsRMXHQWy zbQHg=*qDiH?{j^FT&Xs7o4&UrCUxaT%jxCGSqd59ej(~li)x=eW<8fus(H#3AWpR( z&)?!|+znJsUOt11FEZN9_0A|nvi+snR@*cCr>AUqyE9kB11jqXO*;R6cn0pAaI*ca zz_p6xx^zj=X3EgtFKNJ!Mu#-okzJws_lwyU3J=ij>fQgyE3aobSv zrBeD<$fXxt&%`awoWty+PQIE~N5z=eu>0O{`|P^^AONm%jjLziwM8ol8=^~$RJgV! zv8l7Hq;CWIyhXX)!vMk%F{(q}tuT|RheB36k zXC?8Zq|}-NULn~{X{fEudkV(^QS-i(0S`B-Wu;RBKfiKjDA`#-zPV|;H8Tl{ZaRw=b5$u??vVz=fSmO?TDv7 zvCQ`LGga0*I~CqMv!S{Ml#Il(06NoBYm)2AuK%y6kL6v_P|$t|;FV;yW3zdQ$)7Cq zAZ1}^C>1jjZNtmUpxW#=`J)^n0k1}IB13SONG2g4G-wp%|Klpm_W^fSaA6w_uzZy*Q#yL^D=R~jepASeiTQvupXF|4a2jY7~mPa&! zNdyd{4^GFxd;28eo0GhOVPaQz=Aog6YUEX}T2VkZdsEU!En~Gysm;CGkF+nTUcbr` zqZ&`Afo9QQYT(AQ|8JUC-zWS$E)<~`*i7*ps=t*GAG&6(uyU}b2@=DBH)&98w4{n8 z*qm}zxwN!?L+oG$M6C#KXy@)dRae&|VM%+UOdSCQcXCdk$AlsJC<>A^Colx3Vq`pY zmxk1Wv-ox9HP!I{LXe+ery6cw!cqEQ)96lLu32FK`}w>pfUi(a0Yw`Ic&|TI#zVh2 zRmQQG6|{f14&N(2|7DLKZ^#`VLSU4kr2rQL58l~b7iR(Fj7=a6Uf5>3mezIhuPdJs zI?EAAneBCGo_A*s=T{?l)X^OL@>e+CK2cW>3*JpfC019&M**C!rjwiAH#>$0TG zUqgA7%<=)GEE1D-lR=aU(5Hu=u01q2PrX6k6|1pxavnm_tIaDM>PlDug#pWjPs%rn zl$X2|$q%DPTyA8D1LBk8PlUSYL5`Z5nDlN;6fKWs(JLEQRdET$Hzea!eK!(SC~kXa z+%G?Sly_w-l%ktzsPu$W4wx7zM9*>-7yp;;T-9j1%r$3h9MCCN2>GF%A0AQLa2&Ar zt;UdhT~q9pl_ zZWl4l7<$9I7uN*yu0-6MqCOYWMpGorMWgKAv$aW!#)9yoS6MF38%kXLmlK%0+Dv>B zxTUo@)X0xJh*432mZ$TX^HqmZ)`A1~Wk}siEL2b;G*;PTzjho6ZAi!5Zd@$FSFOg? ziW(>e=k!DOWu&3rjCi>5!NP)gEx|BtkTaC!g{q-T`<0Dc(d?=!Aee1RWC;SPWOo1n? zLg#H}Vb%c}YND82JT~i7R_rJ|`E7f{a)PpB_hryBED)e!tr+~MnO1gz7$49|Z281G z&vya`mh@j;($at9MVacryt(#!VJ?&=Wk-%~}(xJILVgRHIm z`=O);R9zWbVa>+O*#Mn=A~Nh=cA+1Z{r1$a*$KsPoL6D#^ZbN_`%idrYyM+rFb)ye1Gs`oO=`3WF+DQqG-9T zUfMcR#SxbUh*;3nW+wo!Q(3TW#1EH5zZY5RVSUa}KO1DA7atfV&&jxc{?xoUzp}DD z#xOze9PR^w!b$}7`VXufBxDGW)fxnaK04j~6f}p=4c=2Hbyj}ex36!8!Q5H3Nfbw5 zvt)i@bcwK~%X29XfX3vl+kR8AagLfBdGu{TXhmGtyAsF%%?-@*_7Y|} zNTH;w5C*#8tr-}f*|xJ6%vf<9>iM?%RqQNX~XFbu71L?UDMxset6AwU6jX zHZ65NcfL;DD6*!33CT5$9kEwUA3uHue46rZ5V3qDVbW&5tAP%4gZdS5yu$@kfc16j z*=X#?$Yx1=vq5iHL2bO-S|eBSnS)Bw<8>{;-;&s}z9g$vEU8z)gYK}GGcKtjOvh^5 z1H~#~CSpYonm2K_G}fgmh7WitXADRGt#&X$GVLi@i6ng^Si3Jl8NUS@*Z~nn*JU-4 z6g3%qj%RlbR~`|RNbZtg#9I@&Ed5PL-&chWE>9a2HTm}M*RWDG%T_*vrf54E!1uQi z-DSTATN&zEH8&J9XMBk%M1fF-p-lODB;IX-SJmYVs>zzzu#9$0dFZjFYfgL9%~mS# zU{D(Ou)^Z`bK3lC>_2_Rc7ZmT+VZFZu5W!Abr$`?_C^mp;%Wa}UhV@2-pfy9IFIJ{ zMQR5I)-^(Rj@**C9-3N;!?@07i+T^HQR{RZ`@|{?si6))t$ij4b>rh*9^)3F^(s_Oi0dI0O*%dCs5j z)l-!N(TE+C|Py?FFIyX$r8+l?o9bZ`9hNA9q5r)U~Gne~YgiW7DZYd(dl5tI^LlzvdlxE2yBpof(T28w> z9go|g?-Mfe@H;Hj$2ZQBUr&?764IQoi}eQ4s-}#1cPPF9SlLDP3)VYG2KEge-v$1% ze`5ICfupMYf`8qu_=q-~6vHaPm!nkZMOg8t32C1?M3Lf4oQ7xS^ybYP{Z$RptvzfN zzA3&ourzsRRPS6^=Vpgp63XlMs`=j$3sj5nsTR^h}nrk`c;~15yweKQ1_FgU<}~|FtI{ z2h-UkX{i;f`q>iwA@SUtjHx%XM_I*2s&dt@zx)+J2pw9>ZOR$wxXQN6lDk4Z*e!QO+*G(aIzKOgIvDh~ zYmeZ-Z&nQTazXdi3*|r}3=I4m^u*XB1rP|ON08v<sSKnJsq%b#SxNuE^O zO(47t&86kOz~z4A$<7p9LyeZ5ud?k~UV7<@Kz5HWkFQ2WlWKF{2`!75IrMA z{;U4Jj9Q6xLP%^7jj~)84@>4r_DEVa-GCn5Q}IZSq?<(l3oRV7_{GOZnH7a=;@MCT zrO`!RUQh0~?d=y%!KtHcqjRGbtY*OvBgo{S8oRZ`f#8PVrOUu5XE905+}evO-;V=w zI_wZ&dPoc<$0jtl;tsmNf#R&+hh()~E8#0>6x4SN0iAcg$JyxZV^&r#GS2 z7x(n+yz3HK%b#)-c-FSY9IXqpAWR75smLCMugX|+ z*~5=P#EST_9Y=WCIo`?v)RGstbXhqCJ^&f}U3eyi55-8e=KV8cGv@`TZ{ z!ul)ewRH;}IONdJ7!zv!5mAaug{F7MXGTki-tr-Tg>1OgQjz`*QLjE0t^{zf=61x0 zC^cu|YT$I2wq3!Xn&^J$jZVJ%u`y^aQ`h)x5Y8)J&PjbygmsSijVX7%Vog;7H}9%kOzw(m*Ja z+$fAaX=TapW8l%aDwD82GZSe~w<~A2slCefwo1fn``Jr13E*RMb5SVK5xTOnmqmx# zE3qr_A}txcA0pb+LOwQQ^@zi(&+naL&7pvYgZaF{IefZPLW7Ub?y>4k4~KP3&j z5OVNlPq3TB!d&XDy+duSeTfHkL3jN0{p*=lzWc7W8=%JBB5 z5+`5me?Gd%4e#^_ZeaMqG`0s*ntb0ZU(txRIq{|VSBII;74ukjK#2DFQwCoYAFB}x z4SJZ1df>r!B6z3eUtJDZYCkKM8R`0z!h3O zS-p*^qmWos^W;N&AV5lgtw2(ZzU~B@YpxUs9*B))X9x#{21aEu%z$@-;u|5n5H?p; zw4^(C9p-ZM(n`yV%f7*jGo6r6S?O@ed3iJaf4Z+Qum+4@u^dfBu&m#mD*rk7w;`l0 z?Blk3zAqz|=IsCUv^H?+{0rN(1_(pcFa*q^$Q^by12?DgS0&wMKRN zK^=NsPQ|Xjg9C8{_iE=`&7*(={IWNVfSBC@(HB9p*Qo0!Y_7~uWp7VJ{8ns-1V;4-xfXa6O<8rn&}3l8A|K9O{2pG zkg|XnX$e-aukFZ!FDed5+7B$?TBWXYR&0GZS_XUQ^He%xGk|%|<#kQ*1P~)9#WS<7qO7NROnqt} zS1wAw8c#~rtp*OI%Q}BdOiJqc4T5>=Xz1Iv!5XN2KQWbTnIT{QX{3KI(lr&VoKo8?G ztDqR{wN!=H)5$%mL9DKUkwd{$PD_je{Tb86Dfq`18dekgQwc5YE0ssz()Rb_>0*9@q?X$a zjqxG5y|A~`8AjdEmI$xLkruBq=v;k;QnmcgLpQh>$@lR>79E(dJwexXHxo%(adeRq zpdX}cC3(sQOI5KB5O(9AXAgTW@dMvUuqEyV;OIc2Z~zouZbIx(J!;&(EmhFzFIsks1y&)+!tZ#^yapqIHQjbEUr!vnQ{sY>bh z$pmkr52O#4JvEbYjdb+53p>9b!(vwPXVW~CdIWd8MJ-pN^hN|e?%+bIr1FyM3(~@@ zB{)4bUAJxdn?d+fyMM4HH*s(vd zP3(We>$r$7?g2hrD6i*+I{1Gjyz#6HtmluO$WZ-RaMD?d>hH-A4^-NUw?uDSE`I{; zn;z^Z?jNu&7gBIZa1>7lFtbd1BlA7&$n;RNqPhtdJa5}PI(#4~4qb>fRS{;;J8t`_ zAhSh4SCYW+CoWJaD?0iJ<`NfqoON`9PR4N)^(Woc@X*l9HK7|90`ad4Jv{ar;lfcv zJ*0RB)zfdE>7x56vzN1YwUJx=d+H;=J-z8?a5B_Q>7H1K%a`PL+d2;eo|T&FD4NM% zq6hewxPE}oD;SAcM{#^5!Qhq-$GI2tEcxv^Qyh9XW^1%pJ0Vz=5>o-VRezvFY$;oe z-2b3n2a%gz#pc!IBES6{=zfggkM;s}`CkOcNeX=#ob|$1`s;@px0P9JyXH0UISySU zDFs~79*YsGRtNAFM<5zODsa-)?532FGj8S(Lb)yPnNbp{A|!y^d2-+qQl~<_Ao-c~ z10ToRs;-|z0h63tXX!n=NRbFfBwz6JxYhq13C&UE74p3F%=_a)tz^?NCM;T@%MrmE zX2aX^=n`)npTXT9z?X;=kct>^k2S_GRIymY)&On%27MP4%n5jvEnQg^#}ebn*B1Ie z-tv+4l3B1t>AkQ88>5b6&-gbv^H~59U9lu;oy3Km30y9N#lKz8RRJeuy1Pnxr11~$ z363{%r-fXXFTXj&Uvo_Q7&T%9i!Q)vsgTYL{78JLZ2qwh$uUCY#|U_j#oe3G{eNDS z-2-|lFwho-P2j98scPrg-xejSx~%LrEwZPDin4z)aaTZ$l7-qm;P2a?xw!$-mP~&L zo6YZbcc1z;)NdxgEmJa?LTU)7y<9~50Hlc9+qeG!qX57iu0tR-^jnt{;HyGtJUT%m z{uyBXH|dZNRpza~kKG?WL};U!aO+{QDL#DuzhZZYB>z|bzlcHWI`w?KipGwC#3gS^ zzNi2IntC?sH#?s{_<{Mfy+o-0DL+p6)kgxxW^jW4r|119whfoaO(L+n zbeu0##K=3Y;lJ*75lSZyO$+~NS_>}B5n+(2B0NMxxqFEDqSe!vUjKpm1cMh&0eCY$zHL*>U{DDY z)s6oVqXiRYi;z2Oy%WW_8JVVO%4G(3yqPTnh$;58B9tTs9mO13S5sK0cpPrb0045^ zKOAk(kvm(>gxKKx$6o2mxvq}UT$=Cq1-bS(>7n1Z@yr>c)D(75Zg&nhE!b@Pm5L>Z z8s%#}>=Bzzjlh2fbmmvGw&y6FWr|2qf@7!Wx8uC=#!F=h31;x+RauF1`#pYb;>39m zCvVFbceK|hH?y^4WjSc_9^G`}NpJp&12e>!6qxPW?h_I& zQ?$0d>i2CAL5`0F7IXIiyj{poh&w}ICIfac+k;OGEtE8?O*RwMBRL;f?B;iP#G>=i z*tinHr6jh|^Cyn*HZYxeE=>dUaI-~W@%aNhjDIO`>`~G`j>+QZv>ui+mH4zk&8zE~RXxhhOT z9oswb2}a`cXPInt{&4QAd2nQOMX!9yH~-X-#pQiVP zPj#HEvG1(Gf#&3R!BcvlmS-(;?PtAHHJVvsPBI_wOM97oe{@yv>{b)gSgcv>QVpVB`GH7fJj3IlC;tAS>*iF8 z6;HhuBnps1N+>t=SJQ{@9Ke(@v=|5myS6|@9qCm~?8|Btx$IW>a zarb@ShplcYG_i)7M^{1A%l)xm)`A&kFG!-(!Hibl))2}^D}#7ENh?#aYXQ@O9^MSsOw^-A4RG1zCxks1&^7F(fP(5#W}J!VvBhcBgQ?G7SI&it@;5&Q9`+&zH?j4%dI!sC$U!I2Ake8 z!CU)D;wcY$rPqQgfM)~eB-_iJ%T!mNDCbc2O5Ll+`{x8id$O06_Vis2-mk38mpho4 zIh0Jhr&Ns(?#k=F2A(yQGuG4&-KXexaxH|-I?X;c7kOfIo^Ybys7?d0F0)`0Q2Dm) zu7%Fj9lb z*Zdbt&%8o$$im&cZ*%Eam(NK%}gcYbh1FHxATK$*WUrcF0qalR0()wFoO(U9jP<~(EbwvZa@#YLyUcMb70t2XI> zm0<9zB8PJ))M>5u+e}_XDWddvgEFX1G3uyI*g{jT*C&OGIQ&Ziiecefet$N~KNB{3=bx(V1RkrT6Ze?5!dAOBj{bJP!Rp=1OC8w-S!0 z%97iAGe2R<1k4@5CB~tmK{v2vjZ4BlnSc+ksjPj+`W`r4FWzM`{b4$P5ca{GNOCsS zzjS)jbCE+wv3fXf__;;b$VfMcvCjS_vd52 zxwS{z?f8KtYiD*#am7-)7gV<@O7c~L>{{edtP*q8{>%qI#8~SKeq7>$u)SUBUKOHz zZ6rdsD*CF9mt~N`CaO2X;qxHfkZP1%ggUM;0bIhkqnm;DpR2lOXTGpsAIFTQ!F>Fy zx>KMuJ@a2+IKb{YM`V@%&*a$Q9fQw1#v5GmjyhY=^l-)&c9Z}w=;5YQ05KNirWwMp z9$voLVC)SgD&ZFtqFFFpx%^w3W7eCyfhx^iG5IUeoc9EL>3;BRb#R)ct<(J=X@tUi zzvq+AAzD`RL6X;z_6;=RCWop;e-R+dlOn%4)2TtK`0GNOC;8$)4&X7dT2FWf zf+r4?T*HN%W3^o51$0V>49~^1W6mTe^BSW6DGceR*h@`WTRvJa;kEX(+%}nhi7`Kj z-r%`Hfy(uOI%xiGEpxtc0c+gN+M#>!fxtaNw7(dvZ#JJ`hP2JNKj-%l_g1;fIBppn z3A}#AwaMBOyn1Edeo&FB)*ldhk6&*%Mho-Yc78i!bb5>=C>b;5BHQUZzZ_2v4NQXDseo_0X$5e@V zuB4fr`^zU2)q*`}8aQ(;^2KUa*T$_5i|1{AQk;_#rGZlUSKfp?O2e>VKu!b1_kuRt z)9KeFCi!h(kNfO5XRc!~y?H?w3u}s^=TJe7J$-Tka&JG44Aa*Kwi?f;n|kb%+UiQuSY!sPMiQ;<`xU!VA-8*jRP7+wt(bY}$3lt}gW zOMU>RCrILF*7sY77sA1p74lFj+nOo|5D~)mQx~o7q0iO|Gi} zzG17yv5B$QVb;%%XmN-moIg7|1)hRmd1D2CSvWp@RpYDOgYtz6NqMK6=I1Qc5hrj@ zujH%*12o=lTu?tsYA(6Xc{J2?+j~8dri_VIeGW;C18@3vVcM|I4fXyw|-D*oUo% zYjwVmqV)B~L>r`(i^_}X*u2NzpO~l;KiYwa5sk8j@cnuSvKIDmviVy1c9ZAEbePLe zSYLv|QV!hdOr5VcOcmVFV9+-i;bFetx}NjRwCH#d45+Z`Gdtm-Z{XRms4c2I?V!H; zj%UF4^Sa%vMBTugj!y{+Ix;Z)XfwgkeBZ*SZGo7TNscX68ttRBLph*3ol_i-uJLF; zZC0bAfX@2|wvc$l+%+z6$`W*aKrX})Z222kVRtC+o9cwLmGBeOMwuPyX|}!U;VTm}(kCn$6t4?pp2HSmf>0Jm*j-e8%g0q0ZjS!o zvm4l|^^rz60XrS8U^p^PLEJ6cYfHthZ4>KtL<(lt!*;4~_;M|ZXIzdIC;d8#H?e`w z{NVdxKQz_@^mBxq1I}EYFgz1D47O`f$E-=P$4D{VrS3Zwerofu6`jiBnw5sV{CGkU zN7lW%Wj=-X=vxOag|+#5)y=`v#Ft5~rHS!+etnmYGwK`n@E4pDgX{9Tnr%ZEvnwgm zb@${$R04UGzf^C@kgk}26>QdS-YX4up7Ymuu0)8??<4tkmY5RQYX{_k<411{vu(MP z^poFm&(79>H(divCe@UWvS@2uSfZ#ry;xCtE|BI3)Ba9=a7{Pb6+qSJzB@#GSvm z(5X+THh$6t2e(9qSiWqA7GJ4)xVSoN9lk^H`_IxGKaWMoT|*NBR4=1$yIr#mR-er3 zPkFEWTkW5$Hq2;2&oOTu6EQ}*k2YQYEwZD1WqGVzk9+P+9uSxE>$TgcH@9E9yg7XA zZOe+P%v8J%1oo_`@pnEYr-qcj;aZnGdZL;18`W3XsENHL^u-MYJO^wRUr|iJ(n79L zto0&Wn}@6Fo)t&^j&Zy!Z2S-KFi}_()uHS+nR^)&IGJ&k@ zm%c!cSX;I2T!1(It6Gh2N=i(Y3TT@+CG-?GKN6kR0MPh{>Dph+p?$*MN|WRQ1(>#h zXWSN&zi(meuunwFu_EyJU|C}X1f6pUNTWt4SVWO^9CWv{;Zv&8Mkbj~ag)Zy9@48e zjpJw64;&#ZY4+0w1o-4yzH5AMM(Dg56xCB}k$!9TbM;=8xZT+08p3{_YM!g^wb4aF zqW{ob*IXac*C-wwP6@Ii^Q?zUfr&$+yxaBxEM`_>DCy{Zu0IqR<& zhYl@6{d;{{?|^twQnO%xSDq(aew#1<2aMz(hO?p}4>0`qL(wiD({SfXvMBeSdg7Xq zIo0Q1KIK@;MLGH-&srXNGPFK9T6s)5EF`Po7elQ<{;f?d5S63N;4NEEaK41{CCyYS zL;a?Ym+pYhkSjc3L6i$W{*x%z>QEPZI}{S=nfHU~m0SAV(Ghkkv7EKs-&wL}>nsoB z2j;HaeDzF|xy`QIEqe^#%piQ^xW2~&<8l2R`Y>dNgVOgrcwvR`Ls<;Ue?q8AW0Q>2 zfST)7Vm}5dOkuZ9g~ot~vO)0hYs(=j3j1t6V2U+<$I$%yYK7X**k?eCyl3l;QyBea zzE9pwri9BIYOp2sH>^(yg!;V|_p!~e+UgL-9hau(RjbSX@!E@WA)s7w@uK157jCIG z{)T+wFl>W7Z~t&-2oAWvf1)3B8I zG+YKEEl1Uk;7fTpG|C?q6yF&Q^LH712vJHNs8v!G-m*ci(tO>Yp(xlP()S811=cy9 z8|qB)T#~Hx^M5n*i)OBnss@e7-;v{=%!*IVhmq76SYIEN#u^oi=g)St3qB>=@D@?G zA$|k8J|W|C$D|q$C#;n0*I{c#x@4i`zN+8T_`3ZTiG0%x$tfA5RCiLQlsf3ci@R3+ zlJU-YzzaM~?U30N%e`?`Q8!@z2h4TzK|Hc(V_S6k$Lg1*l-XRE&Yj?k(}dQ44mK7g zyD8QiU8-vM2-4RQHKF?j@GqEV8q#WpJW+Au9KG&nn>4>mqhBo|vW;+Jn>##s{o{4B zEgEu4+dv;y0a;>`&;R7|-1xVaV*za$l^LF;zrypN1SnN0!5T)MSM{M=2K}z)_rVtRB4pJ%jjQr@+lBw+H7-$;F>8I>#qL-jp zQ`1o7+(o!%cuGRTS&0Up7 z*YDGOX?*WgLe2O*B?PxM$Ex%_>l?Ai9wHAJeq!7(Mpo6}AsTJA1JkLmqop*tri~wm ze2qKGj}HQh=?>ba)t)TSvm%=m@jRnr&g4rV-xoYi_|9Q{1+3-5u-rY0?qo zsM87LYGJTs!7}7!F2|y4@?ciH*KZVMYxNuhdkkQ+b|}{muheYBwSeK5XTo*|6?)Pv zA%%pQbhX}VSI%h@6CT4#pBZW*KUl(XgUXMGr!BR3Z+?g$kRn|agol%=B>lmLC&d@R zDKDed-g)4MiBgzo;vFA?58QRjsx4kXB4s$KI(unL<==NtFm6?G`a+-i~1N+NI zXvl{OyVm+9wsoGRoX%iXc&u<>R#xp7s;cY)?y(Q(HyEBv*%+#S$i5UJHH>hp4OL_6 zZ0vH=F#xaiAH(Y0WWgH)jJXlfeaua-w-em>FRf#+k{$DG==YqZ?fT%0=g z9OUq0b)>6HAEJ^yPsN)xlpBk^0p=L|%nDyV`VaNP_S>W~pd}c;lUj~Xt0gRGU{ZADqfhy<7+>q841$ zg(-C(D=8_jN!jk0gzG+9`8os{LqIBE%Rz&TAf@WTpP@MRrPqcl$mXH9i}hLIggd?& zaF7d#dkg3}z|`CmMO7@HNvA7$kP~7$kYGv9F3KEc{`1=F*Uhg(;)A#nEy<*k@|6VT z%d7D9NoI$&4#m-nXN!>k2?$RvdbWS?xsK@@;3NPoPN)A@3PW_C&fE>a9ZzPMj^Rxs zGk1FyLp}aR>gFK^`8|m9)7g_17?`AGw2z6H;C8eEu&xNw)OOGoFYNm603M1{r=bulr?4dlC%z;$xt#i7NUriM{1?aPE zfR^pAhvAPic~=aXn)eX+DQ9k<2P|@_GS$zYa#8(%CGGuxkR$kiCLc=A4L-SQSnd@j z`?lRfjGTqwS3B?j=6kRgF>!YJ{b)}%1=%{e(aQoJA34}G4HlxB z<=oA#Kk-c}FRU|XCi&T0UtdbLix|OYazy&~{^0fz3JKq(9}tO6D#JK`XoDT84fLP? z&(MstlNh7({!jK~gq5O-&g7;?G84t0o@|7~Y7MxFnpcgL+zL8)J^mvjgjI`X?qB?n zROQ@VYwOyiwfrXLM7SmaVvF!A6qii#F8qXTm}^wzYfDZZOei@AxrFK>LITI0*JzB} zG^5lZh~6^~2Za;%ZJl=+-BPgXt1AKyZ`;cQj9$*`QkeNJQUJTJO}pm_MF-pxn36vS zrtB~7hUZJ9bQSeI*qH2#$lp6^pFJ#V-dys)qFN%wd7T}?DX$&Ik2Qi$3c5zD&Gh!= z*Ok4v*-GOtC%J)~?!aG!WF(rZ+!PllSbE#W3pLP{m^i-OEPe_hE(@#fY78h0g-5nW z+wc7TIsT+1zqtD}bCCV%@tn5tgL8&A38SBp@3{fw#Rbl33-HZzy9K>-$C54)EbY7Q z*4+5^kPkDz2FN4Rnr-GC3KNwIE#~7r+OlnXaozf)&VcGeYApm{zRM~lGOR>=cz?3%^0(V{s6=LfduD}CM!oz$_9pf+=p?g z%a;Ga%sF;+eBY>m413J=7$}+?X9%EUrupM7LbP? zI19RtudT_fK7^H}$`M`xh%>jUY_SAZVpg0h+bI4>Ju=PwS!$Jo|0bP$5F`>bbY*lF zv#GOB*I6bXf5G4`TYU!BsDbN6yT1|&=4iqceys0ZBM2x}8uB@s_9Q3%V}`Q^JvNeD zKDUdla&eA6IJayF-n}1xI}` zQ{Z1l&|Xw9?K0td17~SeO|(%If?C7lk}i zGVr5l0^xcy)rLMPs9GM`J7Caw zBq}O;awt`%i<5x{(pv`vzih1vRZ}4Qbsh>LCSHO5q}SUDIEc=^1Sv!&_^a{`S$(}O z(n#6QpX7s%L_MDj>1#)?{+YC-`C)!nMEfHuqk!H_Pp;Xc3MyECL*>y>>7Qs@7_2gpWCsP#vo>F79&#%( zzx&N$_ehO?dGX!6@;J$n`ob@fO4|bz?v*2jg9g=^@4@GxFkg$Is{vVyhztEySARPy zwAym65VrKhV9&mVZtyG|wb%i# z77LJwDlGzaX)mivSv#LEPTl@V>7+t7mfcUt3qjtQemRrYo)=^ z3c2FERrR&s&VeT>Uu)HZa<~%V400N)y)CZb%~^I=sp90DR%z8QiaIUJ!!L43Ji@&KUe4Q;)L`4_ms5U|v){@^|VpRJOLL9}mv)Ovtm? zRKBbF{14@wVRhn-k&gzf&r-H4t%@9V^g{5QrbHGKad9kegkBMpNK>6%KGy2{97cbh4RX;G(^dhiB%4+rw7>CT=Qxf?w zO5pfS=P+Jstn9>Xti7lr;lGJtZ%;?sRechKG7RBQD#v~{A&(BxMk9NjC6@6U=V+%e zmjf+N;r@l(B;I{VD6fG-Pv438_vD|X8Xn1N^!Dx$2)Dv{=c70G$!L4leb3q-5iZl% z`fddUPj2k1InRd74@|@4+dRe>h7Vl;uz(2)-sNy)BVqln$bchwo28X&cy*v7m>-D03;G?A-^>lZ? z$#iD8RI6!kM|7`_t)GuzxEr3;Ix#&Mm0;`a!)UqQqwU3NZEm2%Lv5TdWqQAzzYJp|ad(64Bd)*v0!0~;>TC0ZSGCv@o z2ilXmsn*|8PSc{e)uA)Md6t!BwP!QY0(X^o8zd;FnAb?7s`N}h^k&Kp?0uu-&(YFZ zBU|i`&YUjgOIo}Q?XWw>QTQ+rsIqoqUMueZx|fJy7mt52ORj(K;K}Fhe{V{P=pRMr*)eSvBcR z;FG-U-2x|tx{75`%l=&(h#%GusQVYre!P2lqZf3uAxfjc=@KoRT?#;i;lb!oD3ozs z3_mvV9k?B2e&WO&0eCUZR6+Jc-BEXdZtjE|u)TUFFRWI-H6`|q(EYnU_w!zFlwCTo zh+_HbZ1Uu$@he4L(=&fJMu&~n_`^#G_yZRi#f%Y|rbvImWs@3VT}Hzb3v+`vpe*E% z=!m0K>^*Y}Kqs>2byDekc%=}M5RWK&x3s>ZbDO@qI0Xm_J0N)=`sbxw<8|(FC25!F zooY^gLC6oo>B1Vb*R2D#%`8XzErFd5aVSiXUdnL~E-r%JE(6@D-S&O zzeH%Fm1Ol()H|B#2QG4qo>+SMWIh1gnS5JMuTsN%H5hZ{=-=iBVLoN6N}nz&=_r;P z)eIWregwNH)($fXuBs(qXK;Z;5YIL*sI1cz!?U>#!EBN{h)KCtF+mN)m(z zu(O%U|@e+-JRl`M>jLU zs_5I+H=y`7`FC>ooEXs!y^ItOPYth?g^xsSg+DaD7F_{QQ-4hi9n#eo(v^M*g2+7s zYj0vV&TBxK*qjPr?J>O;)$LhH@dm?0cR>8Xf+bC}3%8%@>DNnJxU~D#;H|c*`#Il) zDGgd}!7tn6;3oNbqMv0)dFh>pB(2(5ZmKS9i@he)5mAcFE{R}F0l>EILyd7z!yg}V zy5#@!jW1nFx#0y=-`)G}Z3487+ptgZY0g<^!$=*+DKo~kXf^3G1RLarFvD7~T%8+w z=wY4{h?#PqE;{;_eTmP<&%F1J6ogd2?w&d%0(rIFm*g_Xdb7@znLH!esN59bv8cVB zx^M~fcSdYn2T##yR3+P7UDyzk8 z{61LTZX|hFg`8QCSA&DcuF-0KAoCRE;4MSWI4JMzk|WJ{aJ$3}_K=`GY1_tKRjWq0 zc8w&gR;H<6(Sdv4^37XCA+u=~Lgjv@%lFNfW+Trj#P~&1Sss~?zn80EZ4#k@oEGMX z_&acY{yUA2uLzUZK#F{)tA2uauN_T;IJ2{L>o!l0HFqvbiKOEt%CK~dyJ4^{>n&+oBqt_HW8$308sb>{_2-+DL)~g47Jh{WXX-lx$y(V|1^JZda{bpWmpDCxX zMB@#K+}c<2we+U2M^O(X-;t}xY4(JYB3q&UCf08aJ5sa6rO-zLQH5ay<~`*X8!y&R ze8-j5I(^tFY+GLdx3NpMQYmD45!XFruQFAk+5AW*r} z>e`_|7AB;&nmEZ}&7Dk3W?^9(64p)_ksg*QX-cFUtMd86?vzX;ncn4^x$^`%v>rzj z_{)83z)D_)kF3-=u^0H<`Mi5r4Vc_HQKHPm`K6m-CF-z()T3{28J2CyvO(BYxgV#?oli|&7yy+uaIE;6-z zS4QubKvhiQ=AUpYZW7lomv8Q%lKK*F=(xa7SID<9^>04>E^-`Hinr3k`8c2k&YU^u zD|ZagV9eIczrA#P?Yieipbt2C-K&EP-gG#&d|v#?rk@m1Z7$n_He3=s_KP(RZ2j+D zrsj&;W@Zy{ab3u7ju?o5JVsqA*q{a=VZN5X>QiR)4y91U_uxEL7&csGO(AAAJ>{*| zcd&uQ7RD8kN8XWfY`#BIfm%k#PYZuL%)q<2Wk+`GQ<=<#`T_&z7RFIqp|?R&ppafX zvvlu^*E9FN+nE=M1KfdR`}cKj|2%!fD+}!Fo9?|ew|*?l1q~B%QAJ(*JLbK`R!^Pi zO}S7WDW!WRAoLBEw>_p7oL}MI^G1c7-~2YWIObb*3A3J!al%qS$PluHG3%LgH6U+C zkHqo+@-xB%H#iHHfp0?J07yH1tOb3|@v9m54ONkn{cCjho;{U(+?n{=z+aoZ@dO{& zwnK&q;gia>VG6p=)GQH0&Z=b%T%et49C^MMfnF(dOnO4o1FQBdoJ*qU$@?I)XnVXe zt;C;$KL^|C#03}(>k0&H`w`E-^oUv{&l5S5^RXq2PWZ|p+0&&tM-j_rI-U7MVfp5G z%A+@n2lo@&7{QR%+tvzRm10ZsQh7!9M;2oRwh|TskV0s*n!hOU-PC~vTmJ82Jf*EpxA8Gm_Mj5KIRXz2~>?_nB>& z?EED4HJ(cmBz(`8oBY9FNThngbe>a$mSJ*SK0+@lmgf4CocTw{JB)P|`}H%Vd1wA- zKHfR3noggBL5H}*{RkbCO6C0n(fWLPT5Ip_uH;vQ{gSAPmfrVWw0t$x0V-k@)TEpC zy8)qpvh=Q8(DqvO1{<6(rfmE{$3A*?0lButJ@}8xfkRzkz4U6eZcwFV_u_*N#Sws( z3S2J|YB0qfrjY#E-G4loTPzGhC*Qt3i?@^lPyQG`1&0P#-WW5&s)Ro44y&QvUj+*c zRD!qOEnJuNA=nsO+LON(eQdi@y!m@Db8dSfVi;@scyimpNngM9Df^u-n@ur{dLGQm z&IX|tdDh$mml$?*M3WH|d0L+cpSL4Ok`Ujo2RWu50i+))4mN5IQ)7_#sz2`8|0vnX zeSI>#rTlcuoyn zd0-#6!YME(B;OXpIHDdjLmF+K31V}(hQ0iY)%**qwcI2_4nHq&T~So!zYx*}`&G@#nYD)z2pwM*&TMymiygJV7Jv=9Gj_>LaG3>9?%YdGrMm>9zJ~U6>+; zTFN~!pAkFcmQ{&*Py?J&7++cy0P&pL^W8&AD5^8kbR3QS6=uPB*nV#OcvdrvBDQ$5 zB`769_o&n$p+ABdlLj#oUXBb7`=iH@k_JSJ!S78G-5QQqIp+WsSlnw=5IbxFOIo;c zG)wJtEi7~g(>#g~LwKF+&dE$@hFjZeSaW|M4f~&Jf%?D_RuM%Uj8^2R5t6A(Y_0EO z|15>H_Myr&peWbIx>$3REnLYC7rzobpO-qoadzj%4EM7FJ=G69l(d~S8{<#<-fU~l zHqbT+v9Do;pgkhdE-m7#n0J%BosY!hPJh36kV{)sBb?*AzsaAEHvtTH*o^yt*Qwss z12E=6kOW;LeV?Z$eqlc^T=ZamqG7je1~oZb_QedxQA&tXv(d{!#ug}$==o|q@1)9iWt1r#vOAuHqX z5?)x}6W%4-m6tGLb>O z>;V3Z$#PuD#)iMInd=A+SpqhxA}@?Ve{#oW$-oAKY3I+ZP>=x3sElR3Glh%2|@I-PxVMQ8{MmjqB{>kaupGG}PPk{dV8gLw{6+ z)(dYL+VJEHc6&WwYs7_+06B*RS!zbn-xv4Icq}9L*Gd^r7n&aiktdT7(iNKl*o8ZV zgEMZ7L(rqPiEgHf%>g1+o@|wMFs5ZJxIHig#fnYtp4^1Fdn|_176?q-f?kGV!FylZ z5hr9|AR=uGwPAsbX3S;$lR$X0WR&9ADXsIH@75kARk|l2in7o$@Rxv|C+y>cw&W#x zdeKu1+iWgJ!M6REPt5;O>{Y!)-(StKMA85z*~#U5L+Z}%SZOfT5y5cDSQ753{Yd%@ zrB&w1VK)QaVK+m6R;B&#-i3RQYV7CcMBh?A(`Jiffkh$y_}|{I2CcG?_%?BmGj~P zaK`M`=zVq&B}|?0ZOtzJYu)Dk-HPyOlQ-IE*oc9FhYw|*XG1upSr&{%tGSSidlx7JyZZhznlLz37AlI?8skC?x zA;U}h#n`Ti`p%KNf-q15>Ble=Dzzz*rU`4l^w!}v43>b4dX6y!R7i&OJ4v6F$piN} zO$yt>fpo+X~ySl7eP;j$xMGJikX^G`j!MY~15G2Eg2!SPxEu-ke{KU_IG|M^7U zwgE@FJ|BPvwGD*|2$7ls3C$cu$=&YjJ;+6E_`MhCip zN!aE$1OQK4d;IV(l`%A8@#!sMSybK)uM7-Bry60TT)`V41hEUQPtK9o6A%~SaSh%O zm#!A1ysQBl5e_5w{Q?cR~XT|xKiyMeL_tIZO_zf=*751uDzpq}9wOp-v z;QjY8^~L`w?2XRG0&C+6!%@`B^zlC6PC#}FCtr%j-#$_XO+M-e20Cl(j}{XEasRvK z^i{aI?_ja|Kh+!efboM`;%Zf8l_)URfXgHB_{u>Brjq z;2;Y_uc_|soW9Gr22A&xf5Y-D*QhOvhqL_nm+9plkkCh@9R1t;91uzTt9(ZrF)J9~ zI$1t+^I^CT7?uR=Pdh=jf9sHx&>;8O@uK`SQih&7Ya0mJf+!M(3Nb7)N5j$B0>O5T z=lno*SW8ZyoZ)-49T~pK%ae1Rydfj1S8v{Rkz4T(#)duM=rMX`IT?OSa=3QC>?lAq z-@US7ZjdL+rfsDC93Z76xfg=Y(;G4!2HvehE2cGrJ#jG8HsO?hO z=l(ne&ut77xmk~iL>Dr|O_1GIwKC(3> zLr;i}Vry!iJ#t%6Ad~5__VdB-!Qmy3F;@9k#l$$)@^{Xq!%g5d)nC|LM$!oh^AHHQ zGSEmYV`+K&=q5nGO&=bznv|WZcu_)ZI&=AEOQmR@$c2BX4(Re~zfG3gu;PUkS44xI z&iFdXH%d~xEjeip)|8xmG{B4fD}Y2?UMffc;@XP%w6qMDmUrC?D!4ocG&;2q2hh>+OEiDhuEKWcA3t z){uwa?45;Ue}ZikfTTo-U6cUg_UI=Vb#>FH)02)z-5i)3_;Av2Cjf|AVf0`$6(i@J zP3qM~y55FY0d=3lus6K*y&^|$d?|X4Jj9Zj0E7l zMf)P*7>KU=9p)}CQPoDEdQpNS@E;aH>}#k>&h%zUVk7!*L+rI;*7ZOV-O!`Qc>w~5 z1t$OebKUG`GxGp5V27_owOABtCekgBfp{i=JZH@c|F=>`*mvcTyL09r#gbDaRhz~F z>MHJA+2EeITs<0Y?fHKiQC)l0g5yCg$1-|oM^@L#YpML!+u9 zdu01YX#?2~BwmfyQfk^@s2T zD{7>tYHII15Qg9(YMi^I)Vfa-2(Ek|_d7~C=)>-9r{$?SP|r#pm)ObKCXb_6(-XhZ zR36^UsPOZ>9H4~;&;4Sqm1%Z;Mvqy5XR=fM2{&2LNh?XDJE{0`Uf!Bgpmb!OG0ljh zBwN-^NACdnmwO~d;a;JD^Ze|SoQ^=Q0(v8N^5$<`66l~8YT=+Oki7`c?@2w2w;$CE z-?_sD5aaAC1C67c%1Ywa`q=G06}<%8&u0Lj3-oe9W6v^b>@srMeEx3%;|ictTcY0m ziol7vm7}QQS{1O?c9XJqx%YC)bFME33SEU{-cCt)^Y(Qq607cK`t(&LJ(?Eq41m2g zT9yPl#CcnjW2J!F*^IT)^)p9rUC8oZ%&yWP1OwPz3v--XA1xGPlYWXm=FGwlqMy6E zM8z@`sxBHbA&NnfW$P@9hkE%nZ=XEU-9IK?(p0Ws=gg~Qfk{akt+dw62C#jF_s&mE z=HL7~9x*I9qU$~N;STNsoy9LaBKRt84bX0Ai1hjNYHaj$uekUK_1ho4mOYXGJKj)P z6Snv45PZ!7UB*cOp4A(ccGDQ*FaD+`)^(~=9_X;IKJCUUrZYk*gj@6O?v)7PMY+Yp zQ#fGoyl13(k0HG)El-<&XWz#@|NIYD_5Vw>;Qybd_D^ng?AX5_v(i=fcX-R>EnIoI zO8#Mtc_>Wc_+_mA&bk*AV2~VQFQRPT9(scl9!GQcVp4<@I{9B^Lp~i=mJRf79Oeed zdTGSclK2hrs=PxRzF>PSLp`MD_bSZQAKi7<`Pgswu_ETyuTx}dbq-2Ub*L{r?*hRI z?6IfD_KF#TxYxS+c}VGNmrMiX9vjaKcYUd=z-`*9%=)8ebBg}-rp}om&FOUvbM%S zGBX9FrKQDKVkGVu1q2{HJv~*7^z~E0TzhIIciHJ2-yz=*M6aDEIkVovv?&{@W`tLv8FB>u9dhqpkDg#3mg_dHbu;L7YtnK@Q|7ah@ zCokIbG*hR)w?=sbqITByj*dw^Jw4|cBiaIECJ#%d!a#**U^<7?q-rl5+IcE6fL2ZG zFyG()+9ZEXFwa8-xRV}b_y$1Z6&Tjzs?uL}cl1>Ph~A47+C>=vlfqPUxZVf8s{IzUWdqlAi_ASuPOgub$16O4`11N_|a65y+F>4$gg|5C`r(4F9 zYvFkhfW2ycqDMLp9Z}J8J;kH4<_+hX1BZ*TLU#{sSbj%kiaf^fbxV|`ra3@ncC-o0 za}IF&9B{~85rRQ3*$e|x;lHidJtH=G|0l8RvbWmeIBTz0gtv?Z7-&AS6CNiJC?jkj zONA>NTE-3C8@}r;qqxVH=_{Z8__pq^4G3HO1a2**ltG^*AoI*wOq+fE6?50l4PI+>-!nNu_0!MACvMD+4MD zXb|EsYBsz)(E{gLZgQKko{xFRl$BHk(7 zTK&+@RsiGcJ!Yqy!)PTgjdJ-af4>5NNJ<4?Syc4Y4mf*S zc``vHKh%QWLqDZtp`TU?sPFL;E+hgBzyyx!v6hYb?i4@(hV8I9p@$jv#3gVZ%~$cTIRSH7&_=+Jz4B;z+19&?{in^rtMyTJ(G*Zip~UtUV)hF+$1M zpY3BV)>XX5qjI*&-t7_lHy{+c!I$dC7*7s8IEMgqwl%C@foYKcy5rR8Cg4R+H**R6 zn|xmC=+z{cKxNA#CI-oluMdDCDo99}UWmvIkm47mj-C7;`Eu3^zxZ-=uofOc+@#(1 zfe!r>B~Rbu!m5D_kFyg|D7iFYi&rK=>%;CX^pfq<9Z3}3f+#>Ge|2$j(P9htrz2;o z_N!}%{W2cVGrGZO%LRx}{kq}>n<~$L1eC%44`cxUan#6B_42P{k^keXulzE`Et9{P zg6TlPk&Qu<_oDmb$Qn4jbBj9r*oe8^b6Y+!DT%AKwKWk6C6jKL9!ixy1c9>9jrwLm zHRHZhF$wvDGG?i^wziCz-r^(ceG_Oi+CLO2J9h8Z)u<*{z!2|lV;dpadyBT-ru3*j zS+ov|#w9aje!VM@o-zheNp3@u0$F5_hi^LQ2MWK-bk;Tv`x)O;lJ7XSWmCg}e`n}z zgk?+%LA2P&hfH`E)&`9_Etk%+^Eiz}u?-i4sNqDs=H@~nXg7-|@s!yNQfZ|lK*u7exTKo(BxWN&E1;``; zwa7M4=cAd5yQRpdW9C}rQWb-P(R^mNk!L4`x#tZpYNnF?{psYN1zVJj2Rh`-ZN@1= zsIxr}pGl-V+0ipF;N=8lr>22JM-qS|3(d^tF=E51M8@*eVr(wHsKH1CG3%U|-D5Qx{mT}(i?yMwxLTv&v$JUz@Q`kkc zZjk3iOnaAPMK~^dTnSLHr~*N7sT_@%XtG@92!$fy&n7QPjiV2y_#vi7DQgH+P`{qz z{wA$R#1{PbLtIhZeUE{NzRw#HqkTpo7^!~1KrZ*u=|_xJiYqNJ;5h1K%H+doD{1qt z72nI%bYlFryBJt6a-bpFsIFu|WwE1i+DOedy%y$d%HBJmQj1~3^7o#ZN#C1MZx5s_ z0*83ul?@hU3<-ud0act-9SF{>Y^y-HSpBWX+r^5iZp8;Say%K}06E9O3(Wov{#l4@ z6|9El_^$3dS1FGpzRa=D1A%q;!1ZP?A*EFpS`FzA1`pl+Wl3M;% zkGisX>v8oW>tn{#oz2D5Un3GMq`C;ii&2tT})=9k1n;Kp7w<#R!NP$32mU#y}G z0}JMQ>nWybtt6rq9I2OY_V|_`Zp#Lt@^+P{J;sKWpdiVErGq82-qM0dnr>b8qo&++ z55w7Zq~zH&x>U~QG*y%um!Olor6Z8&_e}Se|3IMMd~=FuO2%BCkWZ4UAqjPepDe7~ zM5#%d4$SR%O$zgjUfToK@0UrJHST*iWS~5ijAV^xih!pc`%cc~b$LZW<84TnNS7YE zfhsl*#CI_8zba^ut@RHQQ=vkS%Q76`^{Qo}c>D6e6#97Nj1t~YbeYD3gWwLQluW-1 z8OrO?1RU9qI?S$Rz-4HDlf;XLm@V@|Z}TWkBu|acuMR< znlU1{hA*#p2a6~8mOpBl&nH!!oeNZ>x44_|m zr6eXtIl{^DC?YE;fn>gJ`Sl9N&;!RtH|n}O2b_k@SJHQnLsB^fB+W;j!7ET(mY7LIkTGK9^4 z2}YXHyM%<0YQ6DO%yAv_ngugHHk_xm8=Ohv4>9vL(r%OQH+%D3>SGJcGI!q(UQSo z3qWYv@T`Dgzh`BCw3&zx4}Y5=dlKofmit#W%>aJKxxj^iGt%x$<+~eQF5PZA9V;Gc z)6d)dx+}qh9GzG#1W1tGF%?q^Cb2Z1fu&x?jt9`ES)0(b+^3H@P56zuv|rr*QN6nu ze{njuab{=A=D?pWAfwLWLq6uYk$Lt?sj#FQU#F%%=B+)`st5N)=TuR8wHX0+$xiWB ztcE^hlmlsGTgNqi(-4P)zYe`s4yUOw9KEyz(S4>~Syf4q$68D0upv>#h{d{%)!~Ry z>xixmL+Jtb)uLnMx}f$YU5(8(7P3OvrGJc*NW8jfIjR%Qerj-wUQ@dB)r9?Dp%^SJ){0 z&dxVQ)cy-`+A^&4uF3GV;eag2%;1M*q80To^YZ_ZO8s^0S7;Nh6`^Cd+}*!^kj=s{ zc1|R6WaOFOWU6Ay!44tDeRs1vomcheNAI~?$D=5(Y2u1(88uwOH&ixMccuT4VOJF5 z^&Rm)Be5^03=2~c)izb*ld&SZ)0NvlU!H64rOiq+= zc`4ady|$xv7H1F7c=wn;X_ZIa+eiJDr!9tFTEAnR-Ed&TAxca_Y;3)X5_7lP)Hyf8 z%JbPYas5`^TXrAOS5wc%qn5SOVP|GHFQ#Riht2U*CMa=!uL|BL28FD>bF`V0@8}VV zpI;8l?%HkH>;#AWkm%^{UWafA{E3AwGBaa__00q%iN2P(^VPuND>&Q|BfqlKD%Xxx z(@V8BTVb|CB9ILh;0D>)7iQYd{&f%W%kNxEiXJwv+gA)06jDSR3bM&s4T{qDA+!cd zQJ?~u4`w$`u$~N{dTF@?W#&-3ZV_Lz)(+a(dVd<+@Z43$^@xm1FT`>ckWV#f1T@=N z&sWpF?$!+eFQA;N~3FK4-w;`5~Tssk3 zCfFf_P-9QStMT(K-%OneOQqN3BI-s?h!x`QMPwc5)pAXgPsuvMTOmzi12W7%Rw zALh~R`HWZXt^4Y9XUX%lC7P=q&d}PIYvb$=E$hU;n*~Ly+PF!lb>UKe3b(6{P zipP(+ovy4#CTcp~<1Oyf=^(`iOAnnJrh5=N#3%dC^)qnUzrzQefMX-KIj&HD!;^)8 z!)kS`Vzr*hQGVV0%i3GE+a8WzXVcmt#Z(hbevi(bKe7K+H&up z<)|C|Jc_bdZST#FM}Vmt%iXnYZl#z-6~}Kh#sv~ppBX5=wf4_vabCMQIQ?>*2Yd(X zc3==x^VzT7qu+6`lCHFLHjiQuWfHuun75ZIJChy~a-X=Z_i=ZUC}}n6g3MdpU0=05 z<U*g>K4ma(?d^s7${%++Iy#bEpQ$U^D3YQ|#Y-k(;j>1ybr?346NTkz z1sEqWdz-o4#YMJ`?v7NxuHeqH^gC6zw34KmY&x<{-D(5p^a{HaMsK==%)CzCvrW2q zu&OvcuH)T-(+9<4T&mmi2HSGcQ;E{KBPttZ7$PV7K&BLH2h~P8VmBihcASWgHqgdW zLV@B$>1?c}v6b=i-o?y~+WEY#Sv#UJyp^AEvCXWkd*YV6_DZ+YR1dD zuQ6(ymohl_)Ej%Kr&I-8f?Nor)`D+p?q@QX+$%VEcM0uR#thq2%Qc3Y^0-kM&&j7x zB=!jwI9H&<+w1CWrKRCK_EJJRGL#7pMBjjT$S+OQeo8HdQw#A_Bg#3Md={2+W{U|N`8Qe+&n1Ijl;zVr>wb1- z`-9_5cbH_mss8w#14>bC$A^rotNlIDnG=oqE)Ig!}4jZ$}4~Jo6>t zmbA}&v}ZcAU~(#-A!%2ocX&}~06###DF4sPvKr@q%(>4W#4cp6!E0cVjWL95dl`z6 zRhscc5B2M!u%TuozEM8hp6HlomKY@+UPj(?H2PMo*h`;acsRQk0Z~{lDBsO$>%x+; zwAEVXUrYN+gxJqMU2HLyoMKx(Wzzt0>=W(^f9_o07~Jd@VpQ8-*By-q*0f}q@+G=g z0PpZSc#5hl3-fD&(ZB3|GjRhg+rn}VdWkIrt@5f(YiMyR{ro{7rGDX!P+eEx3d~fI zlm&(I)cb8EKGnTO@RN4GJuYY~l$mHL0PAEuSP99aY!TeoLw1d9cKx$a)ZvdJ2eqcF z2_upn*)!v}sP6e41i#1AnM}?Jig(`K3Q2r?gR?#DI;R8l2GvMq$$#cu^6tXZ+qR>(iOXvWS*%ADkO7_A{Kw)=4SHEqq9NRN!-9#d_MW0STD6eZ*=;=ugnrjH%iR-GmpGV6VDqzD-ZKd#5 zc15cgn+Lz2Z~4BsTH?eyVly-Q&_^3yDjvAB`%pS$b<=&m&(VEl#!P)9WLJZ@+v%v+ zuuNYcG;z0{BH5T)xZbVzGh3*A>tMGq!)1)eR%ds_$wz6dg>s`_Ix#cbWdrIMJGp)` zR{FH$g|q@QlwpG39Vu{x_xP!Nx9*QVlCj2D>QgsB^#Kmd0n`sWKYo(8P%}+?WM5Yq zNbNGwSl6my>%!pTz?>&Ung_OSa{5oYcZL@-m#H4wKppn!xJo&s>7K8*R-XCl2QI&3=?OJ)C;D13}N@7>{u+1 zaIf}hh+3#IwyPS=P-WtW_os4Af~|sF{HoI&MI3Pyt-;K>KG|olz^JEAkDJ_rYCd2> zr}EQ;nkbKxd^tD9Z*+&SucN=EXU0k(GjZx|35IKE5y3D(dm{x9yAapubNm&xzIep+ zcf&3*f#ucD`|p6GpD`Lgy9GBT*3(&63PN|@RDa(6w%tSt1dU(C=~i98=-)H_V`GT4KfLjTZfj)Zpu%YfB(rTgte(!kDz z@~Y-n3~g-eqygQ`M(Z@MwKCtyB6lEAv-Ej?KvO1K9-9ffUdp~rHK`gT-mRW@yp%&l zy|j*y>6M`WLZ~+V9`;2h-)vF%K?V6M`q>7GAmjW%QeCNb6TY&AZ*!T|LheC@;Pq~K z%7Cx;D`NY#y7%(r!DA79Z5zGr*{M`W27b;~huM%p~2Ek!9L6 zrx>P9Luo#;ockK~y6ge0Nx%m`r*0)9GJ&*}pGA`5PS4ioi*jLJk?ZqcO+}tey=g2N z4EiCJ5HLfk@1NUxK&snv=DzSD?GifATMVIXKKl4u1H$HkDyr)3BbI)zJ#4p&JeIcS zN9qohQr7_Sr#p~0CyMrOz81u$0CINA^A#H8Gqu%DNi&1~4WTvIA8^R;Cb<=cUr_S3 zkE5S4E+oy|t-+UD+pV0n-4lWhX+mS3%~0>Z?5)OF?89eV+7Vf6Fgv?C}tkLBb_1HUK}i0y09iH;mV1+CrtXq;=T0 z*I%T_J7&71ug-3En`YOh^FR?J!Qc6Nv}U?js~EMFvH5v; z*?j6;HS_#J9gTww2h#;Ivm{*^xwjSvG9P2D``pXV5?w*N4FwB!?_BzI^5ur8;&e;LWN&ql9$? z$wbV2WGCM%tjfcKB2D(PQcDL#)N=%>XA;z5_hFyeirXfi_ugNAT9So7+1tT{WJGoa zMw;@}WtQQ=AZmGiIRA2n2bJPyi=+0WWMl+(RKUXORfATu2>eSb$3N^ayp@MNSsPd5 z52+843j*2%sIQ( zD48!dX;-oAqkg2Q#@NQJOII0RhuFxB_Uc!CaTd7YM8fq+!gMR$X&<^r#~_yZ)LgFOdx$Dp?qp;0k#5PIuF9Ps7@g56T>O9-qNEQzDA()F!@)KPu4I?8`>>jO z?vDn`jeTYaw935`671N2JgjA$Z!Ic%kM)#OQKU>4-5&@~_T@m!hi&+F4eT-M**d8+C8|tU-NJc0cGAF$S zSf9Adelecoix?Lh+MRTo*)$<~ zTRYoHzG2{J-)y%%+-7Co7LO20&bj z(BmDyiIX-=e5}ixDIF#uCGXu}%8)JR(t8l|v0(a5J>(+^#R%Q_dUr4uy7G8-=4Y6M z^u&1)EXWEjDWHGiyM@%el>bC!7xY@MiSj4&SM{)Z_XVX?Hie*m6hpzxW}Eh?qjb?M z7!)NL3&kp##WC4VkK&$553)eux>;72E^0ahm_H5WF9p3<%MaNrTr3ZQ3YC$cyFI4b z+4g&XZ?G3#@6Q;RoXt;SNgTDgh04Kx9GqHb8M!JWB&FCK>yKACZX;A?m*N<&3n~cC-n~_u&|REU&ogF#>@AzZu67tY=M8zJ@&+@_cHs z+3^z`(t>I|CdpBR`oyQg_ubvyDGlI>Np-=i*}84oJH1KD(9V#%$t-9R4~IVsp!YUKYSq?fF?g_-+H6Tz5$(73`lsA~P8&*3 zIB#Ug-gmEQt0)84o^c;ssbUY%2IRWi7|<`}c_4DZL_wDNNjkXz|Hf>Btl<5HE>9zU?OyH|;T}Pdmg0A0K zd&Ff6{Z@?*V3Shg!qxTmh??zgRyOKcH5i&tWP6ugO}D2!jP9}w$^VU{N4u~DZgsnT z^e)@_e!4mMz2j`!UB!DtY2HJE(R3y1?VqTG*MwAPs_^=tu(+hoDlJcYURgYwg0~V- zvAvTjWLlZySvFESywv4=IzP?SZuW5ubBm20*W4n1DHtli&dv^G=MU|-2o`vcr<$x* zj^#!8y7hHBl*k#IFDn{~qv(RqOV{(~_r;zJff`se8gtO0aU3bMv%P6S{x@${e|3EZ zsZa7}Z?c5W>+)i@8BAq#7tJn|y61~EkN$!mU{DaH+CN~c~X}>LrXgQCZr@+)* zFHIG~9eb**O3>Dkb=vO-H5!$TINFRyd!|_wTy-FeP{C4ZNtOYV9E!mvL@B>#f`AAP zeFUWkbxbPfUGlJO5!gG})sUY)tg5SC1C)?q&*V2X_Yhz8ti=W$J{qO-g@UJFlcRV~ zI!pU3m9Qx|Z(yBc|Iu{{ol=o^wrpMM<$M@SATkG-cw|=x|L9K|3)o8b^zj;duWuHY z)fK)kFRFaty3bD^;f0i-`g16_KZ(t*=g-8Qf_r-^?K4Dwwu}Dh_@jV}N_YeO#;)Nf z#_7sp`a$B{wP29d39Ek*;Pp4n z9ag>9Ec6=#p1ScmW8f90zSSl;)|5Dv_rxYk(zuaEU%k4rP4KSST9Z#I(tUa^Qq+C2 z*{`E#)&H;4Vbv2g^5yn6b^#zCA3tUK5^xlU=D`zlGo7maj>iSlqlMG~!FoZq*fQp1 zyRr~iP=Y=6rpQFh&a&+COHb#92~@|ZO~c%dKple!?VqlVRHx|K8DHmdPB(!p+P2;I zT^pao28~9VmQC%+3~K4d6E4nK13BIjF-yv}3m0ILKpikALm{MTWMbIb+stUQNm2R$ z2&=P@8y7dyeU&qrM-VND@zO%GuAXW+W#fQiHbswTW8B88QE$85T4`zxaU}mogBQ+i zzZXA{+k3obEC-V;@=<^bf}LMxAo^|hHgDyO5@Df@pl5NqTD30`{b|eE{q`G^dx+&dgHL) ze@?Zf2leW?biib#iJT8H+|!%AF-<7JZ7`5n)}>E{(KO4H;y#3bNf$u8>&JsmD0;A! z{xgp2zs1v=mAZsd>JS=n6}3u-6!+QmXz(e#Tc>!BtqHrW$?Q6=yuO+I_?oRT(uudk z(|DQg`Lk%IMpUhrJWGkg8~v!L1JBG% zs|R@JpxoBp1^t~x58n%unPbrO1|>W~Y;?O%3HY?fSkH*86p?4f64O@m(|kI#M3)jf zY8y<6fq10Vz_4Ve*JIn!tR94E{ASz91mFNrOovCRlaM3pz0=RAW$monQw{CaS0hVi zRTr-bo6U<5&~IcQ8((7*BR9jz1kN3b^=Q%$Ac!70U1B3xfxjzYd@twTQ|( ztL|RYYMiU1;Y;wdIW4pHl|GX*tZ!JA-8E^Zx4G}7)ZD36+>%1mr3HUg;B;Fi zzcqM@-SH1ZyBOl?2S!qE^5|rzl$8l)k_Dn&ZEa7Cd=?H@WS3M77Hti%xptgEYKfvdO!RtzV3dYwz+(_hV1(>8uEab#5_5JV1<1cd?$f zKA`q?;zVty7Yb`1;RlvW^`e-yegw89gS>qtj#NkQBS&9kA#dEPcvlj$j3gj?mv%Qd>u$ ztz~{d@Q4P4@LvS|fB8#v^B%x2PM}J>-2^ z$3o7+>b_Px&WuO40L4ndBxm2K=`h5!j}S#-=XPRoSsE`PlST0VV(Trq+FIXr@3o*5 zm!icBEgqz}Q@l77_Xc4T8kCqNR+Py;ngGG+spcS( zoz0dM^9$L<;D1j?e+A>65DR-(#g z4L9s)hJUgj1oqL@Z8*`UT%&LEipDKF!Hj~N~#uQ?38IZ=ltVwKV;RzL%09U9shsM;IG%-4nbp8 z&++_Zc&(8Quv_8dqV`$GOt5*Tp<3qc`V|Gngp`Ro742_Wktr3f=|!-4-ft?QpyRB~ z3|IIW{}8q>AJy!c4S{__^^jR6I5m?xVUcR8M)usT_MOC7oxh_2KfU2OFEPhpGKyo5 zZ-TRd2{4CPxjz-G-dLB37|c|+2wiJKnL0=%;OTTBoIvN+%Gi^7|Jpcxbck5i(6O6Lg9&`5oYaJ%0Ss!HurY%HEokb?9KN^Puf1%2fY!;y*u ze0FL(b}JDl6Q0^2qz5UYN+^i3Z*;~}+HYw)LybC-V<08dsaX>oFvZJ~1mu|K2iw}8KXW*Jp{4b$zkwP?@~e+-{Q`~TQBQ*ueIVfbk0`P{0yGB1f5bduYQ7czq0-V(TL6?If%azWEW}Gv)TMOKC;lcRbg*6ja}##T+n`{IxUhEzlNFQwc?vN6+@bB@D@sFi_c z&At&Gppa{cWZ-os*(PK!aS}E`=SVi%|D))o&_bQ*XpSI9Uy%2Qg@xe*vNo2EuHXC! z3R64BMh5l=m>*1-CLIqMxM_8t>N=bcn{L-}Jp(-!gPd=tT7F14F`-WNi*}#2_{B5H59IQB+oJvzbszRm->dd1E%di`D9Zr7e-WGm*Wr^?$-fBziN%G+_HDde^5 zdAro{oV4=L7guQc?EH>uFaeusIew+{s)ovOfi2P$q<|+tn}7;>mcBZ9tVc$^1b47+ur6v5%OAPsno>`Co>u!I2hR47Rm|Dm}3k}&$u zhw>VQAB(rsd%rR#aGVk|>XJ5Skze9DIybk?x9-Ik-IpIa|3umggC#ATR8x+Y7GM)B z%~olS+py2`9NyAXH6x_HXlMzKOz7wOK)jf;M* z#5-PtnN|;ZMq;I1hn<>?%2{uSm`LC*f=pw4xK5YzVB5#fV%JU;bXlovFtC72VBTD) zV5OkxIV15$N!L7LWoGUQy>li~I4}WHv0{~_-3fZl?A z)68$@A%(OcfbkM9Xa20qw6mY8le3jJ``f&eP%v0k1R9;2_(sX8)%=vw zI8fL4T&m0#l-gGK+ep#*UfLHi;@z(@Wj&x`>D}+C>6A>5ptwE32MwF--scVFX!7P@ zI}vrZ2T}jXqike&>tVA!Z+q=_BMpD>^`dO&a9mb>pyO7%$QHnf5T?TW2a}#a$ikw} zAo5n?S6{?GD+o5D0Z8DU*a8Gs#i`I7VY*^akY^_}BRG39&o=P$p_=@5 zv**Ls88V!43h#D@JKwD~WyR}~&12itG7#^lw6y_FfUd9wqW~avMv8q(wnX5^*v^S} z$dOKd^^P+Y=LDl>fV|mh65r1@cY8Ces5L3=WSDQJ*^g8s9Bscl#Bf~x?RjKHEtX5g zGiKz|pXHhglXI>!ZXL=pk0if7c4^d~U8=ahfG96D)J`3$Rn92GtvK{56^1P5i>4M1 z-6%=m0efOLCx;1Ou#}A~9m|bJFySd#8)gcPsW$r`f3GtZww68` zB139@&AzS4Tb@sXXIO@;P*CW*&sOjNN(uw-i~!H{%l75Q~#WmE6j zxzxPLYLzn^ZQ~q0gEqo1-~^G_A4(Jml4;Qt#$|Gv=Zzi9Td2JQ&PbbTK9%Rl8_ zjJMsB*b)HR{)Yd^ito1Dy1ma&?I8V~tnShq=a!>5 zi*>%a48-`C`Ne`Zv*xRjsja(7!>z#saN+}m%>wePe57Oe*2}9utQ?#erE9zqo_a;w zKDFI;^oa12g-33rr(~B)sA93r>_0B! zeJ=vuJFv2{Zek->DdWSS|2QKfO?$UU;)Vtle;~NYvk4R!rRJ;2g(gLjk} zcfKnBke6cqvzZkCezIbIyc#Ht2CyBRI(I^RHaoF?pLN=)UCRl3Ro}T z#7=~cZZBb7LHC=7QG9eC{=k-|{IAw_X$ZBk$pLT0P*$nXZIzfS_1tnz_LY>Bm8b<+ z26gK9VU@+s*G-$MGQOyz(4F(PlvMleos5G?Zk(15?`)WFxZBZYsoU+MD@#Y?=JGX&HU*(y6H#4Xf7m}IJLCg8SX zM%#85$z_iNYPS(wfuU(~?{r7RFQ^f8#5t(AZEHJ|fz4u6KhFNRfXvDoUS)K^ypx`p zqMOEa>y_qQ)J`!tfw-17r{2!63{NoC`#j5@)JD%^qD5@$WzwNvG?L{U+q~8i)9!*W zuvgpr4G8#{_wJv)b1O}g(B9@KAue5E zMeagbZXm5NGYdZqS&D%c4$aaSV2)4aRs?=0#*a8cSrF{wlL16&B$bx+UsNbuU&`&~eIHDxZw!n^U%r0jdD% zhaq86x&vWsl~oKp;HGWXfzka7KQ#NM1BiY5Q%Jrj94i{3!qbL0|O^s46slCoVULX_sbm-b?-!A4U39g82&)^ zDHgi)BZY3!Tvc{_RZ@3gz~JUc3Y>%Nage>UJkImuFKo|6{Ls*mm+iq;JDJzn|HqW#xIDJ~eaS5@Ao#aH9fUJ5<+u zI4AIJrW=?`Ik_a@VD5M8c8Mh>`DzrfgzL5xBQWsCzA`bhNF^0K`!@eFf@$Reo!iyy zhf#}*-UZNA$iNG7SbVh3V))){@=`!)LfiS(5zZoPnPrIr$J+zuGB3V1JVDWF;Md*h zR{;XhwJS<6^G_`;K=nYBnMbX{!+}T#;(B99Hnr7ERe(*#v2I*>y`RVehmx**q;d-| z!^jt!`7UT(`;$k{jNAIPirdqLf;)~o({O{3zP?xMXe|HzX|q#ph4&|VB5=FpvKzv1 z>%!SIu>rey>jBBhxKx?iVz;z(+ZzV%*|fh2m!;^ib6zoW$9F62dbxS~iC00%i8#%i zRB0laXv8I-*e>%I61ALV`nx?Cd)P}TA$i6&HVBp#ZEL)}*lN%|yJWZH>6LbNr8GGa zI6>36aqer|>aS|Rna#IjwIJ(gZDvr8H{wQp1sl!%F|?zm)C$w}HY{fsSqrbZ6Gk&( zbKH)`;~Sp2PFSH_!uRpa!E+?|%?>wodb!+SmG?{_p6$HnKjmT5h^zdz_Qp91SiE+M z++uVTe0V^NwKk&`czWcPl%^snblf8yu;PJ-Z*HZPzVzF4w*R0{4V9v04z7<=_-cpo zA^P^4XOh6ut9IZymtT7whn>MiJSaSg<8AD7{u6f)3Icl}j0z?r^?3I1@P(Q- zoh19&W&oL58zWQTeF*F{!6I^WXkg{pz+kMtzsDUNIpUbbj)>3BWXL;o*s~FPD^KyP zIhySw&52P;kWI#^(AN_^>3Lfd)-v2-2zR_$g!!3#V+-mJ*s^a-jUEz?~zJuTj{XRq*cew33)9P@TeJj)a_`B(g*P9oAUMA z&A|0nnL47NiRKNMUo9|d%7U^iom4Q>DZMgjf?U~L=@8`(X;sz5p*@dJY0A6fw%c45qrrhk9@|4{ z{3_BPnX6HoQG!2oy`(fuVTaXtt}Gbdcgz{wgL1qp*qsLw0I&rA2}CVzg?Ib)wXr?+ z#oWfuQpexL@6@GwgkE|rdMW~RJe<3{4rRxLgf|u(x+5|?M{$-;yK1pbhnnlME;44c(e+O7o4@LR(mtuH_dvFqn*4n-BJtHX zq{m7mEHl8{5a}i(Vcu+fZp1voOihRH6^BK^yO=#U&1cqG@JnW(UTqIhAXVe&8?|^o z1makYp&11|WY3akNeusy9cD!_*gdleJyOPgE5F5L7XuYXO|V9ARn+o(K&P%%O%IH+l;F2| zHk}V`G(HZrtk>c(eJ5!F&MEe^Xp#gk{__h{qGeb$@Dlu*UIbwiT;KDz!tT%7eo{?e z!oLPakFk#ElKxe0OVir>nLL*3(CvjN-odKQS)dR=W=3lsg`>EflUV*282g6}HcI#F zhc&sIP|O=?Tnr}RSKoPmFqCi%jRH7yK1YUsF6ab2u$;wB0{;5cCrO$U;6)QR)_eP~ z!B0!v7aYpQ*hkGDG@2GIg>L=H=(2l`A7h&%mAirb z*Iu_)o6bGo(w+AsH)1Z|m(dtrPKg#NM|H;P{gyE+lLzUMgzxaTcJAo};Ah=pmcR7d zWb4C6-f0XZ;puNpK`5OOw_Ker?fE)cDd0LJkw>CggwX>y;#DJDYlz)bp9e30gZ(1bH#JJk*d7gO{k@?s z;!FUab}C^YZb-Ek15P9)CW%azc{%pOo0s0#_I z6PxoR?~$iuI7W&eQ^4`3#xQX66wbWGT{jzYe!Q*zx?3+>tfTg1Fl)yl8rr5na`Px2 z_8{!&4GT0$8iBOP=>!C}kusowR4ZhoI{CJ;B$A5`rqfu*n#*oaXH?7CuBD6iStZlK zc1{qx5R=U0jf%!)gHIZ1VnL>L=6I{IFcTA|EEz|CxE)5+6oia`s?Q5bs(5&k{tCa5 z?C>{8Zj_*7-9f)3l4tG!cCrXaaJLnqMO=aIbzLs@K-DMJ@S3QgoWjE>4eYJ8**vF)yvTWi9WX zp+6>VNrQjH9&?b#eWha+oQBW2=`kZ12QT9_)s`5Y8PL?xoEyp68? zn`p;I8AZo_3e$kP#cMJ<3*jzJ(elTE`@iu#&FSum?45fG=A%+OjW^cXoKW?kU=p=! z|0f+0e>ry5_Qx5bgS7AlV}SJpC#}x)Bw3>hQDmz5|BC!GXwRGd65<&a4L5d_4BAgg zLYHN_+9o6B6&g#^dVC5bWo9n*rmNY%R_2F1i@bQYu40)F5?H=OTlwK` zF#cK@M;z{)a`Pff2)EMUcc~NrYWeUPhzUrF;2IPv)2x#4 zho>j-rhQRBrC-Cv(KoGKcBW@^`^iq(7o1T2aW5pe3jgCDX?66qGoLm_QX|+rYBHLh zLFe%$9iJD~<4I?@x!4KNW|d2o<_Ya?IfxQfei_=|1$uob5_Z;2#Jr6?-6`j8{XXS; zdps=ZrhH1YpBHyRk2o)06?Hs< z*^CrS+&OO45nA{zOj`>Qe+c2P{xr(^D(yNYH<7!e^3@GY^icLFjWDzLg(>pNY-yYV z_^J7lBD4#StP5mZNyBb)DyMVd#V|SBD;gcjH@_)%XAH?xjEEVpL~og|%+R;T!yTPE zqwNlR3e=7zwSQT3SMz(Z!;_fzFp_6(8mKrMcicHQqTyL5Pu5@HwPX&C{)=ER`j;{G zcMd%!qF(TerWSkW0KDtA#mJ`}+N{~-trk>MUtgw%la`>eV?QlE6O(*4gH3f>wL*J zph0Gkj`@skRL5v;*{O)-v`>acK&yl*9KsRTL+69rlCp=5-C5{{7Vb~JWkmBsol3T4 zY)6F{i}V|^Rh%FEX+oyiqWg1jny{;DU#ymGB;9AaBrssLde@NTDM^4CJKp26CE1lG zQuFg#5-6%KzXaR9qR%X=b|MjET{=G=B8Dsds=4-c7phX}04;t~J-YHM~`n6MB z0LE0Zuy^g7!y@0QUnt!K`|H56p`31Bh2@|H({cyM=Ij0*ltHu_QQC~uLbi0mX~dwQ zP7Sp{vkZRGmlC8K5|nil4P;zv^SdoZUr@J`Oje#U2P4I9+4yKC3fF##x;I=sb8&hfekS{t#-aWrAUHz>Ci)Pvz zt__cb#Gou{z@28lwnG(V(8#?pZeiXZGx=Qx_p{`aJ^dw>1=G-xeebD(ufc8*}yaHF!lLV;+t*mWqh80wHR`Z~$cCHQ!P0I=@eUrOE z!rPJ^rr7^pHEi7j6Im@LAD^EGP!9di)Um@+0?+pG&jwe5aQ71BlOpsg#1Ml`)6_%7 zNnnEZ0$47|LA z=5g!2tGt{AJJB&Y#u=ra^KPeg0MhPI{`P?e`bhaRXVJ1=aVF~;r4Yuz4fcP0oeU5{ zFEd|CqS9YHE?$G4w1n$j2S5eyd4Mlb-+#Pyhva;Uk3yf2`|J{!jQ`lB|)u zgQrn)HVB)8RC=cAB78y1X87~F?^m&Mf26dQ04!sM+5@i`ieH$Ka^j*U6M|N92qQ*N zmMBGE&K2BEFQ3Z-UmAYi3;g9~`D;plKO$V8RTHHGEfLK=BQt}ZtwGe3k8!SU&9_F+ z9wcI47byNYb_3I$`6Z{|Y-Pa-eJ{!7W8-M zLVn4)6xi?W)J!4h2OCPk04BqO+iT3@Fuzaq)yKGrXw!Nm3$%FF!0~%aeO}YbxP{Hn zwCmI77Ny{p#^OdB;jJ>DK`%eSL- zfcqToBrV0D^7o$F3=t>Ep9d5!!+ErW02cdoQBDG5&{ydsZ5$n^GY$H`G+M{(0{Mx@Rxs$4XlkRmPHmkKiuiB~bk>#MyWnbZy2~UR&CE0s=#=h{DB_l1~o6yY8s7Y6E z-q$uR7w~Wee_N|KDGo1 zKS1sVlW`AW`fF$4WNz5fh0L8j<{rb(<4>FTYr8hz9HQ>WKc!C%4OR|%Q|~L&IR5!w zAPgZG(0^ki#BSY;G$LpiavG%>SzS(g5uWMR(h#|DTvRxaB+6U(ip4gOW3cgpSF7`( zr{al~E7sci5wtqP+KB+|1P0LHni#k*S0(xE6rXAK)DWJ% z24RxaGi6ydRVWA`ky^if-|=(k)~;cdErN$Il^72FG}UF944W`q#T{K*7svPXC;Pqx zG$(%?jua`=OsJYj`oDJ;;7yK{=f19`T7%T>Fo+x0^YFHQWezg z8QC9|Y^zs?J`1l`n@p7$=z#g_iYQKNVJ)7K&enpfs1h5m(=P0it?`+8<>I}Nvx|!bgyt$ag zy=k0t=;33(WS;tiDvqBYNSgtXT);h^D?Gm?Xz}S%+m;UKDi;Og?(-;nQilG0!;7z2 z_cF0aH@`kpixdHRmG5;(IU-4S_+*uvJKqDma8*BnlBl>oWR?qTJh2I^@#s2spGA?;_}>|g->(&2&ncbAeOZT$hW6mUcvn3;45Z z-|KxjlYe{Y)vXl3=6oGZ@G9be>Oe0fn>IgJCxvU>=l+D}J059cR?gJ9k69|t7M62+ z_RZa<>p=Mm3m^rFzDuXKyf09ML;l9?{%KA(i0xYvi?)<3FWnDWxO!n=NI`)0vV<~~ z{jAJCQ4McjQM_7I*TKdshu_hk z?E`R9XXLBv^Y8+V<)?S#4F$hC;=0z!O6`7&7$?WgXCwV&w#t{(DfUVd{Sum!^Pu)< z2o0MZdb>{y4cUCI8R8`)?5r`Q%V==q~Eb5`D@CD?2_> zRrL#5URVw`#ea4UKY`iCdums{ylLaO32=IWLLnt7009cnYf!I!?Q5t)&x?;$*DG!z zvD1}NXUi8VGFNdYK2pJ)p6emFLeI0OX<|DBIy_I@DWIFy zFd5&F`#3d0dOr2kq;;s5A z^P*kk@^6U@DamQyz1oi_WVCn#`R5n-e+uLNJ5K*6TK~o>Bb?-QO+_mpzpn4KY*;-I zwxoLNGw6VBD6T$w;M%?8$tIb`PCQM3+59SMJQ+YSF>vVd?l&FPqyy*r7gb07I_{tP zzAqMK|Dci@n9| zKduDMwM?-`ACLu=MlRV#IN=i#RdRY>O;@I^0pytsr;jaUbfwo-hn#WMlaG*&rw;xU z$nHBc!rbGI{z8TFWj}TBqlUzQfABtOsj*3Th2W0?^Y{g~TTHtk`b157`mylbLYFg* z81#o@8^X#Qs-Cqd;-|g-zd9z|anO4w$Fm9Ww1rafZ#ML1`*`%JsMOZ8CtMGeid^2L z_hvFhp56@r+xSu-%hj%Je7xTS%oW;HE|-hivMeWdGR<8pb5dpTa*2?2$aiixS^pz4 zZSZqJTah;t;O7WTasOEDw`HU3Wm25Q&De%7YQm-Om*uvmOjEK2P3ucjG(%b~IJHDR zRT_`xSNB2Rhv~oZqU%C&RS#WJ+xFBNKwkabY812Qt@p!c5Z}Pou+Zkui=Xg)bl7Nud=LNax_-=LwZy&~Hn%nm?W-1E{+@~(-7yVFF=YmFi%eBA6fckS%Er};qWwI7vrb&N{C;Lm=d>Gr6%=_b*Q z;Zp8>9$sE1+fQuWl(6g2iWB(gn2_l==`!8&Qevh7*w5EU(0lqjX@ZOthNE*`Ld$tM zl#}Bns!KWe>C{7LT;eE?K#FGRsV79USUESd;WI|2 znJYzf_}Z;$&YSuU6j=vn=k9G!N&#N)^mLshUN15%DuB0B$!>nL#y#Cr4%QFhSdD09gby=?UWi(aGlfMmd zTxT;`D#N9?VA8mzLh7pdAK@+ZhT9%9cbFbMcl3t(1tg0Y{k;Q`iv`yZ8T_u;?q zIv}5GH5L?PdQZ1}*H_H7=Y!+!$bbPiC}BT$>zKkd6*P_N;R|5HHz+F)1CpAF0j6s{ z57LpBpv)Bu16Iofp(X;NCM|coRjQjaj$@|a!Q&X#=ZmX~BBp;H_&vW8_{>s&GUZQ<-C;uSSfZl&LAS}2%BHmZEA^Z_X_d*sx$ zG~)8k2uvdt3$~wV*;D1^=U+gOghl`LwAG(u&Q!%n z(Yx)Vg*mVzC7#=d1V9o*$&61-xN2ZQ_wN(_r{#*w6AEA0vx(zk>^9sE+$<|?oBy2( zrs)%O%)}O73jfj<{&Oxoex>23dEOgZ<{ddf8B(jMSF!PD$pGS6f=$#dEhAtf7F`~Q z3g2`;RScB8D;)%LPZbMOxgrMpVe3*^rX5sCIhIeez6g_zQSSSWWvtR7tivB%^LNsB ztZyFdNvzDo>=p<{ZhfM?@4*%=-_I<_3(Oh5$0l)cf9g7QF@Z4`_Q_+Xz2gzCsi#=@H9K;kIWsLkh%~s9r;njs4MdFdQGy30+vHmBl{3F;Q z4CwadhnD4kOa*@G#vt_FE7YmMeY$-mW#3SL*M1z9;^w>Xb*P?~k7?f@L?43XbM_JF zpby=a4$GU*V00s!dF`&SOx>O6$Ox0l<@`Pq#^~%$QKKwbTQ+m4;y~`mmL{ zxVH4bi*H-s2!jx^*ta3U{>vXYbmbVKI*?5Z^1T7VPac+%K7hTikPQa79+j7a!|xJ@ zEP#-Sj9vbh0j*d1`%Jk!>c5_bsP;oP=xS44XH+tN7JiK~=GDQ)?Vf`Tj`gPPUz&wU zjQpG3{rgNMCAqWL*3v`s`m@rVU`diYgH`4M0X zEsInAu?@KcgR(O509M*ZQm&lgM3VQ4{E)dbLSxwA>+CAW?+&6{uj?(9 zR9z$(elcgOrpCV=vL0gI9AcjEDMTSxQKn8{!XTqN-&Xy9l%|j%cPO<%H>r6v;CBjO zQ;B4=zeW}t780&pK_axmp)2*<&NM*IoC+^#6BUZpLlS@hd*u<&QF!DTW4Jt);njqJQ+$=9bAEng2U z{%%(O`_=(TMu~a@V0dUHBW1B4xl%Hvs=d_YTl3IyFwF_Pvt?rVUzuW6TN;Vsre!r> zw!jY#y)=uBy0?%bw_=A7c6<8tdWWGZp=*E3Oy2i7j7sFM)oPM|P;r`PIXDb=Ea*U9 z>+@BBS+hcck)G-~ElE~Nwduv*`_wnopB)AZQtyhzbpj5G7&{;$@?|0ecUEIYw$duXjSaN#8bJfqRE)hf z9}_JT^pk|*tKR@#0k%^V(JpcYgO|-wKdOE=U;Xp`yNYs&=_%mFae>)uK_S7fsA7@t zMfnv^JYEiL3d+evaJ~N#rq7X^Jnzp^VC*@g9W}R!pL^^v`24mBC@nQJ;#(a?ZN85ei8mX^7GR0>NB0%sJAH!l{n+Q*SJ*WaGU>{ zf0X=NG!phUy)TaqMB~2DvCz8(IIg*N^91D3#+m*M{Iw<8-U{!(1f=K@PyCujWj0?=uD`Ksq0U z1ftZLLq5MLk!p6yZvMVjF3ai8%@_RYZrEDM^3LCa>j#CrAGhp@3ud0n3zN9V0EY%~ zQtY5ya$4HRxgBW$MR;#;&(3P=$|IQd+OHks1qwzaRI~RwYi!G@(fz{~H)2PEswZMo zO=mXoPVMC;}1rnh%K;>VKe=%8jcbfMn97`CK#Dau7`AyZ!xm8#~E2 zyRxwUH>Qett9nt#*oAd9Wm4KQuIN~ zq)FS?Fu?Z#g`}xOR!0r->uQP>*|~u0C0$?OBiZS8Xf|s>JzWV{2{-!J!CYnE8Z`2( zFX*Aq2Wi2UmEa!PGgTR|t|QvAMSdX>7@64WrsX9O0!Gj2Y2fS#+o3)5ayxoZyYTli zST;*Hp!8bbat?aA6#Y;kSy)4vYYLJ$Ri>rsl3D zn4cJl56A4Q)>p$3qFGj0;DR>L%$mnBbGK9 zcq(%80d?$71lB54Ele9>0{d7Kv1${nVc@!a04H1h>{X`|63pu?dEgX|6 zyk_xVpOvqcMM_OQ?*FaGE4UsCXjh$|gVcblyRVqY8m#FA%K1IDewGpN&M-vRc$8ul zD_;(l__0Dqvs<><7?L#50Zpox`r$7(;&J!OAcBGgnmu+B#S8FL?Wnd{TJ^|>x-hPVip^v56 z>)DM8^x*G#Rj%~L(2MT1${UKx%un6EE2-FpF(O)ht_=!;ai@uDJ1?t2CqdnyK2w=- z=$aF(U@2sbQr^()?YAu|0JQ645x&Yq%tcF@ApaG=huBw2fkzIo{`EnZ1^NB+e&zUe z_Q?nQ7bT|q>38GOKpBB~3GY^8(ggJ7$WBjOQE}XjlcUI?jqVoHM{S3;Ym=MxGux8^ z|F2wa7-f*t9r0@+5>+#no;3s;4xFaB)$1RLSC01I)xxluKRv8Cw89=Ad!9GbvbD9a z?>>>B%sc`VS)##NS(;o~jV{7G<+ID>yg|UM;RU!|%eO&y;gTzj3N1t3WFeBGb8D|& zLC+h=W0^f4G%rIpvGB@cqeumtFrwMW($B|o-X*Hrp_dIbEWFXjHEuW03t-6jbfu(Bf+ zwkE62hQp)8f;Yy9ql=({d)x7_U5krpcijI_UF>|mIK|Nn5Xz&RUF&aq`{5tb+-2Y&qB+YQsFZ5;VZ(Vd5ii0n1e>XeOoE7o&_B{AlpNO3HQ4pN&j`L9`mbzZxX35O8Trz9( zhKW)sLc<$o@f-|S3jbJ$dvNMbS!c)qKAAs|$hdTr$~jAaf=bxw-E}?dRt=5Xaz0BkH~&=|(k= z^gssMESY&aLmR}q<0%j44UKy@>Dn*wZ-KP|>(qN~Xc2}Uyb03v;$We=CQ!UYvM?PX zyl~ZF@U!^-5_>b|#h$Zx^fg=p(|2+og3RZ!@2mv4BH|a$ETvWd# zAD7AIhtDGtUD8v{|ZGMKA~fL z$CS~}Bplz>h62VBK-+%V^lk7Zf`Z!PdFh1xALWr+lc#1&xu}pwz23m1>Nf{|t?U(d zc$AWD{CqGDI?P)&!!hC}xsXPcDijevA&vhG@N^J+L`Rq^v8-NvV0UiytOGe#1h7|8 zfYnb4rH5*Av<-a(I+bH5^j>}5-<93Cc%$um#GG^K>j-1nGyIuedwwUnbV+!JV7!xl z(uK}V&r4`@t=sqXoy~FJhSS&CV3(iQQ`#ZU&R{Fia~#vB9j+D^ebF$JgR_i_J>=Of z^|jLx!@+@82Nzyrt=lj+(Sg^I+T{75k&_6U#vDyW&HH*v*hC_%H_o!ahuuT+LM*c- zdFrGKzCl*_H>N~LvYhQHW2WZm!!#Iw`40Io6DjuxA-NE}@$$Rh$hw_|G@=+#Zha*l z<8?k1k@~AFaAS%nddj48T~FwObF$3X>|9~qZP%{uHUxxVfg3>69BzpA?=E-{S_gFm zjIHae^Zv&Wr`>m;)ty1^&UISQYJ$gtyjxi>#G#J3)(@pHe_SDY*l*NA%b0&+09uL= zwZ9_rzhtRh{u#TgTB=PoNd9>fqmPU9A(|37&|?1ngPoG(hV=o#sJ-iiQFtIvc!MMM zO1t1QW?GFHL{A@@LbOw)`^Y?Q}B5BK-Tma>tdG_HT8U1r3*2(ps2JV z5@QqA_3X4CC;y`LSgfRGzk-qIxpgP~le0iWR zoa@Tz97}h6ks{qG(o>}MBl067o>i96H z351aGQ^&3`@ZlHK_kWx!GL=)2PmqwpMYtaTxCMKwa#Kj-Rm-YqD6JhmHUxGc%5int z4}(c7a8h@7i6i9@fKZ~`CT*dJa8EL6C}FIu92J(*4ja`kSuqmX^nuRy>`%R?iUr76 zn)7So!z-f0OI7eKO4{cvf%p&44b~69nj6DgE1YG(W6s@n^lA> z(-y%PUT3TSk6W>6q)qIqXX8AL?+N!M>1l*R^P|zy>Je9pg!(t{ZZ&(N@H#o4(;8Vhv@{GLyx4dWYu~EQ z{ofmL$4+pVL8X3|)V&GW;F+WoBLh9SR6E#uHix<{&LY(~={;P$@4JHI(KK{^Nf;?_Rs|pvAgo4r^>Oh%Y8Wvbh`)O8f^vEwD!I>HL7m9l9ESx`aSV^ z;+~tgAzO@e?QM|{_ZIFM2v5#T??+iK=5BW7C`Pd- zy%iEZ<0b^O#OZrIDw=;9{=QjA@QVKgdXqi|i64e$o3H&KVAR&GxdsjZ@xs(UaCPLi zM4e>fH{ZFKV?$Jx<8q}AauA7HySn*byd^)7a&q9`qnkr(Q>!2r3sGI%*H3F^fkgaH zZjuo&WShoTnD{{cIrlumS6$mmva+3tS)x(B$>VPef$^x8Y`sR?9muHtuwBi~aq=z% z>}cvp6~d-$>}gKcyFKf%Clsy_&dVnf)shDWiusakM?Q-K(Dgo@9Hzv59S03MokB;D z4^9`0)xRK*$zD0k(e7)rNcjPUn;~bpF=dz%wW|mwo#eL|03vYL?6hJgn)eKC_QN5b z&td{$P|t}oOzz|hRXNZOx`q_;B0^=gYd;bQI!xnafg!!C^0}pi$l-SbHq&yCnX&+C zt$@q-I^8eP#)d_Ej8#5Rc(^_9luosT?fq`zm?K5_`w?6G z3l-)y2RVTWtX9w?N^x~SGuvGO>jf<>l2a$Uh`L2Paq&56e!swb2qClN*YL8^pn*LR zTSIRs_r}Oe%g(6Mv%l2OtZH?X;=ac7wiV=bLUeL4F78HO9Qrc}2<5pify&-&T*l;b zhYL_kvT}4V;pgvt<>`3NkD2ZsHG5zfG23>Vi;r4Hx`*QY-xq_M&di9^f?p#zvc1=% z9ydZw4D>~ZYMxCDbn^j3WzE%$&q=oq4#2R{RTOqd`2f~f(G&D>qbsNrJTmS=g%QGn zdY=}JU<;^4=QceO3t}g+;QW$Y|7I=8&2-o3~0M~3sLF)Re2cr_0|_BYUr$=&DK-}h(z_`Q2~0o}d>I1V$aO2Anf4`FxsY5v!>h$oN?>Jq{a z8dMu08(%xsFZ$q_ZKbIgtL63>H6!^SLKluN^$w?7bXqJH?{xO&TPR`T?T|kUA)+es z@!G1AbfOpWf4~JRWLiag{&L;Si!H~Mir?42^<-Vn6V_$=J;;FWxqlKy+U!$C4ORo7 zi&vM{t4H$;3yo%12)92pXE2TUzfC4>>8(wVWLo0509pcLSFW(DE6hj!l1jgVrAD9y z1qxMFf-Jg}kWw3tCH5p<-uQ5xQ8d~P6yb|$kb5*MzqUQFSijdQ7(cMG9G~#|tI`E6 z%`##4X#F;gt3xwI1FUSv`NrIkGOc%2T8Joce?zuoujyw+-~Q>9#sxu(<)^ah599&A zwrBYeH=QtP7oSlw1E||OxT#&|>HP10n}1o=T13U(%<#{Py^7vq1mkUsXTDDc5+ zm~vZ=D1DmUYjT8%HCLSc z{Lt&)m+@oy!00d&%A58FG;<|M z7}k=|YjM0=-c<8jtW2}{+N4_IeE0;h!bRJ3Vy@F~UdFwng^Lz#YwNbX8IJR9{Ws4RoRCL1 zc-nz(yh!n0$0|KqCMR&U7s^6Mhz?}Idz@JbN3JJc4PsXw@^LjZESz~yNaB}r$Bxl~ zH0dMc1Nc+kls}+|4KEtKjIYpM-WOejcrwR@_b9M=1dWJHAiS%n&Q9Fwr)}F+h`0rX zls#cNvN+@CRCkX7K6S9}PJkqS89Z8*Jyec4=FIPZ2b z$c%3k^VhX`lk&gU=1`o@w-|Ui@_B)zMTTS?@>ZqtcP#tV!G~TWq2$GC$zPw&E93hV0~bv~<&T1U z%E%jl7u-@e=Dm;#AP#u+5WqOK@&4BP1lVzh73!zGhjFb+4)460EPN765F4Krkx>Pr9q%7<3Y?ycZ1#^X)9=>dMvmz(~yOd)P zJCLQ$`FUskG*Z20wN=y)15T1+B3AyF4hc;PTs@|-_|2@dEx?(0Of?KJ0lMJJnunz1 zQ4K-?idI93G|_ODDnh-_v98Q!X3|Uv055O6&QLIY_i`*Q;z>M5!~_ z9UX7|tqr5Un=-Y>v&;F$l|HtZ6OjKYYRFu>U#6LMdUoE@aDML+``I9#{H}`EG zD{mjQwLrNfhFPVYW{$2EaD#!A|M|H8czHUQYf!GpwhcI-*!1ch>AEwug`&&F6HP;o zFGxLpUe_eMA)! ziZHE+aAl3YyECK{^~Pkw!b0yi1(>VdKw;s?vH)~vlf!Px3U{Qg?R5FWvX(23Oy8q7 zN`lK4WK zD6~@M-xT>jZJEdN`N7Ui(1{E7Fa1tyd^+a8b=I7z*M2ALJZ=7BlB*<`lG%ppm!?85 z(4L5kTmR=+OOBlcRt^qY6_B#lJ8ylj^`srtuXPcWB3vB!wyL2289K#0$m9H=w>?wV z^O~}?ZL!(MX}Qh+W+lU8#OH*{+Z&pzEfJ6-h-p%dUVi>dPT+K0cC3ekh-BXO(&)RL zR$JNG1o05bHRU{PH^wY@Jkf2c-RjRj<oKaC!UsiL^G;e^A|jd~ZU~P!`@QL6G#gKxm$t0O(bAei60JlxwyG zF$C<=xqJAOBsM3fh`2?n&AML5)d0*+)-eoPidnitE`7-C*b{Ejj`!jQ` zy9BL%X;}XoMG1EsD_d(>A26Gs-E7QmX+2i5kvp}-MGgS50iBPsDQkR~VX&*Z)P!aC z?(~yAi3R#ivHs7SGVSFwkp#E^Y7*M>=gI<8~JYtUTNMUj^?a0SO22f1VXO6dlnsrj&B*KERnhqKrYT;*fb?V^%-2u%KB z&fpSGoD6dyzttMQ!{=i6#e{_9%l>0xR!w>S+9o@WBY-;O0mk7vj! z!wb9SUc$2P4@J}G^QF;qw+{H%cKwgS)P5HMwCyzf4Y@lzF!sGKRQ_X%xJ)%~%JMDA zXvHHRm-6Dn8$JjDjXtQ9TK}rf#U*@0s2ODuYNpoZ(1f)vhr<9RG~a3KI5Weqi%ZPG^7 z`t$8^Ok+4bG>g&!!7&Hox}E0M0x|fuFy6u>*>nFky^Ei6O|i#+mX%3QNGa6m=8`%8 zv~{yC>WECfleD^9CJ407Hr3IP&|@^+G$kJop8NUqcMe`Z)c?V~%LRQpj?z=71)944 z9{ZW#Wdg0v;o#^s=IF z$YL=6*%7UyV1Zb!b<1BLXtn>XJF1nrIUKxTK9vY|8% z_OhfTFiVg33r7Zd3<&n@ZYCBA2MTshCBhm-MgLm*Ej%PAcdLZttL>@@^)^`=k>wNy zwME*!*9?tF4SzQ-ML3_91kB>&lIDgk%-T+bv3*}>hs!ng?+;B`bAg$Rr;ro4)o{AC z=*08oU|;s2vJvQ2mmDRaS48ra?1SRG1S2!tHf&~1T8k@?wsbyjv|SpXUX-x4bT#T_ z8d1@4Ho}ZiF1wk$f?(k!Mi=1_(W$o-hzdW&DYb@x7{XeMh;v@qWM7KA7q2`IZJu~l zd%YJUKHopTIo8WZ4cktis!1=fKD$Y`bS!dN3`Mw*hy9wrL$`Xv@Hw2eGpNKZs9mbY zDD{IP`o)zMl2~|F>YLl*U>Q-9gQxa>I2WIc7_a)`B>c)qJQ-*Fe!>(F)GxYpMZcP`my9%9Pd$*68Sa`NMEgA}BebsS_%tpRL?BHpgLOD<|fdp#@}<8$TWm1dOt zM%R(!n8#to|244_g<7D|SwX1j>aPUjSCUz!S51#_t*Sm zer%LK!ycZ=;Vp=qv_xl(Zyxk=XToASx9sl+2B+)&co;HrB6!UIr=l=EJpNFD6JWzB zc(Z?yyZ$w;{Lmu+`=bP89tG63zXJ-iGWrr3bn|6|z_hEXACUiP3)bZ3#JJTz$mLW1 zrHbY1phjOQcOIToN*5R0NsmezOvD-LImcR8r)NM1*w*`M_L){`ahDMWaE0#=N(9nM z-lz$9*h{&9L9S2$*c-6gcYPf{Y`&%AX&n$)QM)ATykue?M_~H9mU7hrDSxF3aPCzx z{ar}ek8!Q`htitS8rv)2U7X}z3|h1Vj$5kUWnB>4mtVHfcPtjf#j zh$i()4+@%I{kU&)|7{mxuM6$coFm@W#RyO*O|`#x&_R#HsjmIFv&pw!Hv^kCtPP))8*3C zWeYKyjs`PcrILuk{We@&Tk+JDD|`&I8|g3REkBWsg*kr5zRp;4ZevDgkzm;8|TQLzd6Hlh}A5E{>PJ zIAz;`Y-FJz5``a?^z9oWbwz%z<5&Vqp5#$1d5+hnR`;l34Ymh^RYXh9)VdB0gz={~ zqmG@gezfj5%Lx|CuDWS4Rruj`l*FRKn{eFRa_k4OFs-@ctL;!|lf%B1Y=qMBs93tN zQB*mkiZ`VlWg`i85_sZ}OHe9>)3Bj{KFR3mVf)5Et$K}_aD8Q!)k{3r^e`4~TiC20 zO@*{P9){-x?UT-NgMG&p2J`?9Vlh&jct^CvhP7Ds(ES)sr}o7^>-y9w2z=#z(a1bW z;h0Vz!rX(?JSrrkyfZMe{}5j>?2Gs2hbs$S>mk#en8--Fa4dBpFXu?67 z!`96|^w9IU!vLcz=D*C^Q`7x;h}SUZf$89V72QHn}|^-<$%v zV$$rWQl(`#d56yGC2sAVJto#2SMYm3*Z*b>TbbFf4lse^-4@-kMHOol#DH%&#`Ij9 zs-_rM!O#nX&G7C;(>{@m!Q3)#@96v@Atf^DEr1!JXnf;SmJQ^K>bMY6OrW-pHRTK2 zt4LsvD>PYi0XhpOZs|Do5mst5=WWV)(Y;?Wbv9WiVhPh=V7Z1kqC^i?CiGLCl1$oPgXiM z*zRq!EW1^HF5FbNY2#@Mci$@};BHc#T6iKV(z&v7_=mo+g7TOmBW(G)035S=v7+TJSodaKerJNPAlw zvC-qk8|Q!QMHhhZ*}C4SRm<-)qI7n`Y+0}<8Ihy47~EPx ztYGp8L-K+bmsAG@y<2r?4Owjr2o*S$yxW+g@>;c1q7w>jXKV>ZfEH!^pIMyy-3YxG z2U~L|d=vA=pGjb0XJz|LD-^UMm%6dr^}K~Fc9ma?gB>5bf?C?|Xm9nSfCQX~crS_u zn~px_H)D4E9kX{VDeD~o7?O!UTYvT*n~-G=B<1re;;m%v!*sMe`k4NhAsp;V* z(u3KS+FV#LWUT<4`Ho}aytu}VtnMdzDwl@d;D2|?|XJ67yONO$5dlGBQ zOKpDq!pqHJ3a&PIV%yk2K+A)sC>YvMs#s+=D4dqtJ<*Fohh|9TIruXy>BA>c9uEEU z1rMY3uv4S9G=Tfhn5ppW2JYueS5vhV&u|0Kk#b$JpvA5E4C=Uw>&t4M<oC;B{IRpRbom(z%Vzz54$<9LU7kpUsm$-tMQHJR zXga_N#ndZ7cn0XGu4Dec6lh;5-{J`s&FIAa`=S;MOi0KRc5D88cds6%_ib|%{!iHR z*T{qT*IoVMpz!eUk>kBua7wMaonqWD~}{yf4})8-m{+TO`gyg@;1+@ zh=EZK-2Ch4EzK}dTnz*|Og$A{gCJ3Rp{S40mOc_IY zIl{ra4%;1?aQCM)$D++JLTLZ->ZUE@oe(I@mq8pt$fUGnHs$Kt)>)Cix%~fk(xX*V zFqH9%j<%!~??qyfP_-^)4AavyL119gv8bR63|(wJXd3IZ8+^C`gx zN+#cm;*8c83ynI$+3dUX^fHB?eU&4JH2=uoP+*$){|EH=K+23iR}M^P z5Q_Y8Uw_v72*_C>c2E6?#gdaZibP+dgs+5Sp>9tiv1`aeQ-i+nXh?7;e72}@R)IgI zY>y=5JYLhupTXBc`txH|e=J2uu>hZV5WyOT$dvtjxot;zJjikHRHEtn+<`?h9^Cti zUi-dc__gb#?C~KF@dl-WaJU1Lx+>H2FP(2LLj0@jY-OJjXPzI|6PbJ)R4)=EJjG`b zSCdkA!Q7pC^^^$pLmSF?7<&YVVgmC5m!)yGKamVI@geilmw^F@Wa8Zqa#!@dOr9POM8pWcpZ-?UWKA^ z^cpMd&BWjLiy2-@mx*NCr?{R+N4+(q+CUN8z)O>eNdETxI2}L30c=WVvA-}jeN7mr z7RO>82U9vr%9AU)4TtEWy$Hn&0Xwrh%ZJvl2~@JbajMD|IzB8{)m!dd#X>ji0qN@I zaTK6ZjCs8rpN0k9Jz2LCC;j>;ZLXv4uydE_7v3_eU5##5GSoC@Z$i6S|ER+eeHX|p zD+Ao#LZjLL6@~Cmpt@LBd!F9k0jIu#E|teYKDW_Cn%9m$#G1})o2ch{L(+wfi16u` zh-_^xri7ukDrL$~o8RBJcgYcMyFMf!Anr14_uBlxog(D!`baXMn$c%TEQhct?JZ== z4ZW?{$iT0#Qqv-DeISYFs85!YptP_|M^Azf55~C6qiba!Fc3o3Z>rQfsKy6;<09)&+t3z+61sx z2H&q!*p#+~KrA2EVEVvng%`fyJL*{Z6oym?#NM^AsU}OF8n04-)$x;3&Ca(;fwK5s z$-;_{6^dcL#~qw@%Ws>g)HUOA+UXDbYTAkCyMmvW_zQyfsq z=HUK2CeR4{`RW_M{n?r40u}YZQ{i}siN@!_#J#wUz&YFbu^4Y%u!LUEa%7^&mi?=L zxXu1kr5(5k=3`G+J}6&uL5{I%DLTjopNbn46BVAjF4JA|%Vu;<(EYX&^zO+RU1QRL z+X6;(kMn39_dCc#n&e__Cnmi|U&3$|U16un2R4YF{jAhE1{V(KRK8m4p60-I?s`Fm zm4D)9Ns$M4f%+2H`-Xm@VK17JapxH`U2X!eS*=AgQCP`_KxI}XuN^~$8!uU<@JZ{b zAlBjx#F-m#*DaHyD#e%5)z^nJwq13kYKTuqlAHd5X^f__IqWhlJ!IaB0vs?Oy*A4G zy)XP6z%2e*F2!)-QY=Ns_Ux(|h>sCw>$KQV_~U67PmaDIQ6%Pa#zC9#PF$x#`j!fl z8e>llr!H~im2sjS;Pf)0=XQb>Cwe1MkwPPFGG@2sdjD5b`5m6;al3NT=q!LdaUYbqm;_`R2UDrN5d;?lkrJ+50Q`j-^Z>xyObD@7r-*v1~dCu6QE&q)cJ8y(k zQ*?}s5JlyaOqDHdt#L7Af_%PQ`PG2TXR3f-I81YmIXo1y_GM;_0a|m7@hl|YPM$AM zj!*#FVBAfXPw*n1r%FbDw++{kK2XIXHweL|h*EgWun^n-TYA;%^~ZOvuP{eQ4mliV zE1zfa1co^>B=oNhZqfHMF&uXC;jdZghirVz4KAo-v}0QG)m;xpG;^!p7yEi!iQlxK zBV_1Sg{l%iI+!q~ynz{u*HX%8H;w>Y@U`*BN-O=P z*f`FzHdVezG~iCjrjp*);I`{Hj@Gbm9t)Q!x5LuT+mP*_8mn1`DJ?z>G zj9Tbg`nK(;z14Z01R^nDNcr$Z(&#A-GzKT(EfIN2U^P313k^66K@5F~j5lMU66X!y zC}kC>0<~!#lW1-hSQmCkpj?D_fkB<(EL*zpz-og?>*LZeGdxCdzPOwqGF?$qDiPtx z_w8-i_Iq*yf&o_eAK^x=ks!nE&aZYaFOpOYg06Z#tDClh6m1JD45~bi)%rF^UABli zPQ*XH14FLz+w{e5P@O2Wqa{q{^)nJHYwHxgmQ7#oP4ScipSky=|H9}8WL%XXsJc)MGg12n(b0qepnb*3nu7EVbhE)p9IGzh{SDN+S_LZ60fH7@WBwPhC zD=J=u+Ur_c8W1r-Y2OwHsD!}B4H!E<(p0i+sArB0J4u!r(#ofAxaBkp+P{-6E+H_0 z8$e#0v0yC)FqXQ~%+>10&Dl2+=+)Y58W!M%HM`G5r@;G751MxKn-9bMIOgTLe;bnx z0&y(_?ChjhE#8eZyF_F?9PzM6I1fkGP)D$cZalIrQh;cw@ zV#-_=x)^5sqk67YC{-oUkl_EgK_A~Adr|lc-E_vYfJf%$eE#(C8f=n}{dqL?eMK5D zHF-Tscbc0}`cjRNre9>|MzI+A8gqoGo_7%svBI4cBM#4p7q7ZDtr;-wJflFmFuem-f(}DKz}NffNZet!Gm9a-pEO7yw<}H@lk2xNE_Lvo(d2D_9Wm;DQ-c}>7~#jUs;H3 zoGNa;?;9@wOg>$LwAR-Z!@kKYBZ~N@hZB4_wc88i%~a1l^hM3%3dhCchi)}n9v~)T z{wJ0~|9v^7g_&92RpFT}UFWg>ODg?Ls===o9qi;LD9J+*LE>Aw_qj43b2PX*_%1`M zqM`sp5HF`xaUo%@w)zggO+2rul|(ANoO;v+>w0q3V=^z_S6}Tu8E)d7tLL8nP7z=j zjBavA8)y++U*D2_7`gE(-kG+@6MKd2PuOG_GWEwtm1`POplSDF%D<-EipJVrW^i3k zmHR8u_Xl>j?bHhcx|{->lR)eQHg)!b?HO1#_dwNgrKCPWYgBo&F!r- zaK@EmC;PVsM`S`s2o*JBZ&#NPYo*Tf(sdW%n7BC8m?QNfvZQ=oVX>Hr_KT8mW<8u&1-E|Y zg{-=t2_k*n96%)esnf@`#TX$lIuq$>gEz*~`5G|lt6gmLEPjgWQRD-@kQ43SwZO;4^DY1&#qD%k>%A49E5!c_rOd7adrO(G-&OwaksKK|#n z_1CQe@g;xf(5tjYZ2I1}MVqS~I0!7poo@*5?-z^hm-!lG%NngD2zEm|l9i2f@2Lm_ zRvCe3e?*lTEwRg9kBg%|Sm}>{zs5bfr0ePFN$SmqZ-R3^gX53Fmpn22mM*!YiV_zt z=o}mEnBtmU+;n&4L}Yh|b3XHA>vOMQm-%B{`xwg42vu6{1#d?4P!jGAz_Oe8_eDE*$mM4v7NaD#y;esLY-Rh0FX5 zG#0?QRl=T}Tt3~2fIm*^_2x^-0Hw>3`+uhu1g)55)zL9F@A6eufsx5R6wdX0i+(;t z!l^8fyyXT%-MRm}CsRE3nWQq}m3^SY>VG zz^Sdy*>2cXZS_lwlJu!TrMi}>bpKqh7+B}qWF{e$hI3HSGK9W8XVOTPx}7SqYTBT| zq@hLjYzA6Wv6H>U31!|viH|!MY1i*%q^DE0n}4M1Kf%E_JIvjb>03Yg)btctlqLw5 zFX#&3Fmu^{cwuFvn9nDP)deaA^CLZ6k-BxK$DGVZ$8iFJ?J7RW^t7@Fu8udJGKSBl zKpmtg)3vsztZ{Li2PY}zR72RqlWxzgp!zr<`3Z4G1rTKuw0}{JZov;{JLJu&eLW>{ zXYwjBXaYjCTu-3FoKX`X?aX>%U~e0@TmUWY#V$3<6N6fIF!TH1ou9_3`xzszyeB|m zTl~E$UZ?*FA^eB>B$>|lfq~|P0q)nISt;dgjzVM#0(3!YTpR$CRTEm5?*E)d^$RoeGR>z>rms9*^#vHG`|rz2lUGe(!2*W<+#@am7UGIbOB zDc7pJ{Cx65Pke+UPDO)=fFOv4B$_$%2iPx{uwf(IhxlGBKtewi`<+cA5$0la^}5?cc?0A~4oOL%T!t-OZx}DaXDgS$&4LW-x~S zn>R@RL?1U{TOLxo43n#q2(951U5yq$@V4-7hBKwtk~gv0yFNy|EID;YM1bZk z+|6Q;_s@1ZE`jO6tJt?%fRY7SpXEc(B*(t%b{|Kkl@&`e{Ga8Nml}#*-YUw<%nAKJ zs!Y;#d#m>S>M5}^=OFX1DU$f62e}S(_n~k@557-AhqHrQ`3|gT4uuqdh%8R!WR=~(zV$HVtoh&N zg|4%~Kkspi20b1u;I{kZoSAK(t#v>;HS~3DKDN*H=74EvG_Ncruc=#Z7YjD-zP0lo_F`<^^(j;t%@sApLGPAa9P2UMKk_oJrO-X?*!94-VeU*7Qa6?yYzqgFANJa zg^p3t9dUcV>6^=g2j+@%%E&*GvnW%N$S&b_;+70(G)`fSTIW(+XFm0y_`s3-o~xaM z!i0k}V+L1V+X90E2{Cb&3>&}B=*8!YzN$D9V2G96r7EPZev#BplCSn+-21rl%#U@| z@4eYL4Mme7U-X9cD5t3o)@giN^}%IK@2fhfj9Zx{zA zBT-`*)=Vs{gojwE=S6{#hu6gTm>LoIancLZ(-99Av=CP=!=1EeOtTDm0Q}}9HuY~? zv}|v4zj3p}Owc)O_y*{P8u$%7qlO>f4#)~kW_4A-uSSoXF{s3Wp;BBCv5ZT>Znd_7 zJQ4x6h@a)6OP1>J1)RstJKi_bnEt;vfrNXs3f$@+j$b4xePa#y!+D~d#!mjud|W;z z)_f%3StQ(OyO)#a9DQGNqUp^S3v;-?_~^DZpF)_few=2x^t0UK?Bb#h7fKSXkc54w z?|a_3lyQ~(;KsKDf%<1A?m>S_j{)x84J2>+^Uah0Ws8ERu;Lh5G%hdo#FYoaJKu-8CTFt+rIxFv{EOWfa+rAhMQDaya@do6!g%XPsg=P zvN5aGi_o@{r5AOZb@vkO1{X_BKC){0IbVWV_7nKMNrFB|u^(+Ot_uoWmxf0$-icY% z*Q@w6>%TdbMRFEwhsu=m>lEYHRxw>6Xe%5pUY^i<(KhUdm2R`^vCiKB1`K{yAmh8zM+q0U2=qxve!c5ESa>)qunb!`pKU(Jxi2zOVZB1 z%Op3H%#EDn0Hn{cHCin(AmLPuw9ms>TD}~b_)nsUo1l~BbT@a7&HPVd zn+`4`>6BZ%=z9I93cE}Of3QPMr~mT(73LvX1UpEs|KBL3kCx7?3kX=O*sBmtx+8^zR|m zrQ2KISeIdIXpZT_3J>E}pHsD-u5Llhfp9AaA?&>AYt$4EeVYNKm8%1l^6drwT<%L0 zPv(uog?Zy`HizW3%EhT9hP(f97UJUmc>E%*ln24caQE3@BccZ^c?x1P8y-TI8nt*UpFFD%_}x$S5QD$~|dpkZS)_5NQCqkc>W5KmNbo{554;w2_U zI2*cdB(Y7t$u}&vG<#m{8cE6KV$|O}iwb|3vGEO7h>ihK6U6-?CCg3}jz=+IAzQtA zQM(@X(B)Ye0RNToEZ78i`ZR zX}`5bq0w`O;2`!d+e~tuykvO7iCl~7+4>wz%XsXF=_-6}d(x!%H~PX;p(V)y5gUK$ zJ<2+f$8&gjcayU>{;3dqSjhh5MOEobfOse+VE|t5^-`YO*0cT%wv^2w%}wA$Vo)V9;c8k--8q6G@x*jB%}Gb?HBc_#A@ zkr#F3R8^KVr*o&Yt&uDhZ*F{-&X;pq!h5d}r&wDHKSrjXKVMt7Mtf-STj3!x^?k!H zBm)IlN8P*H-1gtSE?$bMxIM@Pes%4VVSt=#g|LxnTpOkib&?Vmor3&OSgr@t4;|Qx z7bh!CBuqS+G`ivZPdagbYH?Ey*m!#06Dce)_Q(a0nPo6tr6@-0x$~=m{=y@kUTc@(> z4bJvM3n*|Todd|SuJQrxZYT#-ULLLEV1^#?I=0seo9EeOR^Bctpy*0djVkNTM(p;0 zu_I2!kF16A9tTQ4AG*}gP7x=Z*yXWwN$r1f>fyAWh3v?>`K7X|-g;_1zj7^jw`vv; z6u%$9`^ugC$#W(gPRM^)7j(j&4f_+p=c?TCeH}T^6!U+RIQWHB3%D)~S~prFY$B=#N3)ooe30AQFL*WekAn^Iow zBT8~gZ}qx3$C6I1!;yI^5STyX0-~{zd#)#EIvkF zkzn3Xy`7xLGB_jJ@iianwy3*m>^etXd3+mGB3tQtOkK_=t?YC{tg;!T1Mr^@%8BVh z9iPTIerGT=!W^|Cl?i(AyBnXGg*BBJqQ>3M_cp?{ig|2N8t#6fr>kKVX8e{@25E;= zCD2K_5|DZzZEgViaz}!@&b4FulAUbK%HB}Lr}4>fEPd4<%#zydscABsV7+l`3F5BR zVRkAVOm)`OqleW1w4KxUP$*Zxu*&9Tu-!|=h%-l@e;`)s861ab9yJ;X>NZXbo%l)D(`X8{L=ow-yh* zAt75^F($i7C3RO<%JZIsy87LQ9VNUM7z{Kvh$ZZa8;WuV5=B#T;J8`cdo)iy<@s3a zAi%j2No?x_I9K*Mn+gxBqv$QHF5%NlgWPQpNi?{eSA8ZM(l>e0g$B4k5FY+5!Vz6y zcWh_+mP{+-GTI_gga>ME=|=RqXZ^g002Giq2(c=DxW0lJ)y<`2=vDGb;}37p%=lMX z2C@>qD%XcvrkM~WBDyBe0J9fT&vGy}(@B|fUkD$I+`4+&b2Z7voO zn}>^{Je`|>7YIQqH@`ca8$-siZKpL{9h$kfX;$su&$yx3-VG6hKImYLQD1@RD}W3D zi>}Ok;B6s#k8aV5%uk0QxLiLquDjf0XG-1xJU5XGBLWDd2;;;aN0tm~aD|2{ z6PH*OCBC@9EDvFVs!UHG;`iMHLBhu-no4!n_zpr!yOZd4KIgr>iCzqQ?Sl+?bQ>KU z6y^54g(Gm)u4u_Sbb|I-S83ZOLECCHGaU|d@>}M#G>uzK_NDK4I#FwWDl~73sZpl8 zPTqucMeVEM6!_BT-pJEYMwaA4-sX`e5zX=mBYq-zr%l`iQ5`J}9)yvO0qGpNVaS0Yf8+5y=REKGf3N>sUKc7e_r3SN_g=Hs zUVDAMhK&8dprSV>@p9^(e8=rtiG9^*AZwE%j$sBDPq1O*tlt`7{VXSdj9)PSNTYpK zd^Qx|w&YIRyvHiSjdC)43pc|8YraNQwUkr-Q*2Zg6|G4srhW3^HNA4CgfEwyayQ4r zsw#%lk)N7Rm@PSts%$us#F@9v=+@-C&Z5PMTEm*(chERNdkO_Bfta^~KiCrHt4Z%~ z${8Kbsx?RoWKDkdmgl+qrWU0Vb@$2u^(NI&b~Q_GTXOLWni%WI;1$PaZt4tkEI%b| zB}VpJ8K!k-WS$6e^;nQyf#mnI6?9z|2J+*p$2M1Es4ic7MSRu*n0`&3t&oCPbZVQ2 zE;Rf%_gXb+U)BmSZBCRDKCz6LIQ`sMdmK@9aB~cXOkp)%*dv=*#$5Md(#y+1a_K+57&aHp1*~N?pX=le%frCyB(5m)j z%@+8Ybs01~NWgI7h}6WwdwaH5BJ7CjFh(na2s=^#D!`$!3W2Si=%>yTyrLeGY%+cC z*P6Jd2oGYl`=7jsDK9NGh;Mt3bGUkJa4p|5Ig>JEYfy)X*z&OD^p`+e>l;nbGtw5^ zreE}eJ*r5lBOO#4%0!Fgx%)hPZQ8X0gR>4TEvzr*k@qzKd%a|J-RW|N9LlDwQ=VAG zx-3&7Njx6{BKG=<@_XxM-nJ<7L1wxwS>{?Sb$hM8W?(_|#{FtwD3D>!9&0PD#V2%8=aeS&rxntQ;C|qq29TM(NPFvey#96NpFzj?GwuUu#FBl!i!@EbjF!b}JpTl1uoHBFJOC?Jb&=_6PawEyl7 zbg$Js?JT?_^JBa=|B}#SY{MSW=!rB+1;yXK$vVPzIa(mZTm+%}uGGd6UDg-vI17FYRP&+;gbG!HUB4i9*%%%^Ln+HHSL-S|9_ zl5GBr7r)BQk7hVBgaOJg#57h6IjL5g}>R<|s15(N3%C z@W#UI9z;CRKYK~P*+Dq3x;$ph6QJPa!ei1#Q{3sN%~=>ESbLgo)VjO_&Vd(G?^P0^ z$^87OrIbA@IRWV5baI((;ayO6zmEOZN|6>4C69z*U7j3VV{7{JR-q?Njxx?Sp5FTU zSqb5YJFRj0k55e3pjSd45>L?_5$EH}>OJx?QBM#K1#+uUF;0}Z)0**3MO(=d4I&yl zn50iy$A6f4Sl=ftf#W6*d7uH#=BidM(%bog*B@?2R@Je1##0Ih!d;PT*K@9EsC4T#?_u)ie;C{z^2YwzPaNWQCMcg^)DVudqcMo#M za`)VrC#Yg)izM)_q8T_c;O^Wa7DnONG|>bRF#PFZ`0&sTf!@CIe;5}&-tY8mtA$)` z&>(eM`VncDY6PMS=N$Ze@Z77`#BI+Y^ZM_!>?R^cv`Tq4D?*J;ZAj9F76Wo391MC& zf`!>nagN1UWz)>@g_|)Rg2|si_Bc(Xlm6goo3A@XnTFI>EWh(r7a;at{MvlO&)0+~ zT6q^=iiQ%FYqfqgcGi{eKQ(*Pw3o+{85foy@YpRpp?U1HDt<_{>sto&Kj)ATOkd83 z1d~Z|RQi;?;}%36c8(hZx_)^rVi(<67E}+%sN#3Hs_4_jXjJL&ak2uTOa&q$F<(0GDPj)ipPJk6W_}+mqzt@2<3GOl^E>I?uUbdc<;gff zP210=GiEPG*%81KsZx#ZpR;I24|B`{$M-io;;w|^fOTu{O?vU}A3sjGeaWk2|5pm; z%};|>15;ChjhScY-guZ_p1Ozm3w0|~r-t9Ax8kCTqP&^fVYhQkl{3`!;9zR49KW0A~`|8iIng${5g z{&}GZJRr#5o<}O?KNRV*IW@C78h?lH*mj|1-~~cGQSiFsas+PDA@GjU43x3~ZWLmt zI-BAq~oUbpx{!ZU2TI%x{%bI<L{cFQSvU6swZ!p@OMVu+4ZZ?Y=Ad4FLT2h!z{; z)gwkpyixI<`#>V6D}x$Ef))du!uMY)brFcTq#;Wp?PeX8ZVoI<%hqiXpsQFDBQXZY z;H$3+&sB|W|3@|(F?YIaIbfHNAWpHP#Vo2qdva)J6K?3^#{$kP0hD`!AwcuKU0+ft zjZn;L9&M%wXHbEh?>J;88b~K9;J@<-cI1bOx(p!cNTMzf>_>8+_}^n6X4&=jH79(} zZZs=^VZ#hJ!hN6m=Q`(;5Tu`G&%8y*S<3Pi-CCwP@lC)cuou%j{07yzf~)k4JQ}Yv zWJ>KbT?{mV{Vj&W|GyGntn4Yo&hP8!AXR_h8)3;S8#c;@?B5<9ES}labpLAM;@}86 zw?NsSadLJg#s#;%ulc=_+kR?86Y}=L<)JUd%|RT=*58MGdhc-W#4u2CO3uHB!Crax zQSHpaWjxBHI*#vI);O9!S$5T9HRp~m>wU*v_88p;-CwExFw1)zfJ|MLs_-3Ps{0xP z{=)x02tQ@}X0+>0Z<5}lWQ`asN1G$}8@V9<6$eDZXz#DRUG7T_|6pb5q>-pUefV z4L|+;RGgJckTG%me?R!J=nxEhHN^qL?x#qYNt;~dQEr&Y&hMoCH1?pr%ijci)u5JFWZ3|NNSq1*mr9U8J*XQho+S-}g+w|5xF5bWnn3w@o0HWnKACzE$Kd9@T;EEDBS;VFT*kE59-4(2 zfmA~R3RNY-&8g7b%!n`!9zCimIYqCta;;$B` zbGt=i;^|V;BqHYZSn$u5kAqz-(`hc$83{GN;^g$4!S#}}yLer!%>jw3)8W<6o6#W{iV@6iAKT6>OGXWG}2WqR9JyAn)+eeb)& z769|LKN!(t$>rkvbh`80wFfKa6Q|$OCf7t*@=&*YEXb1l*t=c+p`kfuTbqqedk}#_ z%o7Q)J_K?0l2e5wXT3pxJ^UVhdiEo}YZ?X(!xnC?3E^j^qR(vKiZ6AUkO$B$UiWe8 zkg8L6A@sj!wvM021g}?PeP6#+hY}Gg_!M{vrSVO#gRIrpU>LETTgj^u>KeJ<5^JnkPO_|^YOFOgs{Y5Y_)XV*q} zp4p}T9;al)0mYlipGv;H4m#mXQeS^dOs}!H$Ta0UWVR?C>26}`>y74^_=}Y_2#m}B zfOeG6zR6`U@RBRBfOIfkwTKGGoK5{I^!Uk(<6W`l<_@(8VZz|$IqZ%Gs_b5?t3~Rs zDN*lWik{u_C1O1DbNxWxSQpQlnP`cI5WOWP14h4r%~(M8yf3n!OmLn6 zhGb>1^33~gKnkC%3{6%1$cCzZny-z$Tg6Y4MDd5h4N4#8*FxhXam4`sF!DU!#vdI; zn0kGB&1)XtF)Di0TGsM?OZsp+9F@@j9MxqB={{LR%= z_e7{1XOZ6~%pvd5wXt(PJAL8pn0m1MFJgp5>>z6oR}uZIroeQy_L*6}Krk|9B}ShD zA9*MVwZU<;%vN ziO?KryV-G+uow?^F>Nq_!-k~Y+}cH3L>Ds0fUOi6Nh>2@sR|VxydqOGGm)sgt}cac zlmWz<7?V?WHnbB`qeqvEZny|6*Mqn2PgB_P?L0wS^<8$=nwxNtp^E=u{>fVTXoo9w z!u!6GCiLTVKAInBjMoqylxAi%Ej>R<6lZ528=s#59-pOdp3|R|KFb#m zjHkiQL*YT8z{8m8N-mL>xGWG;Eq=0+fBJe$r$5Ekm}Tp8k>3zc@}qL6d1SAEMDAaU z4DrT$i8GX!eWgyAK6Ouqw!;_pgZm0;pOwgIV19QISgxsdO_G1L;nt!6s?|;UAR3E} zZDVU2(%Tu+f~Kox`qc+P@J^AV6gz#9z0gK=x!8j9yV892hSEr6Ey?isJm0!1(ZIoA z60G#ETQ^F>(pnp7H^)S$`Ic6Fu-mNfl^orc>r%x6Ed`6Z4|ZKmq|0(Yd+eoixGy7N zkeM3#uOsItM<%4sYqZ=4p~(AUl!3udY{@^JlV9DABkt0 zTmBXN+#s9VZ@YHpb$pLs_xe+JnvijUMGy2aWKIuf8ov_me5~SDr|uT0BcL?ajyO)ij=sOM zqdL=zK=9oKA|?{n5G@Xk&xzo{QXuY;fgFDmfLOQ*+T+Ge*o&yZZ*Ds~Ck0Lk0M$9o zY32^=tJ7Ekdyndt;!9u+E>_lYZbhW^2y&{45@B050>xQ3vwqU*=!bQ)BjX1PW@|IH z7Te}Z-JAcu`F%9z;!@0`iQr)drbR1q z8+LH>AE^S`2jkHBk?UrDvv5wwRoP8hPvg*veBRc9L!g(C{5b{Kucp@LjfPWu$YRl$^Wx>CBBVEn% zc=J6q5iC#)Q|CF3uhj9rWV4OaRrcjObZ<)h5NX4!$I6Fik;Kt2+%Kj+E;@(SMj$X5 zzARfwqslf5d~d{0O*O^+?=Frj3^AE=BBNpA?ma|Iok#05Ubf)aVj#80r9bi)+(5kL zM!qBz)GYk@PE|DQPI$)bF+U)-2yowa+|V>(UZt3pdZhc)>Y0%LVS{b_c4(8~46k

5h!?G0QU{3_V~rFTR` z%OCnMwm3c4)E2Md@X+n${{}ZC|3eUFcvvoupEnl^j8yl2eYH|@_RQTH^_FoWs9Z@zUGKb|9EY-f;Q;b8DP9!g}|$Pd$L#; zev?BWH`cb|+?K2=OhUOZ+xda++@c$d&!%bL)}plxy)?k zB0u!mw|?N&yC1P$g?WF503H<}(2C~A?46$yRc^y;C!^W(MR=Y7v`O?H4nb)4kfZu+ zsuUlcq;11a!tzgg6XDlvtU+h5u>jk`kgng{BZlCsUJ567S1`U(F2-E&i`*uuZ z8WntA+S?uKd2qXDJ<23&U+Bu74If0{8(D7y4)f${y!yD+U4nHFZeyrKyp)|xB03^y zpwK=Aw~aDapSEEO8{cCbIm4o4JdbRlM$=i= z13BY?TEy_hNlHZ45CNa)zOPIl#54pG)}43FW)BOW%&F_QK8K0C^HV-Fs`Me=n`5G# z!y)T7bMwG19{hbY^v|EwgA!j59}50)SbmUD=AnCVBa_*Qq|>XiZ`~?M!wKp_{7iw) zw#dJIzyi4-uE_2H~aO-K+8 zlFn;$4_HJ^oe{HeZg8pb#pK@Joao6vmPRCtRRGr$Oy7RC)NY3xO7K!jCVP0TWgiMC z9hY@yXW`Z~?TuEgbsg2+^oAc&ILn8;{BBg_HKIz;#&04F%ikVWuHOkf_St-=NA%Ij z@FvRV=_cc-DI2#mjmYtV{Y}kN3M&CkFQ*j<%E*__CRA&^qx_tOm{t~dr&+0}JDzEt zXMVK%HKo3c6G7@mgWRHNBp6NWuck0MC-UH@s+a7?Y5#SS582d3AQyF2EL39X1xp{q z(i{tRy^P(>FwB%ZV2f_40{&cn3Uf-;iz>Py%RC zz(Y}|<{vLD9ecP7v`n0Mcy_C7hD%2#HF>hKpsCz%6f;4Tz^`CmaD`tLgI4KvOgzT} zi-AoPR(xfrf}b^oG zb=rq%CHLK%W)?l+tA)hjWo8CbLyb%*o(QL}4>m5Hh7d~`%<#M!t;3*odHvnRrg&@Z zXR#p`3*Le$3T$mW64+=0UQNsVz(xs8x%|#|+dXl~)@kFz2X>&%9Pyn-Ff8i9yheiv zpgXEq)2!F}TU?m%z?{jmYlMq*GK?c^fmWrxhWW1psn8|W!&nJgZl-lYV{5`Jlt(Xp zk73nQ&rFK)gY%R6x-*&O^PEt`H^Kr}-YfFlriL=m`W1&jYF~6uSRCF~q>N#N%-oMg z2PVU4VNwlbmOd2ahjStw{~ZVxms5LQ_q*yo&OVB1DcWKSA^)8$Cx_xa^MeeCyKC@| zBBf)ms&$g5>wwEk25c;WSH2*H=uo4c6@SEIR$}lJ!0>%nbO^H4m%K;zh>Di^QSlDwZu@Of693 zX#H+UT|-0rVN{Zp5{DuP<{`>y;c02j7O4}b8{=?-aYOid7oTy5%!nltLa~S4idp}Y zGcx5b+PjGysc6|}_dlkJ!>v}NccrxLwU;~KchD}T)T{*c>SF%r29^U~Jw1)LQEAoH z!*^|ukt`sA6um#g)TJy(M#cnr(7s%c$4`2QA@En`=X2Iy?pJY5izbwhC=HOM_6mCu zqvzCdF`e+K`v88EPsMKP`3#J%ph{ufNG@g8#|;r<4f|=3hyK0B6x>hNt(}S8fl2O7 zJnG8UUMzan(!qvgeYQB75?&dJn^%BzvX))78imkdaI5JGPm?(k>@&ZIagR1fPyF}? zWgDjOgqTnluM#6#6AVd{CE8-GYV>Mbs!P$1U1gq$hMOZC@jVHlxRbKIC(>gt)ONBA zo#ocY($lB9T=f*nPNfi~^&*5`n_FY}i&ha+qlM%z%sdMM7w1{vjVCSM{z2({+vx(3 zl*X;}XzVI&^|Q1JoF>f%E5lvAponq)K!nV zNI2Py%BDiS90DPKz;5+7E?AyWYnVuG#&oZmSI#>FgSKWpO|ZjD_xZ*#ii*&Dw(VKe z&B*~WwY!JNOdamZm!)DOPn?Y7ei5U*@9k$_N=chEnc8U7PF$Lxx86-3T|I*rrS%{$zrimu&DPRtKoA{kPSCICCb2sq z;(l3DNTu$2Q5gpGq-fvmp5v(&*|B{qQJyaBni<0a7*gFvp*-n+c2&A4hu{qG|C;Qx z;KPmIK5wZVSLr6Dp^>h!_#xb9Fj)8^B0|n|Y~G65dT7%P!SyZ^Xs)Xq*q5XgkBZX3 za2#>-6(qakh#UX%Owo$V78v-j>!H(5UF=c|M{egH{H|5{wf=}O=5+UL)4CVz$oTbk z4s7zvSEQoixB_ZbBe{7-{YLDZ_Ts=53XJCJ;C53hYWU^}Ra+Gkh^uZYoMX%jbf@a7 zNG&7n4bKKKX>mfw6%~DPQxXJU)>>rnd&EHPg^l_>u+Q#TU#l9}ieDK+I!i(avkibns^mFA98ntRpoSTx6F5hA)-BDCkOpbNwn zYAI-ii4xP7I)S}CckcOLN(QLA+m|3Pzvz8ARgOS> zS7PY#m6VO6ZLSb?@npolMIG7Z$v$QnUVP8WcrgvNwI2tr`HQS#G4f~85yd0njLDw{ zL3~*Qc`Yqu<8QBc2C8&eOx$hoUhP$t7Gifvn9OsVj|=7unR#1aQOBby@eunhPj{b< zC@Q~5lcyt(9TRxA(|VLN|8)`|#G5xwRor1`Z}Uxv*Dk+ z8uL9Y)s5}%aoop0d`twuHH+maycojR_Cn3E;%}=Sq7ML!GO0`z1z|gomV6_S6L9PkdrRRwY9qG>rtW(Ahkozjn~Iz|GGrC6A(BZVjfrp z-r&4H2H}=n3cmrrlFWhpL!7>s>6Q0)vilEwghE~lk4o(mu)y2ZaEl_0qW+pN*PE>kAqOwFkjh+B)+=X?L#Ztz*#Ipr$COb-;$nFNGwjObR%ir z27v-IL>^%s>9^+6pcf2Ks`sK!cT!i!T>Da;t{{|^*2o?MCdsuPdvkNpg+}v3?yRE1 zOg!|F-ogUj`5tMW_2-dI<$Y^LhAe?#eQD>Z zN(Gn`w6{j&eUT*6%jZja+?NvDvp+UHkAaXJdKee8a0@5X%Rtb)2uGCA3Ee(qiU^jp zf41Z0B(^B1A>GS=_U(0o03QcO^z*WU(n6xV&ot&dspDV9C!|!Wj~B+5F>?B15#Z*R zi3G(_PDTJ#pB*h5s!$N9pP}YLgNk@^)~+Q_ELe&!mVjP)%s_r(YiK`iW{Q>)gDy*+ zQNREYF(|hX+;8sHmvxd+hD5{e6^b-aaY%u<~=| z9g&;&e7X&gtr3FK`}F3xkYocBbU7GeBW_tGK@thX~&u^QhGXdGo0?er;PT-AKm(x=_OBuP{L#J|}2 zCX}{;79l6Aa&~3eRR#p2dz=V;qZhnC*)?iRKT>lmjhEv@V4w{GTS>S<9`iaDFrOs6 ziZyg_P|pD@j+X~gD^~V z@96qfvJ)0A9pE@up8bir_meb!$a^!}tLuH$hy5H4&gkgJkNey2Th;A^{7DU0k4;~R z%{=s0fgn?b%i(h-Rcrm&{68jUOWI@l5C>C~2Y!LT2>`WjZJfSturb+Y)*!w52QK=~ zMgsw=-}G;#{~NNB=`~x|kXJ(%72!MVp_R%``sT9L<70%Bn~>>sDDA5xlu)-EL;O!~ zYAXF6hXm#%a#J-GF~Gjv>Uwp5@k-#e0!G5Hmn0V!SAeUR>OzYQ&iGS9F>qF#WACJr7c9*2z*CsEIbo9$=jx@22EX zbJ#&(xW~1Nt}H;yZ3Xm*s^Bs{b||ToXD-HHnVp`b?3m?$va+8(>4V2cfY7e2NbJej zlY92pj=hU$dbPrPYTmy5{zTs}!*J4aR=+8GZ&)Oz0s|brjxKi<)FQZ79rT+`bpF%8 z!yD+qW1Qo4jpWu4_F;rlODaRX+M`UUj_RYff(UhFPH%=C8|6gWWv{dyLO>dgg*d*n zwXQ3`ZFtrBWi3m-d0O~tHfZo{YGE0NIY;igPuxYG1P7tv>g%_nE5o&Y0^w8EJj1-d(yb-@Q#A#q^C~Tmfa=yV! zKGoT!n+$bE%Oh{^(hC-m#nj8o%}v%q!Y#)}led$^)~q2`EyHI<5)7Ho2Zvs7BcX?* z(XItVd%GL}fSqY`!=uXsjivtWRRcL(zfrpMY`R{3d{)#Gu0;blJ*Yb!?YQhMmw?%3^EO2BZrgQU0PeQ|$`y`) z^q3=$uVmv#D?0#mq(`%!(EDFLDY{)+CjjcRGjc?eVpq@D52(xLU{G)`jyWQ!XXzL- z4Gi$JRt$KmB*P+UJ5C}yq&-)g!n7KbaRjnU$x&PYi~>p@}AxsKQQI689UA!y$ul? znor3$gf17kwglGaR8z4=UZd-W!f>^G%a=THtkQk7_^Spdtw#+V+c()8;{5ifE0kVc zHvunL)!|1t*Lr>X?oF+N6INoE!R~igIT~1x|9UcylqCJG17Y2mrvsmeJb&!fK)FeUy?UqN2k`C9#AN2pA;7}|8Nm{w9}e?!JFdXDdAQYDPwYP4&YiLMw^>@g z_nRP`gO!z8ZbPA;FA*xCz}f09oZ2jBJ~sYRhe!My9-&5-ktHwzepTKH(NM2@ce@xo z{zSA0q(AMj&$wn<-_%C#djtxYLg!&#PrX5AL))f zX@3{i?x?y?#l@ING>|6Cf%W&V1S3pH|NK?L%CgzDsnnwNh2X!pdESTjpPoy^(f&O> z9|ciP*mODT>ZYCjeHn>Lo6!Jo{aRVf2qz$X%ZdW0>g!i}AM251hpt@iKa={=+wv*e zNFnfNV#)o7kS>8xZW?^sNiF;|w8&8A*Yc4#R4*dxwjABI{%%>i>;he!bM|I4@z+_t zOZgpH?1(n^-Gnq}0q^|9>Q-6LgIUvv^eO(2itL};qnI-V69}*>KS%laaJf7M=>54! ztP>==qxN#B%HjbSpnPGz2U@NIrrh~m%4SW^hR%`L<>V{5p%R_U^N+SK({o70h0d@hZH44B!oQmEV<or0la5+##%-<*U;O3Os+QPOza;4@u6=6S*&T zX(_&?$Kn6gh3DAy*T>Q9p8O_P-B@j2&^ST=Rm9JQvm&7#F0sHf2l)9N?#6nS)8KYa zplvVUx=U_)zsX`oj%MfxEXEzGn+m;S#GU36d)P>XB@82LAY5y;;Bu>aB=uIn9`Z=OeD>a{=?0~MxEC(<^nLjab{4iLD(|2LDBI3 zXelSMsF2J5e%Jc6rlHc1#-E`r%bdWidb(<%V1Htp#=bPAY5GnazIKKn90dlzR^@7k z^eX*uydp;%#Ew!rBB@?i#EblD`SdxVTCs@@FRqa7B@XV#i#i1{N=8)!1IqFp*N%3s z*Weg|y&KewKKBV=C*mY%DmuaIuQTKrb^_(JH4!}*mcCfVS_rA}oD|M1QTj!4NX>>? zOG&vb2D4DVrDkH`>F)TiIk$@^p$itvb5FSpUk`2E?z-L-cuZ&<=W~^2agHtekG2Ei z`e#FSYsYmXgqKvd*-u!QN!#CUK^c;RvpxFswxamUQvfl$_Suj7m7zciILVsgEaX~$ zv~Gv%;xFrb?0XZ+K5Wi+ccU(yU5zm*dwkMIGbD^4;*6xfw+>DSguXyFL$G?d?SxA@@Z+HS%Kak0p+F2;cK zn)+!UpvPw)D1VN>)!{?luf3o~tH7mc(P;s<LSV9}KNg?1=3iE_H5ZuYZJ=cP$%D0Dp+M>D(}bS&{>WQUvK- zRTiKC2VQLJMScVl+B67J8pB|IFwlKV|K2@++# z{^JXJlNTV8ltw5C~=_UkN$~YrP3#5&$#~U+sxnq~QR6IM6YFOEzQnAq3Fm0C;nN%5m zCpqU-0cw|fVDI9bJ{({Fc4lW%)#Z^9S^=3lzZ(VWV-k+9@7YJriRU=+IVRyAWz+dB z2QH8$>ZkLNdNvpL2r9)g>4&b$I=x!;-Ac3Gh@#KtnCia34mTeUYJeP4SkC$v%X|IM zbOl98>KfGiN&__p__WyXaOzf)uf%+mc5>$Ti7Q^4)!jl-srr&w~a z6Hs(xK)L006Tx3bh^HeIS4;=LR*SD;j`GE31=Mu*P;Wrf4*sWr9oe3PB%*xy*Hnf`Y-+!msU_a4`r#n=pQ(h;- z#y)=?`()_JSo<*G_#`P(d&X@@0Wl!Cg4N85=2P(3au7R&@&MyJEN`RasiByRyfI!%Q+W67bxs7Wl>;Y~DVR+Z+y)~~G}kIQ#azry!q z;yZyeRPV3Qt`B~^n!yqZUhl#Ff?UZa0zL5G&Jz!naFBf_7A;B3T}VbD;rm|Cfa`wTPtlt} zA~#0H66&^-CRbD1#tsRpv%C_CtJs^h{+l9ch5VrkMJ>(=iz`0T@Y9cccwH-ex<okO_Xd>>E3G)Pw;1wWUEh#rwSHP!^J=>j zl6hR2&LYaEm>N=d_}yY=@ZD3c01!u-aXRohxrAr*lvW7r+3!I;BdiYuS2-<&2)%h< zO@$DOA5b&z8(gK6?U&3Fj^fEJ=COYV5UGG)(ZyGcSGK;!4QI{E_@SE*dFhy&G)nWD z!U<~aXqL+F63+cfFnH8_W0xwKOSed&GtPq_)K+d=t8v6os7KmQTQmP=Obi)uOPlO& zDboPG9HbVydH5x^L%f(g(5nmXIvmSC@T>s9i0W}@tMrImCAYa*Kxcf@*T*tuX^jTKGguLv!`{G+B4m#AoVOGOR8?8Ubx8NVg7Eck z2U&veIccL$=<2nrtEt_>h=K$=%iO~Se=YRPaBIA^f7phAP+z)CYkr{>Zp?wS?>2E= z4f;0K)dKgkZ$tqJPW`aBX|FlIemb^eL-TvS)?;B~+n+Cmb#sJB58apxb>)z7fAzC?T;@f!QaLwLW(Ja-A- zu6@`?NS#lTe2YLfqnfY(0F!18cu6`cBCPbBj8NBx)FSuE^&gop6b2HTf4ZTcBH3PDL@m?X$l zOkB55i2F|?KFWofnz8b{afTWp8gFi_P@(^d^gw<=t7748Zt_L@9B#!y2K$S$e*%s) zLM(Y_h*+DgR+)7o>4CF=p3Ndwq}H@VkMs0@LXo%6Nxv;WyC7NYH2z86?(hO1TTP#f zXFb?N;6}&#@3=!kc87+DhjiMc-blKPm`mp-q}(iv=ue|wO7)oAYiQ7$P|-~23nWW2 zJ0u%Lc$v@;m0@z*~4>&xPZ&*Yg6 z8c~-jbd4`z#-MqDp?60DuZ^@rrbyqh^pN8_DEPjdht@j{00TUkqX=6}{i2(vJ!tB! zT@_|ieM$KpGbx>aAR%U6G&)`qSFEmo6Mh z7S2f~f&))gqqg5!aU$;FGu-~>CJV+oelcZ^c0nG;RWXO%FaPB4k4U_h!BlXwAA6u} z`>%n0#h@fGc^NP#^nCx{|HZGivs9->t|;$IITLU57-N!u z_V_0R{l8;FE|~?Xp!Lt;|JU2n2tCzXD5*@SB7(>kx0Pc56M8-(Pop68d%WKJ=AXEf z>=(jq9~=9w$;@pb-Q)bP?NH3-#&|SFNqKP>nq`e>p2SxBT^Gp~XU6><85W8q!Y0&O zgQ@2_{F?l4Px?-m{h$K~KbQ{M`2h4kAD27rAu;afhxnUsO~8?I8EqbwOCBSkQa(qe z@vp9Tf*9e5-#Y&`0Gp`dSHZujD#_9~f^X&<9TseYPyY56pOc~lZGHNy@v*cEp{CeD z;&*+7=o`96-^g~vQfJS#Y0?s<8< zBg26fCc$6#p552NwnHmV29e|K7c_o$mR`-ojhLFN;~RjEqKV^SV@E7q4jp{|Xn7Nk zT;&KzNiBk5(#Ua8CX5DgC7&hkqeT<|WGA{PDrNd;t{d@>yND&G)n1%%O)V5qM_)7{_FY>NdlZ%_IVBd9A#v?YzEB^d z>-dvoT7|OXju>x4Jqn01Gshs6waZ!Ewj5kiTQy>Bu|g0(@DXRugYvJHHbz=2NUG&1 zP%c@0IZpNHIYsko6%IL$AB~5Nq9ezm09CB|nAc!V;oEyQf?`b}^GCVphu(&K!YaS* znFS5Mh6@6RXE%40Ydm3PVq(%C(REW-TFMlDSIb69%=r0Pr&@vV2Q2ozqHs|A%My131n?P^}o7Bx#JO8;*=!{)ExP&?F4ilku zeYVCm)xG|}wgeER+y5T^dtfGAKtz{z^FqyCn2#SnmTtsa&QVjM!YE_GijX;#9sOK( zW}GOloK3_3(k=AWo!(u(N5)1^YS}P{`3}T#ZGa>qWOJg}F{J^J!|-6rx__Vx^RKy1 zKpFkYW;Y{B*SSZX^gw#4xagy4a)w35r@LWgy<}&dW!?Q7*yM zDurs>kWq!+1?gpH9CM++&ECF1#RL3>Cb-`%JGZs*l#F1~(Fi!`hGT0Xm;6@k0eRcw z+yOJmn27p76p#ZS>})f%n^~fhQK-ZkNgRZaJ4|`7c`uW#em8u@?7kq|)?u31#z)T5 z1#B61(eo(ka00N_G^v5-d#=s8||PxEk=h&1&9w0-u8L_c%a4 z@9y(1Tk}laMSB_<9Kq-89n9VAFMfN58(jR(roU%XBW;F-B?l#%dxAo-O2Uz5;TNRb zKFo>Aq|@7eqq1TpU0c*4z<|H-CzE6E7T;FuyJBNg!5M;Jq$m>RBOlchpXy++m@; z!%>%f!zYw?sS+sNLn1`aI0$6MuJw436IhtmnUSr%A^vUTM7Cv_V`;J}sfE(_1JB`% znnPt8um)hC%ni03gTDuUfG5Q|_cMj>H{0UuY*6^S?U6%72NADY8N?!H8q0gbM#J=8 z?7m5@bFDHt*e>OxJI$mx%cJ+?)mfZx7t};DCTG?uUOrg6Mr;EET94wE%IWo+(o8s( zJ>`w8$8`w?kAfrpCk z>)py0+EyxOq;4RyGqUdyngEWD;dRB=^E+cQtwVOT=8C5SE8&d9{@B&Bil< z-`Fk&{D$yiUi`twCGE^D#NZC{C6Dv3Zb&G6Zs@8O8fkg9bcZ{one&>tY62ht{){!D z+>Jd_&ovw7_w+T#a%)F#SPq!A3e#9Uj}@(+zPxEu>Vw*y^j!NF?Tr0y?D8e~tsyy2 zciEq*qjm*(H(M|bPt>Lv*Vb>fRpVPzT9}DP%P+g~{WiR;zd5y~Ba8ou?jP-0cyN>_ zm;2JSj(91>_!cyJD|#>|STkuJR$qi`0&t)HASboc57R3SaW#>2T`g0%sbB7VqX=Db zzxd$6oH?{TCtBj+XStK+>YEU3+gcgxevq-CJ}3T-IZVmYxL}0hKunETW}jjStI(C@ zoB|UUcq+i3`Nzp+)zU%*eMgAk0g@_41&GR0%UsL!)zLAziwoTQiqq+LAXTGtAS~3<-J6d2x6OT`2fgOgaQK83#Pz+XIAV?6n;aLT zbLXQ>ml{xzbM4o-Ik}h6u7OgG(gbo9Jt6sMS#_sn8`Il+jVd=A%h%Dh{Xcl(l3={a z;F!o|3#aks^$C0&>r-wugfZscUhP}jOe!tQ`ZJ>*u_{cXf(ARDW#z;HRyGS=8XhM3dya=;8Of`KJ8CI@79+ z(80U38)F!rn9-#CTi*(6D!2zQaLXSH+0Og%x7ri!&bRe`@x2cr7B|A7N0mpvct zQM0vK8&`2F*=&3r%(M($XuWDZX?A)?~ADMv`F)hs?;O&H^?B0w)%gC`~RjG{SSBCW6XQI8DO`LBOR|2rwdK7(;OLc zXa;D6lpcPkjgvk?b0CKQ!f)-BEcJuCUNDFsJF;j|PuRFU>0ep@Bhd8OT$;;YNn57=*{ z^V#Yc%HDoH)Y%y-;b!;TAr$$(WL|>*_c4g-!=6hh(G_SkU=)mIx9xl!d^5-{Urgg> zefte+y;DbN{cyO#X4(wgQQGIE%~>0#_KvU=qme1W)>bxM(?8v-VBPc4gRnhO$Ch7h zD_0$?zk+I) zoR@x&hPpAQ_VjD+(#gRD@VS2q*6@6k5*gWLiRJ`(-m;E5=HRR{%J%gxwXEO{aH-Y;+OmXRaZ z`^7DU{XMK|<3{e^bj?!d{&KZB7pZ$M2U;~|Ao;@z4!4z@-XE#s>Q~V>>p8X@m|$!u zlWQVa88O?jN8OuYFxKKh6tmWPxk6?L86u->)0^5iy6#5{6$Of*%KWTH0Y`UQ)GR2@UYWrR+6?vAszvQ4u68p-A-dsy z1MY?+Zb=?|P3EWOKS+oCbKI!#b$RnMdG6%kSGE-;^)+*Uro`^tGk zss*5w9y33?9pJGst4Dog2a~BfG^2d=D$5JU+8A1iU^DQ8pHx{i_Vi6YH%S&g`p_VV z?P#~@yHQCXX{`CaSNxVF1QO?rc(Nn2`Bh>*jWOKfdj%-Hp_G=JxQwTiJjC))5#Fpnc(B|nUX?~BIMhGmco_RfN zfe!NdC802z)(@v8r%PYXHR`8_oc|f3yWrbFJ`m`fl{P06!GZGIHBI+<;VqFF3pC0S zUHlNuk?*iiw7MvB>CaMHxI?2EOnI?fi;s4KZx3hMHOa8>?tJwMQF3hWVWJ*2 zy$jBtX?RE&9{M^_NLX<)istvtP%j}1j6&b5K0XGg*(S%W)vKcGdw0bCNb_$F*=RIl z{Hv?Ygxdls`6$K=^rw3}0#0hlW}iUt4m;GxeJ9oQFzVGQO=3GPOv&P4-c#w1oxL?N zA8twfeB!f=#wwx?Ofw*RyjAIM`!~GkqnJY1ywY#mKj*1kcoJZOO(c6pz`Pp@r3%; zaTK)n7#X$1ROnU76z7L-qGHOD;*)G@&6d1|EAW&|!6uv1KWk>3dFtT%bC1EhjU1wcoz?(;rL`1?##$fu z(fKiP3TnJGNswd)@e+G6hAE!7BSu|S1W)d#sv;4kHmduO7m=yBrb08|Dza3UhnW$b z_-A#H-nxC8gtx&|pd!52?eQJT+Op!rF@1*XH_l&>_h-UEKm0>u{x{;J^PQcYt)KYe{l#Gj z>D)In6Sdj6o_0&jueTb ze4cndCKYuTr$?BBqr~hMhLrCkTpP0nB4`+GLO#NkIgPsl1u!3eMroU0*fo%`t8zD74yX{BuUr7Zo@+z%V!YT}UHxTHSejOeDK5F? zq3Yp7L{;H>~L1%eIyVYKMfVMNrpuK8Z0*?r>kTXrhlUw7Z5 zm>V|O{LT}g+_Z1M$&WUP>c7D(>1Q97e6XU^rQF`8Jo+aUw29@Pxr2DhKh`}o zV|mK2L#*3ZwDFoEJOLy%`}u~pMDb((-6(vMg~EJg?gsTiese}XFH>Cq5{NrHht__M z7@VZ1kvJ~q$^0`VMR>GSG~E`<@*AvYHzx zUn`C!NygiKko>~s>Sy})Tdu1SiQBtJ{igoyA32i zg&wq1n-E+*JD7=YnpON>Em@m3GBnpNO7#T87&(!(GmQAh?r$?ucLSU1g0@v>y+YEA zxvC(p8irX6WS&X=%uUaHrJMOLbVtUkd9?7|^l#b@C?gJ7uWht(m`~5%{p>_9DXKeK zS|O0qsF^s($lWc`f36AeOK|LvmBfNhfo6j`HKrkB&on6UTz*19tZ#!rgcf@D z%+EkX^qp;?^{cDGw4!*)pCfNDA>$rYu~I+u^gI*GWfiF{sEvf|)dZ1c)_gm`Y3Yrs z6jLnYsPpE~{I?1h7RwKXz7&@mT*iP!o^ILI44ZF>PX4f3Anv&ItoVrz)rt(q&jK(9 z8RPvs_jEn#^_r{dSaruS6-VQ6Dr4t$QcSKE^IFrt5!G!l6ciE&xwUwQjK9VAu0d)ZGm^ydllK zwD+p0DzkHuI2&}yeWl5;dwnlr!bc^i(6x)bk~vvs*gReR=hfenQe~EVsePL65m*tr zi<<4VDtHf#+&l5Fd$c%Ua>7}fuE?<>H8VFQZA#E-v&;+Kdo@0yL4fQTzBW?i4OSdO zo|Kic%<-5z%P zWwK!Xz?d4GaX>QML#OH9cN+8*q*>~jBKe;dJp@{GMmXYCa%hwgs!gMFw|W;ow|vJ- z#4HIo=SqrRBWKUd0H@TYTrq%sSamU`6yETNbtl3h z?>{JmAK6B3_W1}qR8}y%yt69reo>E{W%K>K-XvG01y0Z<4Ee0v;!@B2->Tcv}?uuTi^NR)_<#Vuvvz!wS_3s#+D3Im4P-9 z_p~1wNq}$Mz2DPEmNwKii(Kh(ax%e+M43r5+c3S=bxie3WK7|_5nUiG z0F0Nb+F5M5ka1i#$VNo8`aN)7`7Bb7u=pqDwKM)NsXuu-52kI3qO$ZD-QhXio z+20%2=%!A{;bau}rCQLdLn1`=#XuCF_n%-)=O4p^WJehdKNpQ1Qw%*1ufbr8${v) z@)%N{qpX?Zk_%g+PF%EQrB}BRGx@H3z=9ObPh=oF^=|4}HvlEJ4B_M)3ihHmwHUP| z(ky`mXevoXMiMmKn|`7EM*VK!(sbrDLP0Rx@aLuW);Vq3vDznnd5V4bfrL95n3t<7 zs49R_5-d%O1hFaIl%90D*7{YohPga9>VYxfMUh2Qr36isnW*tjar&Jn=_SFf$Kzh3 zrHA4Zxu+Ze9GJzuqz!-&{k|IJs06-+{-u~_jDr$+%mA)Sq9;Q?j+##wt3vv$T>&C8 zB{z6)RXrPNa7_GDE>mrOKm5?utHI;ZJ_3*5w-x`IxfxSsFYMqjLOUkI-pK5S-|)!D zuAhX0GuNkVWv2)UM=ompa)EqHBBW;vSzf_;Tara(yt;5Iq0Q}Tx{wM_8drYvL~l-E zN&1aJ-B>~;V5~vYrsNjtPe=_Le@)yQ&=Bb^qiWyrT zEig|F2YCce!dInGjG9ubkBt^mHv+Z3E(^H!s>m+Jk~pLZ858NUQJB9Nl!kn#rL>vK zur1cn_csut5Q@I3snZa7r_(J@ z>Uy*-_^9IRs+7~O&!N_Z;PhTcgOz5m%v}R~Me6BVuymT_S}otS)JT(^T4>?zGD>bq z@f__*Ep+;LV?@oWtXi!xTK4)1hb;w;9YZbaWL_8)K!w6mIfRU=rE}lM=1wD|kyF%3 zKCnm=DXAB}r8b<^%ndjTENZFgk=xE1<#3k_>|?n!m5^5IXw{GErV(^|;NW9gW}FoH zAkHia-MsnW!pHKZI*i7zsqYhldk>UBvn%;A810Xd$-K!66o7_2JQ!G~EVZ-3>^8Dm zuO2iN$}!8WhaQM2@^24>UvbP}N0%|NR5Wb`ZmqGM@-ddpcGh4!e#H6q?DN5UW-ZLY z1*?LDG)|kND1k&0hxI_^^iiB?Oz{;X9XxNtx}naU)G`}gJ`*gdtAn*)LXYI}VT#je z^kn0Dl0}Qjkjt_z-IddyP0~tTNz!9UJ>K;?L#ef0$rp%HqBuxHAZXmcNwaldt&1!0 zJg}Hg38xMr_Q7h_eQ#p6R_Hxo*GXo*pLAWTli$F-wzX@?=Y847V%t#a|8(M(4AXm_ghG?An_o*`S{)Se-`r2SLfU}F%H zSJRhl&Ymx4|38vi9@IO?6pWdY*6)Rv*|`qRHJGSs+5hTtwtD*@w~7I37CqR zS8Kj-gT}s$RD4pr$}_}+T`*#M|^(#w8A%=XL5OD*xEc3R)6TWc=jvqI+FUMT+ z=*}*#Ns6a}kY5drlYQCC04Rph&7g)29&TEf>}{U3Ncd_!$8~R24xluNE+XUg*3)D& zkEU>e4UBpjC0Pbrb>aJ{K+v?I56>x`&(DfZ4ld7hp?uRWG&pvOLgE~j_QE2=)ZKoW z-d~Z}RO^)r&L;um_emrCLHRQ5XjM5%N{Kt0D-AXz=PwC+yaLkf$SaZNJ#XceX(bO$ zV+v0guH>J~s<(@MzMucy!TP`@M%-W8=KF%{fs3B&>FoOB{k41;lF!5grQ$I-df~0e zqA}+T`Oyx?!9u5ph4`p_A@wK6GSfKM1P~7*|6S{b>j7AHdykf#9r>>6=n_z|mIf*# z3uK5v=v>;uJS<~nK_5QX7HD;;X2OgvZIf z{1_z%1P`Fmws}+X-~{59YMJqt3YlkI{X=1nQ!EGR`5RDwe~bLmfId3eItxRtQqe4| z^u9MX;-#^wT^0hz5L1lxL|i5`cdHe)q%TVNXzNQ`h@zfVcUEUae&?Pw?$~eWTM(4i z?-wp?kWddDiWNw;ZY-3dB}xeb-0=_|eC7nM0eR){@%wzbyglx(0apxkQzpnant~pO zkU#=XJa6hGb!Lbs>eliu)`{c~3k|u24S6}*VtQ-ojFnm5`L~yF<_0Lq_?YGU2{;HT z3GoP~_btb|wFil=PMi7mN=>ah6-}2kLPRSr_IoNKD9T>Hu2NrI410}Hss@ac4z#Z3 zH5kzo$b81BdHe9Ss}c!_+H4fO1t;YJUm{m&&-+FDfsnit_(1!>QRU;lt&Z6)OF816 zl*6m;d-cN{XQPL5mPk^Vw>!^xYElpde+sqKgEC4np=GL*J#T70b>s=!zM2mXZ2>$X z+SToc;zkjrMz!3xL>=m6)?&zo327Rx@B>dJH$_7yBjMJJ z?J|uw`zMXq5b1@LpPAY&2#`5&0!1hf16{5m_!l$Ek@m{qFGTP8; z8peMherz0JYF?$uu>_5nvekuEZD5tA?+3<~x)pTBu2(H!m7QnJ&u&pb-1Ar#reZ-a zh<0f@wJ~^sfR%~qkS|j z#*4LA_4IGKTqup*Y6!?jS)!slPM@mOta}q~qY2t_1*I?aOCY8cf9Mgkv0!j*?^4-k9n#Y-n$$W5@`lQ&K<5@Fp>PG-%#i_6>x+ zW4ezgrtSP{nOslQDzAT3+|yx{^@=cRa=GcrLsdj@nyy5pu5VfDT{i76{5u%mJ!c2n zutob})&U9bxG!azycsnGJF)Y&$~Y&6mHQ7TUM*;QC7TUX6X;h)sS{H^*!U@KgdXeR z4VVd`+jN6K6{T9mM$P6U_~RzIG&?Y=5X(d++;MnNWLe4`Vg{QMuQ*nYet*+!fjfZs zCf4DJYQGuIf$s)Z;%?x;(NF*TK!}}^JC{PgbktaUH}JKJ*%$hD+D{F0gtX!pYCJPU8w^B~1*e4}Qq{iDk5W`8c(wW}oe*%ukLlm*Gz}gepd5 z>^r}1WzJfcljA8k5B%3a|f@CjCxyNX_CoWnfN&xPlvD7afS+w z56jmKTZC&idC>`L7A82~OHfWbhNd;rYde2hE&X-hDN;-qyOxwvm(S zR5;!xVe^gnZP|Vr*b;EFOGssVw{*?_Dm&~|+y_pgYsfD{u4ypEgQCi8n~+2T{AUAx zuUW}F!$Z?Bb3RUsiBq@%#6)Dr|L>{^9SGfa!}Y*FHQm7D9kNSxDicfJYj1ZrnJ|B+ z+^ZppxYg@g-Q$eiaQNO0_{k6BA%MG{eCDMF5h=q^MfK)GZui7HEwm+49l-~M7rR^u z2Xo0)>kT66fj>VS#Lkr4;q*|Oa`DF1r37}@2i6sw8AdOeDo)4Qmq&-MRf^WRJboYl zB9Ph869-BAd57V1$&5c^Ts*W7z?o`>2x^4B6URW$-ycRF(x7X81 zpP6uq7*{#j?qJJ<>`uRyMfo1>3~FpG8_dS#1~`8;WE-q&wg}+JTtDeDVi8_l$&E@h zMpM|KwoSOGdd<8>AJ7YxXP;rZ7Td1aEuPf}gTCNl*C}c62in_MDG#Ma^JciWa3*Kc zsc~c@>S8|xUs4!v;E`l+c^rz(q&T@UXB}x&oC!!IBf>Lh;PoFA=-XIVob^1*M-lX; z)YOtG3YTm=O8+Jic#`vPTn)gz3xh^E&+D>hqLp8~*Bw;S!FHb<6R_VV$s=W>M!Qz6 z2HBGO^YQM9shRc0Cu8CkrT7j%0E!+CU>@90Xljy~svX?u9Mdizv(9s~P-u0IzYYju zEL0cUpNIo4B>s1nEFtQE#q7OuSco{`6KuJPd62Jko1}BJZNcz2oOREHI>0qSb@Rlw zyv9QwDdFx|2e-xv0PO6s(mZasL3Y6z_!1I*EEwLUWEk4j1_9`j@4?S$R)GxpZ%f4O z8m`-tXW$5U$&Ug0;K)x8AkH^g=*&7Ns& zY1*MeEDDfRIT2YpZh0fOc-2spX^Itx*=n>mYe-3e=)bX}z zUQLZ|q|~QW&kOQyqPO~48JI8XHH-GR3;yx6!e3a`K?-=1?v=;7_9=oG%MUc`sD_V zpb*f$VJh@Y%6;X!(BhItJk{W$)D>cA?@aY~O2LpsF(6y6YdI3nT==_!!G{{B4Wnm; zjomWI*zq}Cbb1}D8=95I^bX~AsXyqaTgK4#=O{k#)mz$$oCQ0YAX$Op)u9oXhK zYk04Bt*{*s-&g@n?pV1e7c7c|HPT-=c&{;h8viL<*rW5br%F#;1tGk7_bn@9e*1EwG)TuUd?V@`B4Lo%puJ>n|hD|CfeZ{Y%am^dY%7>xWj*Oe7;g z#pjvLq);(;V^1<$8oktBqkpalN5i)+#8O7WP#D)c#ByJ0=TMlsvC*9{zny5Ns>#FT z<#30GDL+#-)%MQRHu;4EJnR&Bbi8Yr52`?eK3T*z@+_%t*+ZcoR-H717<~T@MP_N7 zEuzELld#T0kJq^{3Q5po4Zb8vc{xt+j!B*@%>>1c6$M|+++6ZjcbK#UAgpGhZVB-( zcuoKot|H#+D=fDM%{cp)Bjc@He^or~xq&F@Jk)adET2^!exO|T&L+sopu;N< zx-qVyw}xZZF-jAnVYr1wpxKR zkEt%6zJ53>b%ZmxvF#nHvf}-HmV+HsVdC`*Kc^vThG0!gFc6P|K}%X@!?y>~*zQ+6 z0t6&KeVN1QXl$eYxHo{Y6#=m-_nptb1eGUrqyAUHsKA z2Ze{n9tO^;=ljdAc&!E^84em9(qa%L+$rYfs0B-kBP?!!xDN}UQsnr7^ z>m{Ecu#bB>t1_0ju%wUPwYX=q59)3%T>VnYJt7m`0_-bnS3h+xy4IVhs%CmE z%k#|4VXKOJs~WmC6iju1r>rJ$h?v=Pz4mN%kLmS{GA~O@yEm5qT-%%e61Lt%P~SST zFcjB?AOyE{ycKzs|8keS0Me#pv)Ay-mP~YvwX}(|l=JIUL1)r9rpw}jDms-2zZbxm zOZ;(HT)sSIM&Z6XjPsuN536D7Uj7NV_i$?@8e+f=~#;)L>7a z2LyV+K$$;q5YhlxWD?^KJpSc&%emV<$LTn-GU$sXDsAaCI-iN@4aK#_iqQ#&J$MSW zmmDVUY$3Fbg`~KIO-PB4XS4^Vu@V)Yk2rU^ijhF5b$Mw-TyfPAVPw(ue{@b9mKZZZgKTXvp?>Eb-R@jT+_Tx>|KrDf_KGF_$+Bx&4QY|$JA4;7~lJhgysc>($J@j+(Qau5i|pJc2~#xl@rv>gO=@ivU{6jS;T9P7Ni-BRyfxv;nmp?;Sa&xNwx{NK zFxs>uj`2?s@~$<2`wa#ysIz>2;*S@b@U4irA=98etk?z>(C64%mdg}Fh%`lsuwEiZ z6?|FWD@0{Y2flU{D|rO!dm^|lwfytavcN5nyy?#ahme!;g-j||fFTMon^6s{+vVODA;5%JXjG<~fM3BYH&|!_$GKf=s z9cSLuv8Ynn7oSh>R-D-xe4pLU@jkeiA6jfcZScO>_c#G|*zo9Tq^zaCD6a>{tWc6> zP>1pEI8b8G*X>9?8Ech65gPiI3zRBcd(vB)U*G+QsT4WXS+o&yo07H1xl9tI#W zGgvW+-)z94c{B~>%+JdJf7TW-s4-N?jrvDl9UE6&u9 zN6!0H!cP)=9e4)^F9|Sayw>xsT1y?Xds;jjo}q6Cl^eIBDT6uRtIyEOUb2sW zZfI|R^2=fwu2;(O>m^qIY$Vp5Ml<9o3_h%iEgUzfanv0<9<@W{oKjAEAQz`g^c2Lg z@M)_}n;T`fZfbZD8V^HhFN_6h&N%DAlZ#RV?EBASDbgHw9ZU;U;UK*^FzJm5SRZhO zzQ!B>miveeL})VNQ0L#?`R+mDcFhWTOCU_N%g58HLi5%$K!nSZ9C0=T%fJB~V5{!S zju^T_yBScS(T#&o?fALrII2}8fAG^xlC!>jv1O+%HV@4Ixj1B5bQ*0CmFg!~peSDA zw&bcGoLDsa&Jt2x%P;r=&wTFqlX6pITo->Z)UPwI_zvQ`p}RE7&bfHmMcrbx#3D0m zSiQ@R>tN^gSjV_--Jz0t)L2TEkbUFZ#VXlCTi3KtX7KyzLgY1T)7W~M+NN@LMHyd8 zDYtNgp*W*3|Kkso3~sX2{n!(x(ROR}ag4ujN#3;Akd**$f{)dgZb;mb&$ZhX;x2s% z!1wVc&GRq1s2_KGy!usL1`N(|Oz>z91lJ;{6v><6`WznH^_P1c)nuXK>B&9Zh2&II zTcxFDjq*(8JxTq68DG#~_lShCmE+ILGi#39Lm_42x2t(X1MLCMnWS&vL|l2tg!BaS za;&`&A)p-0Z;Y2a&u$O`P4X_xKT@aBz8e~Wk4!qu_FnJf^1`ccVYtbs5^LOQ zrwHw)&|IKE>Vx&e3u>u9ND|HHJ-t-jPSRlUt3u;U>b)mR_u%&ZZ$Gw7Tt}g5J{B}) z+s=*NOs;G5(=5f0qltkuflmQNu)a(wU&(Fn3!MpZSJtUXNk6L^Yju`S4K;n7Z?@rU zrJ~djKrqEssA?HXWR27m09EhCZn9>aGf1Y-Nf`cqWuXV~6bj*McQ2=x82V>2W@k;` zKEY^QDZH(IMVi{zw9o`0GwbFikp#F-RxjV;aZ0p@h0kwXI2SakQGSu27R=!8J0R zpU!?`nf8|azJd5a;6?oh{7L;t*LvF%AWBo2>Z4yc8CSsZ6pKUL2pBt9)^to%Y9pWT zs)b>>%ZWnncIO)7ShSOhc=aHKG4shMhewD_XVii{P6()4w92PsDf=metV#cF=i}Xa zMFknC+*hy5m+Hd=uF?k@jawJJo_16CdU5Q+1=}YYQ%aWpA<~}rZm2lxRNB>4RlA=E zPI>#uRj1hd0hCcLIhhq*!G!0foD9yGgm zTHSz!VFdG8w+hw*J_4uu9v)*j_0T^Md>`jFeX9<~+oZ85&Wno|kv(U@6FWss@E(eP zn6aDUla@NsIWsJ3!%C-_nwn#@<~Al-5xyjfa{I}T8_uwLq94p~lZ&7Kn!bCzxxU#9 ziuTfCZEe|Ja(8)plyH2igZ*OTetjI-h5gG5@+R>k3M#+-s8euGp;M6Vk8veW z0boPks%IMm_L0Bs9r8i;ETzq0(%`qt!GL)r^bZ@P5dr*^FQ}txzX+JS>3^r=$?Kfe z0L`NZ_@h6s|808c|80%IBe(s~MlVfW#(@+PqBo8|{<8f12XlP(ACvhThM)Rm!)cOZ zG6nq*xVZyU5l{?c{qethUNQm3bXn%Y$gLs5)bro&cHy@`UwfSXwZF)m7c{?Ictd{E zsyE~p>K3%3ej9Cwh=jxb^R|EICl2Zh?xzi`&#IN1*R|79n(%C&uWZ^6H5c|CP^c22 zaql7;r2NYOZ>J4)TwbF;R@9H*s%+O-ldeuf*BupmNIwDK&A;iZ(D ze}Bl>f!F51<>0#pa5IHVEu=)#>kc0o_y+aQ!9a<3E(pYnU5Zlc>^mhVR|9jqF54N+ zEEu|i#giL;2Da__oDmx#)@uys`Tnk)Vkd0;kT9vBmS@sh=4zkavlU7$dTg-cb;f1b zH`Ebm8Dw-$yj@5De&W|yDr=XR7u^6#a*oc(+`I6eiAUVdH6T5(76s>v4vQpbPSU59 z2$fd@Qu%ClFjPB5=jdi9jGFT`a7I-L!%V<>8L9Iuj}bH3%EuM?xc1pADAmgFI(SKq z8OJkfH+K4@TtJz+XWmQ77Iyl+3J_*f9Bi#$1H{^9rMnop=9SfMno1c1C4neKo{|wK z_1QW2;*3nvg);DpWVtp)knsH6T#fB(d#^`3%suI8o8yPgtuBMo*_(GiN13mMe-t<~ zA=aSll<#!~WZs5L-AIlFa)mDv`%1qE?+ zH(`44vy@ZA=p8xYwcgO_bmhddE1n~TTC=`qZWQ)ZBt>Kx!>=&dLW_37_+(CJ&eVNFYnD(D?WVxPcqN zMdxp?CMKEsh3n$s>)lSQFc&C3k@bw1cq;Uw$?Z!HQz#ju8%ye_>Uq1bH@UfQaP!hp zR>$71e;9s+*# z?KQIW>fkaGLl@rwWjInlC8<`#EH%u?MG0EwVB%GxQdQA}Q)-$>YhCUK&q_dut;t z_#QVMK{I>^;jyuxhejulT)WxVTzW=?NUCUC1*3`4Lwrd$x#Mz#xD&{8FS!JnbMqx> z^KEP9y$De^Heg+H6M4;R4s?Yjta+#H<_&1Xd(3ZdF6q^Snw0I#i3$^tjmu{%DOFB% z5ddm*J50(=R_{?Is6ZGc0F+liH%|URO@^vy)l}>Kg48Gc(?$%PsIUwfxeHGqNjf!C zPG2QseyZ*nO2ZI;fu9_f)28DlhbH2j#9T~F-*-q{qm^8ir*^1%E}^fLr0DMyU;i+5 zb@N5i0RbJh;=kYr`}Dbc`*y=ftFV=^nch~F}miV>cjK;QU2cx&H z*yI$vwHdRXm{@-xP!L+Vr?|JP965oRnB|1eWDV{})cSD}&{uciyAgO`k7JpVHBK20 zh;+G9t?I_ImL=sqAjzhi!QnL5B`HaLcy?`yO?^b#=Cy&X`fDn!#E&~`{Jn$7rkSHq zzdVJg6CslHvo&95nPwu1Ik_flJr@jEh@T(lN*y2n5$`clp} zf+MailUR3(S-vg3a^LjY`a{o{P z?65>PO!0~knX_Rrv?KS58{e^sgGGh3>F{i6z+U1V=zBEHx&@-Yn`5lMf0z;q>ME@S z#V*SElq1LXI!V84R5X90wQL6A*SV8ot8%!q?UHXn{I!RWR(PTN{?Q&SsOEg9lb6Xq znQ`RqkU~(4{`fRzs=82BwR4)f@OuN`#B)GU_l}J(=RZ5%VI8aXLgp08c0-Kso3N=3 zK}wvEsYg_00tq~}$AA%OrFQQl873Ed)<7j2PuQ|z8IwEgvAQuQ`;r@b@}UKJt#}1A zV`rV;jJM1C-Fl+SLVap^qpIp-)0L(xg$o{1z%2Y)&LLRWlO+^o%w{56kN5>D!H<$6 zP^D$FuqB97JAnMc9E)P^ZbTU1c17PK3gL1c4N>tMaVR?h8HJ+Ef=LUQ<0LT)r7$%a z$@x?b5f7Y2JZrIY?v6X@(N4ivBGCy7$}z3wR(b_5C>evaHvjlR?US9&Awt|*)L7xS zBghbeIV&Ba=ekTa5%{@D?u&*%UbgEiW`fO{tP3lCR*g4T>{iQBYv^K*Rr+yd?QTvz z<^^%Dozz=-aavfGt}nX>TZ4x%H_XY9g{G{bHX!GobPmt`s^Evudzyg5U#DU9)Wncm zCxqm?DTsf&>YmD?p`uN6(=RG@~AQxYcIv zX9!CToqfum;1hRSU|qdVj?`{>PSr-X(u8X=*pXDp9&v+XbVow-;6P%vb_sNFoU=b4 zz!Bw8Rb@&4rXafVxnYn=nd|NeJ2&gV&aS)5YUmI`^Tk?~9di@NwG=nly|`p@D%a&L zKBAE$r@2D%sLag9F%YPmzNI-{@#u%xH}OCr*S+ijS(h9fY`Weq&op56C9S)I8CUo^ zIwboeSkcxXr{QfD?J~JbftYT*4WZQngOpa^r zZRs9_xMM+1n^IGbgSW2a?glIIzRkRcVMh*cfcTo#Gu*e3ulS%Id#xGWzLH1lANnlF zGlrSU`5t7D$uYYaOXv=7upJZ}io0-?0*(WCqropJT7JC@yuE~l-Ydok6%pf(2(spR z!R#{|c3a0Ga^?oloNLP$EahYFp?Vb5wle-X=h2yuSR~_$NF2Eu!z>egy$*avV~L;1}K@90B)zBcH;w z)vJsEg-XXq)7V8Sw%ZJ{d(}3S5S8i~k80_e)~<52K|+(POjvbfaU$)w+Q&6f>Nc_s z6~2_x;^-0ee9y%N?eBc`_c|GP3nK~}GwxidpmKTSCvu#a^Od1fJ<6k9io$Qolc0$U zSP{(6DgRnA-z}yML}h9mwdZ;~|J~D0UKoh|&g_Vyz8p~CRUS|$<8*rl1xp8!<8&4> z4NUIE&mc4k4jz2&4VSY)zx#suwGHYo5;#(18uFVtioQ?Sd#cP$DC@x~%kuiC`~QF? zB7v}a>O{@&f!t}W5+cxMxkN^%@9{*>l6ayToR=xALB@KBa`>J|6#R7U<~B_fagb9O zVC#NQ5;Xnk8z^5|=|1{)@8S32r-X|HSxlUR&fLx-)~JPZHA{H3N&{z#?ZntOUU!f^ z@xdOi(OLyALU1@x?j0!EeCO@jGA#&JWGvkdj7zsocIniExd7!UtDc<(Gpo#FysRxczh>$$w^R=L#9Zs$>vma2 zm^T6ruob^o8M5XknkxoICq`^08dR0CQrKg=!x_61*22K4tyyo1sR|$=XiO0&G{Ip1 z%N`V+$Pc)-8cP)35f2Q##)uE!ce)#ri52x9Nu&fSAQg)DOPyKCB9T|8P$XsiiLq{R z6)Svcsk#*wPC7#KN?MKAYz4)CjJ=wRb={WIzs#ghi?xLIen9{}P2lxLy{G*7=b$4&BZYVDVFm{|((M!tRML&EQ ze29BI)5E8Yj98fnhN$!yn?XXs-gXZ7ArJGshscQKPu4ryI9qU0_#T4}RNz;GQkZqK zIE&cZO{rwjqI)?Jit~zug1`g+m!avYhkK`GnBCM2`c|c8&nuj&_7%e1TaMNGS5r^A zblOUi&*Xad@1IcW*8nHuosxH!W2Z~4E|#)yYJwFS{Kz;F%;?a<3~pqt?nm$Q&&37x z)3?%iUMO=MjxxAyzI!TBYWXX5$lF>DNTM7qi&Ht6Z}#-~MO+Y}QUXHjC#Y6b<&4zY zT@7`|(@cERD{*P|4?(;V_&?)|7r6EH%|o>iaeoGxT@&XlUH)FLylTz$tflLGCjHq~ zdfH4^x#q3zq^r4yx)&B$%(Q1)a*E|?_TlX}^Asn>+!lZYa@z@y{=@~A-b;@gG<;cj z9J148=Jg!-IY11Tx(V)Nzf;5ap)lW$eL*I0vjEs!qxRY7p-WjDK%IK9AaIO_1$JmD z!-U1uJ{$;Y2N9~LV8PMjG$$CG#udpJD&42IM zP`vc;o8mb$FKEEx`9eg^u)fooNigg8p31or1lxcNM1(#_|0 zMFM5tEPeP%|Cqhz-TJ*Q%f79RX1jEJ&T8Pkm*tD*XkRUVr6hTEV)Fe6gsE>UUY!3l zWsdgdHyQZNae??$*;kub=obQFhKokL@YvM5XwlgE|bemL_a) zyQXtnrRZEk$E)D=4htN9%~cNCnp1jZcDt>4?i$&Me_JE0jz#jl(!W{!^wLlHJt}+B zx9pEEdC^wjr!82%FXQh*Vcqk&?n1M!9m+Ei=Y^ZRQtD=$>ZJRch4v5l=JtuNyruSU z*27utdeea0hx8xM-(k7(fY8@1$y;^2KgCF%pL%lB!Kd@;E|#CR^zZHEsAZm=ezJ11 z>$2US&sw>g-8T(cwr(YNsqgFw^5Q4oJbu=qf8P2pXj8`R*T#ESKJ~NAza^F4H?0#E z$5#E~WBZ)?r^J8h zcS+SxuirUVW|hXS_kvE6U+m@Vq5>aozr_!%lDtHm#$AX&0cZ)qs8l! z)848%T>E!%^?V`A^pYMkML*TgmVaw%`>ji+)!bCM{klBUlpD6OFJqoniO^Yw)!Wqh zO3QQZt4z8dsq`w;TIBSXkH_7&$UDrke6Dpsmc0tRCiaY zL$Fr~vxENIpVsHC;+@mi@@K10^xUOq-tdht`1iIu1)x)T!QkvQ$>3)vEI%#j=`UWq z;rX)Osmq_lNZJ~e)kjxb&IaC`W`2}+W?+4~NWAjT(DGAH+JoMoUy!SsHA(aD*Vh;P z*`9kxoPTK0xomp^+`HSh2$h}^zCOe5pnB{l@%z0e-^gu!Jl`trn0?{qFTIzg6t>9l z&aD6FaA;N761@u__di{~`MhZ^@VGOtwKJ{mth-Tm%dh3GLtfOxJ6kQkzKZ?sR@A8a z_{ox$Q_n^0?y6b!^_KPB+g?X}`Zx8$#~>MInexiWSC%%Pv3uud`TxnTxQ%)Jx5DFN zRTf*R@rjmN-paSwP&sXmyTu&A#(mpQoYvQ$_)(~CU5Uj1D}|RfHn;68P26t{+!poe z*H?*cH(u|FKKD`Q{gcVZJAo%C8edMID|{{e2B>wnOH2vNzDtIk8An#h&p4hcUXvwv z(T1n)kHP013;tI>Go0u9dcJu-D=YI^j#`4CGaufq?i#Dg_rXr*dA|qP(gTAnDZrEH6WI@+%Z3U#bgO^*&-nbUT-36zopr01lX)#sB~S diff --git a/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md b/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md index 14c704a1..d5b96215 100644 --- a/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md +++ b/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md @@ -1,7 +1,7 @@ --- layout: post title: Step by Step Installation | Extension | Syncfusion -description: Step by Step Installation procedure to install Syncfusion Web Sample Creator +description: Step by Step installation procedure to easily install the Syncfusion Web Sample Creator on your system. platform: extension control: Syncfusion Extensions documentation: ug diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/download-and-installation.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/download-and-installation.md index be3d8b23..bdbc516c 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/download-and-installation.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio-Code/download-and-installation.md @@ -17,7 +17,7 @@ To install the Syncfusion® ASP.NET Core Visual Studio Code extension and the cr * [Visual Studio Code 1.29.0 or later](https://code.visualstudio.com/download) * [Visual Studio 2019 16.3 Preview 2](https://visualstudio.microsoft.com/vs/) or later -* [.NET Core 3.1](https://dotnet.microsoft.com/download/dotnet-core/3.1) or later +* [.NET Core 3.1](https://dotnet.microsoft.com/en-us/download/dotnet/3.1) or later * [C# Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp) * [Node.js](https://nodejs.org/en/download/) diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/download-and-installation.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/download-and-installation.md index 6a67457e..efd76ca6 100644 --- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/download-and-installation.md +++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/download-and-installation.md @@ -18,7 +18,7 @@ The following software prerequisites must be installed to install the Syncfusion * [Visual Studio 2019 or later](https://visualstudio.microsoft.com/downloads). -* [.NET Core 3.0 or later](https://dotnet.microsoft.com/download/dotnet-core). +* [.NET Core 3.0 or later](https://dotnet.microsoft.com/en-us/download/dotnet). ## Install through the Visual Studio Manage Extensions From 7a09466fc42169714693102cb64900417ffeb34a Mon Sep 17 00:00:00 2001 From: Kesavaraman Date: Thu, 23 Jan 2025 10:55:52 +0530 Subject: [PATCH 7/7] CI issue solved --- Extension/ASPNET-MVC-Extension/Command-Line-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md index 06a6e00f..0d0308bd 100644 --- a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md +++ b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md @@ -1,7 +1,7 @@ --- layout: post title: Command Line installation | Extension | Syncfusion -description: To install the Syncfusion Web Sample Creator via command line, follow these simple steps for setup. +description: To install the Syncfusion Web Sample Creator using the command line, simply follow the detailed steps provided for a smooth setup process. platform: extension control: Syncfusion Extensions documentation: ug