diff --git a/_config.yml b/_config.yml index fc05b1ba01..fc12177bee 100644 --- a/_config.yml +++ b/_config.yml @@ -1009,7 +1009,10 @@ navigation: title: "Installation" position: 8 "getting-started/installation/nuget": - title: "NuGet Installation" + title: "NuGet Installation" + "getting-started/licensing": + title: "Activating Your License" + position: 7 "getting-started/adding-telerik-ui-to-an-application": title: "Adding Telerik UI to an Application" position: 9 @@ -1042,7 +1045,7 @@ navigation: title: "Style and Appearance" position: 4 "licensing": - title: "Distribution and Licensing" + title: "Redistribution" position: 5 "upgrade": title: "Upgrade" diff --git a/common-information/installation-installing-dependencies-wpf.md b/common-information/installation-installing-dependencies-wpf.md index 09ed3eb8b7..5325ac54bf 100644 --- a/common-information/installation-installing-dependencies-wpf.md +++ b/common-information/installation-installing-dependencies-wpf.md @@ -13,7 +13,10 @@ site_name: WPF The following topic describes all controls from UI for WPF and the assemblies they require when deploying your application. ->Note that the assembly __Telerik.Windows.Controls__ must always be part of your application. +The following two assemblies should be always referenced in the project: + +* `Telerik.Windows.Controls.dll` +* `Telerik.Licensing.Runtime.dll`—The licensing assembly can be installed also via the `Telerik.Licensing` NuGet package. Controls | Assembly --- | --- @@ -126,7 +129,7 @@ RadTreeView | Telerik.Windows.Controls.Navigation, Telerik.Windows.Data RadVirtualGrid | Telerik.Windows.Controls.VirtualGrid, Telerik.Windows.Controls, Telerik.Windows.Data RadVirtualKeyboard | Telerik.Windows.Controls.Navigation RadWatermarkTextBox | Telerik.Windows.Controls -RadWebCam | Telerik.Windows.Controls, Telerik.Windows.Controls.Media, Telerik.Windows.MediaFoundation, MediaFoundation, SharpDX, SharpDX.Direct3D9 +RadWebCam | Telerik.Windows.Controls, Telerik.Windows.Controls.Media, Telerik.Windows.MediaFoundation, MediaFoundation, the SkiaSharp NuGet package RadWindow | Telerik.Windows.Controls.Navigation RadWizard | Telerik.Windows.Controls, Telerik.Windows.Data, Telerik.Windows.Controls.Navigation RadWordsProcessing | Telerik.Windows.Documents.Core, Telerik.Windows.Documents.Flow, Telerik.Windows.Zip, Telerik.Windows.Documents.Flow.FormatProviders.Pdf, Telerik.Windows.Documents.Fixed diff --git a/getting-started/explore-control-features.md b/getting-started/explore-control-features.md index 5b8f6d760d..0ad9194e1d 100644 --- a/getting-started/explore-control-features.md +++ b/getting-started/explore-control-features.md @@ -10,50 +10,42 @@ position: 3 # Explore UI for WPF Control Features -Once you have the controls [working in your project]({%slug getting-started-first-steps%}), it's time to see what they can do. This article provides a short overview of how to get started with finding control functionality so you can use it. +Once you have the controls [working in your project]({%slug nuget-setup-lifecycle%}), it's time to see what they can do. This article provides a short overview of how to get started with finding control functionality so you can use it. ## Demos To get an overview of what each control offers, the fastest approach is download the [WFP Demos Application](http://demos.telerik.com/wpf). -You can also [download the source code of the demo application]({%slug installing-wpf-demos%}#getting-the-source-code) from your [telerik.com account](https://www.telerik.com/account/downloads/product-download?product=RCWPF) as a Visual Studio project and play around with the demos in the comfort of your IDE. The `Telerik_UI_for_WPF_[version]_Demos.zip` archive contains the respective source code. +You can also [download the source code of the demo application]({%slug installing-wpf-demos%}#getting-the-source-code) from your [telerik.com account](https://www.telerik.com/account/downloads/product-download?product=RCWPF) as a Visual Studio project and play around with the demos in the comfort of your IDE. -## Explore properties and tags +## Properties and Tags You can **explore** the available properties, events and inner tags of any control through the VS **intellisense** to get a quick glimpse of their concepts and availability. ->caption Figure 1: Explore Intellisense in the markup - -![Explore Intellisense in the markup](adding-telerik-ui-to-an-application/images/installation-adding-application-using-intellisense-vs-wpf-0.png "Explore Intellisense in the markup") - ->caption Figure 2: Explore Intellisense in the code-behind - -![Explore Intellisense in the code-behind](adding-telerik-ui-to-an-application/images/installation-adding-application-using-intellisense-vs-wpf-2.png "Explore Intellisense in the code-behind") - ## Documentation In addition to that, the **documentation** provides a section for each control that contains help articles **on distinct features and API reference**. ->caption Figure 3: Typical control documentation structure +__Typical control documentation structure__ ![Typical control documentation structure](images/typical-control-docs-structure.png "Typical control documentation structure") ## Design-time -Last, but not least, some most common tasks and configuration options are available in the control's [Smart Tag in Design Mode]({%slug common-smart-tags%}). You will also find **design-time wizards** and **links** that can be useful when you are getting started with a feature, or even for advanced users who want to save time with setting up collections, data sources or properties. +Some of the most common tasks and configuration options are available in the control's [Smart Tag in Design Mode]({%slug common-smart-tags%}). You will also find **design-time wizards** and **links** that can be useful when you are getting started with a feature, or even for advanced users who want to save time with setting up collections, data sources or properties. ->caption Figure 4: Smart Tag features +__Smart Tag features__ ![Smart Tag features](images/smart-tag-features.png "Smart Tag features") +## SDK Examples + +The SDK Examples (also known as Developer Focused Examples) are a good source with runnable project showing different features of the Telerik UI for WPF controls. Find the SDK Examples in the [corresponding GitHub repository](https://github.com/telerik/xaml-sdk). + ## Next Steps Now that you have the Telerik UI for WPF controls running in your project, you may want to explore their features, customize their behavior or change their appearance. Below you can find guidance on getting started with such tasks: -* [Change control appearance]({%slug getting-started-change-control-appearance%}) -* [Further information]({%slug getting-started-next-steps%}) - -## See Also +* [Change Control Appearance]({%slug getting-started-change-control-appearance%}) +* [Further Information]({%slug getting-started-next-steps%}) -* [First Steps]({%slug getting-started-first-steps%}) -* [Progress Virtual Classroom](https://www.telerik.com/account/support/virtual-classroom) diff --git a/getting-started/first-steps-msi-or-zip.md b/getting-started/first-steps-msi-or-zip.md index 8332591b69..55a2badb1e 100644 --- a/getting-started/first-steps-msi-or-zip.md +++ b/getting-started/first-steps-msi-or-zip.md @@ -12,7 +12,7 @@ position: 2 This article describes the lifecycle of a Telerik application. This includes creating, deploying, redistributing, and upgrading an application with referenced Telerik dlls. -The topic shows what is the lifecycle when using the __.msi__ or __.zip__ file to get the dlls. As an alternative, you can use [NuGet packages]({%slug nuget-setup-lifecycle%}) or [Telerik UI for WPF Extension]({%slug getting-started-first-steps%}) as shown in the corresponding articles in this documentation section. +The topic shows what is the lifecycle when using the __.msi__ or __.zip__ file to get the dlls. As an alternative, you can use [NuGet packages]({%slug nuget-setup-lifecycle%}) or [Telerik UI for WPF Extension]({%slug getting-started-first-steps%}). ## Creating a Project @@ -40,6 +40,10 @@ Use the Visual Studio's Reference Manager to browse and reference the Telerik dl If you need to set a [Telerik theme]({%slug common-styling-appearance-available-themes%}) different than the default one check the [Xaml vs. NoXaml]({%slug xaml-vs-noxaml%}) and the [Setting a Theme]({%slug styling-apperance-implicit-styles-overview%}) articles. +## Installing a License Key + +To use the Telerik WPF product you will need to install a valid license key. Otherwise, you will see warning messages and banners related to the licensing. See how to activate a license in the [Installing License Key]({%slug installing-license-key%}) article. + ## Adding Telerik Controls After you create the WPF project and reference the Telerik assemblies, add any UI and related code-behind, models, and styles. This example will show a fundamental setup, including a RadTabControl with few tabs defined in XAML. diff --git a/getting-started/first-steps-nuget.md b/getting-started/first-steps-nuget.md index fc781c1b51..40d8ebb165 100644 --- a/getting-started/first-steps-nuget.md +++ b/getting-started/first-steps-nuget.md @@ -10,9 +10,7 @@ position: 0 # First Steps With Nuget Packages -This article describes the lifecycle of a Telerik application. This includes creating, deploying, redistributing, and upgrading an application with referenced Telerik dlls. - -The topic shows what is the lifecycle when using the Telerik __nuget packages__ to get dlls. As an alternative, you can use [MSI or Zip files]({%slug msi-or-zip-setup-lifecycle%}), or [Telerik UI for WPF Extension]({%slug getting-started-first-steps%}) as shown in the corresponding articles in this documentation section. +This article describes the lifecycle of a Telerik application when using NuGet packages. This includes creating, deploying, redistributing, and upgrading an application with referenced Telerik dlls. ## Creating a Project diff --git a/getting-started/first-steps.md b/getting-started/first-steps.md index c261597028..8e31d64df4 100644 --- a/getting-started/first-steps.md +++ b/getting-started/first-steps.md @@ -12,21 +12,19 @@ position: 1 This article explains how to get the Telerik UI for WPF controls in your project and start using them quickly. -Once you have your first simple control up and running, take a look at the [next steps](#next-steps) section to start exploring the control functionality in more details. +The topic shows what is the lifecycle when using the Telerik Visual Studio Extension. As an alternative, you can use [NuGet packages]({%slug nuget-setup-lifecycle%}). -For additional resources you can also review the Related Articles section on the right. +## Downloading the Extension -## Download the Controls +To download the Telerik Visual Studio Extenion, you can either download the `.msi` installer from the Telerik UI for WPF [download page](https://www.telerik.com/account/product-download?product=RCWPF) or use the __Extensions__ menu of Visual Studio to download the extension from the marketplace (*"Progress Telerik UI for WPF Extension"*). -The easiest way to get the controls to your development machine is to use the [Progress Control Panel](https://www.telerik.com/download-trial-file/v2/control-panel) or to download the automated MSI installer from [your telerik.com account](https://www.telerik.com/account/product-download?product=RCWPF). +__Download automated (.msi) installer__ ->caption Figure 1: Download automated (.msi) installer +![Download automated installer Telerik_UI_for_WPF__Dev.msi](images/download-msi.png") -![Download automated installer Telerik_UI_for_WPF__Dev.msi](images/download-msi.png "Telerik_UI_for_WPF__Dev.msi") +If you are not a customer, you can [download a free, fully functional trial](https://www.telerik.com/try/ui-for-wpf) and the same options will apply to you as well. -> If you are not a customer, you can [download a free, fully functional trial](https://www.telerik.com/try/ui-for-wpf) and the same options will apply to you as well. - ->tip The following article can help you choose the installation type that is most suitable for your needs and preferences: [Installation Approaches]({%slug installation-installing-which-file-do-i-need%}). +The following article can help you choose the installation type that is most suitable for your needs and preferences: [Installation Approaches]({%slug installation-installing-which-file-do-i-need%}). ## Creating Application with Telerik Visual Studio Extensions @@ -38,25 +36,39 @@ The Visual Studio Extensions can be accessed through the Extensions | Telerik | 2. Create new Telerik WPF application. - #### __Figure 2: Go to Telerik > Telerik UI for WPF > Create New Telerik Project__ - ![Run Create Project Wizard](../integration/visual-studio-extensions/images/VSExtentions_WPF_OverviewMenuCreate.png "Run Create Project Wizard") + __Go to Telerik > Telerik UI for WPF > Create New Telerik Project__ + + ![Run Create Project Wizard](../integration/visual-studio-extensions/images/VSExtentions_WPF_OverviewMenuCreate.png) + + __Creating new Telerik application__ - #### __Figure 3: Creating new Telerik application__ ![Creating new Telerik application](images/installation-adding-to-application-create-application-and-adding-control-1.png) 3. Choose the project template and the corresponding settings. For an empty project without any Telerik controls added to the view, choose the Blank option. - #### __Figure 4: Choosing an application template__ + __Choosing an application template__ + ![Choosing an application template](images/installation-adding-to-application-create-application-and-adding-control-2.png) - At this point the project references only the common Telerik.Windows.Controls.dll and you can start adding controls in the UI. + At this point the project references only the common `Telerik.Windows.Controls.dll` and `Telerik.Licensing.Runtime.dll`, and you can start adding controls in the UI. - You can further configure the project using the Project Configuration Wizard. You can do that by going to the __Extensions > Telerik > Telerik UI for WPF > Configure Project__ menu in Visual Studio. When you open the wizard you can select the controls you are going to use from the list (or search them in the search box). Once you have selected them, click Finish. This will add the required dlls and references to your project. +4. In case you haven't installed a license key already, you can download one using the License Validation screen. + + __License validation screen (license not found)__ + + ![License validation screen](images/installation-adding-to-application-create-application-and-adding-control-license-validation.png) + + __License validation screen (successfully downloaded a license)__ + + ![License validation screen - successfull download](images/installation-adding-to-application-create-application-and-adding-control-successfull-download.png) + +You can further configure the project using the Project Configuration Wizard. You can do that by going to the __Extensions > Telerik > Telerik UI for WPF > Configure Project__ menu in Visual Studio. When you open the wizard you can select the controls you are going to use from the list (or search them in the search box). Once you have selected them, click Finish. This will add the required dlls and references to your project. - #### __Figure 5: Adding references to the charting controls__ - ![Common Installing Creating Application 013 WPF](images/installation-adding-to-application-create-application-and-adding-control-3.png) +__Adding references to the charting controls__ + +![Common Installing Creating Application 013 WPF](images/installation-adding-to-application-create-application-and-adding-control-3.png) - > This step is optional and you will only need it if you use controls that are not defined in Telerik.Windows.Controls.dll. +This step is optional and you will only need it if you use controls that are not defined in `Telerik.Windows.Controls.dll`. ## Add a Telerik Control to the Project @@ -75,15 +87,14 @@ In order to use the __RadGridView__ control in your projects, you have to add re You can add __RadGridView__ manually by writing the XAML code in __Example 1__ or you can also add the control by dragging it from the Visual Studio Toolbox and dropping it over the XAML view. -#### __[XAML] Example 1: Adding RadGridView in XAML__ - +#### __[XAML] Adding RadGridView in XAML__ {{region xaml-gridview-getting-started2_0}} {{endregion}} If you run the application, you will see an empty grid with no columns and rows as demonstrated in __Figure 6__. -#### __Figure 6: The empty grid generated by the code in Example 1__ +__The empty grid generated by the code in Example 1__ ![Telerik {{ site.framework_name }} DataGrid GettingStarted 2](images/RadGridView_GettingStarted_2.png) @@ -91,8 +102,7 @@ If you run the application, you will see an empty grid with no columns and rows In order to populate the __RadGridView__ control with data, you should create a collection of business objects. Create a new class named __Profile__ and add several different type properties to it, as shown in __Example 2__. -#### __[C#] Example 2: Simple business class__ - +#### __[C#] Simple business class__ {{region cs-gridview-getting-started2_0}} public class Profile { @@ -103,8 +113,7 @@ In order to populate the __RadGridView__ control with data, you should create a } {{endregion}} -#### __[VB.NET] Example 2: Simple business class__ - +#### __[VB.NET] Simple business class__ {{region vb-gridview-getting-started2_0}} Public Class Profile Public Property ID As Integer @@ -116,8 +125,7 @@ End Class Next, create a collection of Profile objects in the MainWindow and set the RadGridView ItemSource. -#### __[C#] Example 3: Simple business class__ - +#### __[C#] Simple business class__ {{region cs-gridview-getting-started2_0}} public MainWindow() { @@ -133,9 +141,7 @@ Next, create a collection of Profile objects in the MainWindow and set the RadGr } {{endregion}} - -#### __[VB.NET] Example 3: Simple business class__ - +#### __[VB.NET] Simple business class__ {{region vb-gridview-getting-started2_0}} Public Sub New() Me.InitializeComponent() @@ -159,8 +165,7 @@ Next, create a collection of Profile objects in the MainWindow and set the RadGr Now that you have prepared the needed sample data, you need to bind it to each column in XAML as shown in the Example 4 below. -#### __[XAML] Example 4: Define RadGridView in XAML__ - +#### __[XAML] Define RadGridView in XAML__ {{region xaml-gridview-getting-started2_1}} The [Progress Control Panel](https://www.telerik.com/download-trial-file/v2/control-panel) and the [Visual Studio Extensions]({%slug radcontrols-for-wpf-vs-extensions-overview-wpf%}) will automatically download and store your license key in the `%appdata%\Telerik` directory. This makes it available for all projects developed on the local machine. + +## Activating the UI for WPF Components + +To activate the UI for WPF components: + +* Copy the [downloaded](#downloading-the-license-key) `telerik-license.txt` license key file to your home directory (`%appdata%\Telerik`). This makes it available for all projects developed on the local machine. + +* Alternatively, copy the `telerik-license.txt` license key file to the root folder of your project. This makes the license key available only to this project. Do not commit the file to source control as this is your personal license key. + +When you build the project, the `Telerik.Licensing` NuGet package automatically locates the license file and uses it to activate the product. If your project doesn’t use NuGet packages, see [Adding a License Key to Projects without NuGet References](#adding-a-license-key-to-projects-without-nuget-references). + +## Adding a License Key to Projects without NuGet References + +Telerik strongly recommends the use of NuGet packages whenever possible. Only include the license key as a code snippet when NuGet packages are not an option. + +If you cannot use NuGet packages in your project, add the license as a code snippet: + +1. Go to the [License Keys](https://www.telerik.com/account/your-licenses/license-keys) page in your Telerik account. + +1. On the Progress® Telerik® UI for WPF row, click the __View key__ link in the __SCRIPT KEY__ column. + +1. Copy the C# code snippet into a new file, for example, `TelerikLicense.cs`. + +1. Add the `TelerikLicense.cs` file to your project. + + Do not publish the license key code snippet in publicly accessible repositories. This is your personal license key. + +## Updating Your License Key + +Whenever you purchase a new Telerik UI for WPF license or renew an existing one, always [download a new license key](#downloading-the-license-key). The new license key includes information about all previous license purchases. This process is referred to as a license key update. Once you have the new license key, use it to [activate the components](#activating-the-ui-for-wpf-components). + +## See Also +* [License Activation Errors and Warnings]({%slug license-activation-errors-and-warnings%}) +* [Adding the License Key to CI Services]({%slug installing-license-to-ci-services%}) +* [Frequently Asked Questions about Your UI for WPF License Key]({%slug license-frequently-asked-questions%}) \ No newline at end of file diff --git a/getting-started/licensing/installing-license-to-ci-services.md b/getting-started/licensing/installing-license-to-ci-services.md new file mode 100644 index 0000000000..5c9fe0eb89 --- /dev/null +++ b/getting-started/licensing/installing-license-to-ci-services.md @@ -0,0 +1,60 @@ +--- +title: Adding License Key to CI Services +page_title: Installing License Key to CI Services +description: The article describes how to install a license key for the Telerik UI for WPF product to CI Services. +slug: installing-license-to-ci-services +tags: installing,ui,for,wpf,file,license,key,ci,service,continuous,integration,cd,cicd +published: True +position: 2 +--- + +# Adding the License Key to CI/CD Services + +This article describes how to set up and activate your Telerik UI for WPF [license key]({%slug installing-license-key%}) across a few popular CI/CD services by using environment variables. + +When working with CI/CD platforms, always add the `Telerik.Licensing` NuGet package as a project dependency. This package activates the Telerik UI for WPF components at build time by using the provided license key. + +> If you cannot use NuGet packages in your project, you can add the license key as an assembly attribute as shown in the [Installing License Key]({%slug installing-license-key%}#adding-a-license-key-to-projects-without-nuget-references) article. + +The license activation process in a CI/CD environment involves the following steps: + +1. [Download a license key]({%slug installing-license-key%}#downloading-the-license-key) from your [Telerik account](https://www.telerik.com/account/your-licenses/license-keys). + +1. Add the `Telerik.Licensing` NuGet package as a project dependency: `` + +1. [Create an environment variable](#creating-an-environment-variable) named `TELERIK_LICENSE` and add your UI for WPF license key as a value. + +## Creating an Environment Variable + +The recommended approach for providing your license key to the `Telerik.Licensing` NuGet package is to use environment variables. Each CI/CD platform has a different process for setting environment variables and this article lists only some of the most popular examples. + +### Azure Pipelines (YAML) + +1. Create a new [User-defined Variable](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch) named `TELERIK_LICENSE`. + +1. Paste the contents of the license key file as a value. + +### Azure Pipelines (Classic) + +1. Create a new [user-defined variable](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=classic%2Cbatch) named `TELERIK_LICENSE`. + +1. Paste the contents of the license key file as a value. + +### GitHub Actions + +1. Create a new [Repository Secret](https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository) or an [Organization Secret](https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization). + +1. Set the name of the secret to `TELERIK_LICENSE` and paste the contents of the license file as a value. + +1. After running `npm install` or `yarn`, add a build step to activate the license: + + #### __[YML]__ + {{region installing-license-to-ci-services-0}} + env: + TELERIK_LICENSE: ${{ secrets.TELERIK_LICENSE }} + {{endregion}} + +## See Also +* [License Activation Errors and Warnings]({%slug license-activation-errors-and-warnings%}) +* [Setting Up Your License Key]({%slug installing-license-key%}} +* [Frequently Asked Questions about Your UI for WPF License Key]({%slug license-frequently-asked-questions%}) diff --git a/getting-started/licensing/license-activation-errors-and-warnings.md b/getting-started/licensing/license-activation-errors-and-warnings.md new file mode 100644 index 0000000000..084ed0b931 --- /dev/null +++ b/getting-started/licensing/license-activation-errors-and-warnings.md @@ -0,0 +1,59 @@ +--- +title: License Activation Errors and Warnings +page_title: License Activation Errors and Warnings +description: The article lists common license activation errors and warnings for the Telerik UI for WPF product. +slug: license-activation-errors-and-warnings +tags: installing,ui,for,wpf,file,license,key,activation,errors,warnings +published: True +position: 1 +--- + +# License Activation Errors and Warnings + +Starting with the 2025 Q1 release, using Telerik UI for WPF without a license or with an invalid license causes specific license warnings and errors. This article defines what an invalid license is, explains what is causing it, and describes the related license warnings and errors. + +A missing, expired, or invalid license will result in: + +* A watermark appearing on application startup. + +* A modal dialog appearing on application startup. Clicking the __OK__ button of the dialog closes the dialog and removes the banner until the next application startup. + +* A warning message similar to the following appearing in the build log: + + ![A picture showing the license key errors in the Visual Studio Error List pane](images/license-activation-errors-and-warnings-0.png) + + ![A picture showing the license key errors in the Visual Studio Output pane](images/license-activation-errors-and-warnings-1.png) + +## Invalid License + +An invalid license can be caused by any of the following: + +* Using an expired subscription license—subscription licenses expire at the end of the subscription term. + +* Using a perpetual license for product versions released outside the validity period of your license. + +* Using an expired trial license. + +* A missing license for Telerik UI for WPF. + +* Not installing a license key in your application. + +* Not updating the license key after renewing your Telerik UI for WPF license. + +## License Warnings and Errors + +When using Telerik UI for WPF in a project with an expired or missing license, the `Telerik.Licensing` build task will indicate the following errors or conditions: + +| Condition or Error | Message Code | Solution | +| ------------------ | ------------ | -------- | +| `No license key is detected` | TKL002 | [Install a license key]({%slug installing-license-key%}) to activate the UI components and remove the error message. | +| `Invalid license key` | TKL003 | [Download a new license key]({%slug installing-license-key%}#downloading-the-license-key) and install it to activate the UI components and remove the error message. | +| `Your subscription license has expired.` | TKL103; TKL104 | Renew your subscription and [download a new license key]({%slug installing-license-key%}#downloading-the-license-key). | +| `Your perpetual license is invalid.` | TKL102 | You are using a product version released outside the validity period of your perpetual license. To remove the error message, do either of the following:
  • Renew your subscription and [download a new license key]({%slug installing-license-key%}#downloading-the-license-key).
  • Downgrade to a product version included in your perpetual license as indicated in the message.
| +| `Your trial license has expired.` | TKL105 | Purchase a commercial license to continue using the product. | +| `Your license is not valid for the detected product(s).` | TKL101 | Review the purchase options for the listed products. Alternatively, remove the references to the listed packages from `package.json.` | + +## See Also +* [Setting Up Your License Key]({%slug installing-license-key%}) +* [Frequently Asked Questions about Your UI for WPF License Key]({%slug license-frequently-asked-questions%}) +* [Adding the License Key to CI Services]({%slug installing-license-to-ci-services%}) diff --git a/getting-started/licensing/license-frequently-asked-questions.md b/getting-started/licensing/license-frequently-asked-questions.md new file mode 100644 index 0000000000..f6e424eb51 --- /dev/null +++ b/getting-started/licensing/license-frequently-asked-questions.md @@ -0,0 +1,94 @@ +--- +title: Frequently Asked Questions +page_title: Installing License Key - Frequently Asked Questions +description: The article lists the frequently asked questions (FAQ) on how to install a license key for the Telerik UI for WPF product. +slug: license-frequently-asked-questions +tags: installing,ui,for,wpf,file,license,key,ci,service,faq,asked,questions +published: True +position: 3 +--- + +# Frequently Asked Questions About Installing Telerik License Key + +This article lists the answers to the most frequently asked questions (FAQs) about working with the Telerik UI for WPF license key. + +## Does the license key expire? + +Yes, the license key expires at the end of your support subscription: + +* For trial users, this is at the end of your 30-day trial. + +* For commercial license holders, this is when your subscription term expires. + +You will need to obtain and install a new license key after starting a trial, renewing a license, or upgrading a license. + +> An expired perpetual license key is valid for all Telerik UI for WPF versions published before its expiration date. + +## Will the product function with an expired license key? + +This depends on your license type. + +* __Perpetual licenses__ will continue to function normally with an expired license key. However, the following will happen if you update or install a package version which is released after the expiration date of the license: + + * A watermark appears on application startup. + * A modal dialog appears on application startup. + * A warning message is logged in the build log. + + See the [Invalid License]({%slug license-activation-errors-and-warnings%}#invalid-license) section for more information. + +* __Subscription licenses__ will prevent you from building the application with an expired license key. Deployed applications will continue to function normally. + +* __Trial licenses__ will prevent the applications from functioning normally once the trial period has expired. The following will happen if you try to build or run the application: + + * A watermark appears on application startup. + * A modal dialog appears on application startup. + * A warning message is logged in the build log. + + See the [Invalid License]({%slug license-activation-errors-and-warnings%}#invalid-license) section for more information. + +## I updated the version of the UI for WPF packages in my project and the invalid license errors have appeared. What is the cause of this behavior? + +The most likely cause is that the newly installed Telerik UI for WPF components were released after the expiration date of your current license. To fix this issue: + +1. [Download a new license key]({%slug installing-license-key%}#downloading-the-license-key). + +1. [Activate the new license key]({%slug installing-license-key%}) in your project. + +## Can I use the same license key in multiple builds? + +You can use your personal license key in multiple pipelines, builds, and environments. + +However, each individual developer must use a unique personal license key. + +## Do I need an Internet connection to activate the license? + +No, the license activation and validation are performed entirely offline. + +## Do I have to add the license key to source control? + +No, you do not have to add the `telerik-license.txt` license key file or its contents to source control. + +Build servers must use the `TELERIK_LICENSE` environment variable described in [Adding the License Key to CI Services]({%slug installing-license-to-ci-services%}). + +> Do not store the license key in plaintext, for example, in a GitHub Actions Workflow definition. + +## What happens if both the environment variable and the license key file are present? + +If both the `TELERIK_LICENSE` environment variable and the `telerik-license.txt` file are present, then the environment variable will be used. + +To enforce the use of the license key file, unset the environment variable. + +## My team has more than one license holder. Which key do we have to use? + +* To activate Telerik UI for WPF on your development machine, use the key associated with your personal account. + +* To activate Telerik UI for WPF in a CI/CD environment, use any of the license keys in your team. + +## Are earlier versions of Telerik UI for WPF affected? + +No, versions released prior to January 2025 (Q1) do not require a license key. + +## See Also +* [License Activation Errors and Warnings]({%slug license-activation-errors-and-warnings%}) +* [Setting Up Your License Key]({%slug installing-license-key%}) +* [Adding the License Key to CI Services]({%slug installing-license-to-ci-services%}) diff --git a/getting-started/licensing/licensing-versions.md b/getting-started/licensing/licensing-versions.md new file mode 100644 index 0000000000..69eda85db5 --- /dev/null +++ b/getting-started/licensing/licensing-versions.md @@ -0,0 +1,22 @@ +--- +title: Licensing to WPF Versions Dependencies +page_title: Licensing to UI for WPF Version Dependencies +description: The article describes the dependencies between the versions of the Telerik.Licensing.Runtime dll and the Telerik UI for WPF dlls. +slug: licensing-version +tags: installing,ui,for,wpf,file,license,key,version +published: True +position: 4 +--- + +# Licensing to WPF Versions Dependencies + +The Telerik UI for WPF assemblies depend on a specific version of the `Telerik.Licensing.Runtime.dll` (or the corresponding `Telerik.Licensing` NuGet package). This article lists the dependencies between the versions in the different Telerik UI for WPF releases. + +| Telerik.Licensing Version | UI for WPF Version
(From) | UI for WPF Version
(To) | +| ------------------------- | ----------------------------- | ---------------------------- | +| 1.4.6 | 2025.1.211 (latest) | N/A | + +## See Also +* [License Activation Errors and Warnings]({%slug license-activation-errors-and-warnings%}) +* [Setting Up Your License Key]({%slug installing-license-key%}} +* [Frequently Asked Questions about Your UI for WPF License Key]({%slug license-frequently-asked-questions%}) \ No newline at end of file diff --git a/getting-started/telerik-namespace-declaration.md b/getting-started/telerik-namespace-declaration.md index c13d8394d7..b100bd3933 100644 --- a/getting-started/telerik-namespace-declaration.md +++ b/getting-started/telerik-namespace-declaration.md @@ -13,32 +13,18 @@ site_name: WPF The following topic will show you how to manually declare a namespace in XAML. -Almost all Telerik controls can be found in the 'telerik' URI namespace schema (see Example 1). You can use only this namespace to access all controls from Telerik assemblies that you are referring in your application. You cannot access controls from assemblies that you are not referring. +Almost all Telerik controls can be found in the `telerik` URI namespace schema. You can use only this namespace to access all controls from Telerik assemblies that you are referring in your application. You cannot access controls from assemblies that you are not referring. ->There are few controls which are in another namespace schema. For example, such are RadPivotGrid and RadPivotFieldList and their namespace is: xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot". +>There are few controls which are in another namespace schema. For example, such are RadPivotGrid and RadPivotFieldList and their namespace is `xmlns:pivot="http://schemas.telerik.com/2008/xaml/presentation/pivot"`. 1. Open your WPF application with the Telerik assemblies referenced in it. 2. Open the XAML file with the view where you want to add the Telerik controls. -3. Go to the opening tag of the parent control (like the Window or UserControl) and type in the "telerik" namespace identifier. When you type the "equals" character in the drop down list select the 'http://schemas.telerik.com/2008/xaml/presentation' item. - - #### __[XAML] Telerik namespace definition__ - {{region installation-adding-application-namespace-declaration-0}} - xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation" - {{endregion}} - - {% if site.site_name == 'WPF' %} - ![Common Installing Namespace Declaration 1](images/installation-adding-application-using-intellisense-vs-wpf-0.png) - {% else %} - ![Common Installing Namespace Declaration 2](images/installation-adding-application-using-intellisense-vs-wpf-1.png) - {% endif %} - - The result should be similar to this. - - {% if site.site_name == 'WPF' %} +3. Go to the opening tag of the parent control (like the Window or UserControl) and type in the "telerik" namespace identifier. When you type the "equals" character in the drop down list select the `http://schemas.telerik.com/2008/xaml/presentation` item. + #### __[XAML] Telerik namespace added in XAML__ - {{region installation-adding-application-namespace-declaration-1}} + {{region installation-adding-application-namespace-declaration-0}} {{endregion}} - {% else %} - #### __[XAML] Telerik namespace added in XAML__ - {{region installation-adding-application-namespace-declaration-2}} - - - - - {{endregion}} - {% endif %} 4. Now you can declare any controls, existing in the Telerik namespace, which are included in the assemblies added to the project. - {% if site.site_name == 'WPF' %} #### __[XAML] Using the Telerik namespace__ - {{region installation-adding-application-namespace-declaration-3}} + {{region installation-adding-application-namespace-declaration-1}} {{endregion}} - {% else %} - #### __[XAML] Using the Telerik namespace__ - {{region installation-adding-application-namespace-declaration-4}} - - - - - - - {{endregion}} - {% endif %} ->tip See the Telerik assemblies required by each control in the {% if site.site_name == 'Silverlight' %}[Controls Dependencies]({%slug installation-installing-controls-dependencies%}){% else %}[Controls Dependencies]({%slug installation-installing-controls-dependencies-wpf%}){% endif %} article. +>tip See the Telerik assemblies required by each control in the [Controls Dependencies]({%slug installation-installing-controls-dependencies-wpf%}) article. -{% if site.site_name == 'WPF' %} ## See Also - -* [Upgrading Telerik UI Trial to Telerik UI Developer License or Newer Version]({%slug installation-upgrading-from-trial-to-developer-license-wpf%}) -{% endif %} +* [Upgrading Telerik UI Trial to Telerik UI Developer License]({%slug installation-upgrading-from-trial-to-developer-license-wpf%}) diff --git a/knowledge-base/kb-installation-cannot-load-licensing-assembly.md b/knowledge-base/kb-installation-cannot-load-licensing-assembly.md new file mode 100644 index 0000000000..23f71a4d1d --- /dev/null +++ b/knowledge-base/kb-installation-cannot-load-licensing-assembly.md @@ -0,0 +1,39 @@ +--- +title: Could not Load File Or Assembly Telerik.Licensing.Runtime, Version 1.4.6.0 Runtime Error +description: FileNotFoundException thrown at runtime when the version of the referenced Telerik.Licensing.Runtime dll is mismatched. +page_title: FileNotFoundException Exception Cannot Load Telerik.Licensing.Runtime Assembly +type: troubleshooting +slug: kb-installation-cannot-load-licensing-assembly +position: 0 +tags: installation, telerik, licensing, license, key, load, exception +res_type: kb +--- + +## Environment + + + + + + + + + + + + +
Product Version2025.1.211
ProductUI for WPF
+ +## Description + +`FileNotFoundException` is thrown at runtime, which states that the `Telerik.Licensing.Runtime` assembly cannot be loaded. The error message is something like this: + +`FileNotFoundException: Could not load file or assembly 'Telerik.Licensing.Runtime, Version=1.4.6.0, Culture=neutral, PublicKeyToken=tokenhere'. The system cannot find the file specified.` + +This may happen if you upgrade to 2025 Q1 from an older version. With 2025 Q1, a new [licensing mechanism]({%slug installing-license-key%}) was introduced, which requires you to reference the `Telerik.Licensing.Runtime` dll. + +## Solution + +The exception means that the version of the `Telerik.Licensing.Runtime` dll mismatches the version of the version expected by the other Telerik UI for WPF dlls. This may happen if the project references the Telerik dlls containing the component/controls from one version and the `Telerik.Licensing.Runtime` dll from another version of Telerik UI for WPF. + +To resolve the problem, make sure that all Telerik controls are referenced from the same installation place, thus using the same release version. \ No newline at end of file diff --git a/knowledge-base/kb-installation-license-licx-file.md b/knowledge-base/kb-installation-license-licx-file.md new file mode 100644 index 0000000000..ab2ae979f6 --- /dev/null +++ b/knowledge-base/kb-installation-license-licx-file.md @@ -0,0 +1,33 @@ +--- +title: License .licx File Appeared in the Project Directory +description: A license.licx file is automatically generated on build and added in the Properties folder of the WPF project. +page_title: License.licx File is Automatically Generated and Could Bring Compile Time Errors +type: troubleshooting +slug: kb-installation-license-licx-file +position: 0 +tags: installation, telerik, licensing, licx +res_type: kb +--- + +## Environment + + + + + + + + + + + + +
Product Version2025.1.211
ProductUI for WPF
+ +## Description + +In some versions of Telerik UI for WPF, after referencing the Telerik assemblies, the Visual Studio Designer can generate a [license.licx](https://docs.microsoft.com/en-us/dotnet/framework/tools/lc-exe-license-compiler) file in the __Properties__ folder of the WPF project. The file lists the Telerik dlls used at design-time, along with their concrete versions. This can bring errors when changing the version of the referenced Telerik dlls. + +## Solution + +The file is automatically generated by Visual Studio and it is not necessary for building an running the project, or for redistributing the application. You can safely delete it. \ No newline at end of file diff --git a/knowledge-base/kb-installation-missing-license-vs-2019.md b/knowledge-base/kb-installation-missing-license-vs-2019.md new file mode 100644 index 0000000000..1a6aaf8c69 --- /dev/null +++ b/knowledge-base/kb-installation-missing-license-vs-2019.md @@ -0,0 +1,37 @@ +--- +title: No License Key Found Warning in Visual Studio 2019 When License Key is Present +description: No license key found error shown in Visual Studio 2019 .NET Framework project even when license key is installed. +page_title: No Product Reference Detected Licensing Error Shown in .NET Framework Project +type: troubleshooting +slug: kb-installation-missing-license-vs-2019 +position: 0 +tags: installation, telerik, licensing, license, key, not, found +res_type: kb +--- + +## Environment + + + + + + + + + + + + +
Product Version2025.1.211
ProductUI for WPF
+ +## Description + +The following licensing warnings occur when building a .NET Framework project using Visual Studio 2019, when a license key is installed. + +* `No Telerik or Kendo UI product references detected in project. Consult the product documentation or contanct support at progress.com` + +* `No license key found` + +## Solution + +The error manifests because of a limitation in the licensing implementation when loaded in the specific setup. You can safely ignore it. Alternatively, use Visual Studio 2022. \ No newline at end of file diff --git a/knowledge-base/kb-installation-missing-licensing-assembly.md b/knowledge-base/kb-installation-missing-licensing-assembly.md new file mode 100644 index 0000000000..61b251a59c --- /dev/null +++ b/knowledge-base/kb-installation-missing-licensing-assembly.md @@ -0,0 +1,39 @@ +--- +title: Could not Find Assembly Telerik.Licensing.Runtime Compile Error After Upgrade +description: Unknown build error 'Could not find assembly Telerik.Licensing.Runtime' exception after upgrade. +page_title: The Project Cannot Find Telerik.Licensing.Runtime Assembly After Upgrade +type: troubleshooting +slug: kb-installation-missing-licensing-assembly +position: 0 +tags: installation, telerik, licensing, license, key +res_type: kb +--- + +## Environment + + + + + + + + + + + + +
Product Version2025.1.211
ProductUI for WPF
+ +## Description + +An error occurs after upgrade that the `Telerik.Licensing.Runtime` assembly cannot be found. The error message is something like this: + +`Unknown build error, 'Could not find assembly 'Telerik.Licensing.Runtime, Version=1.4.6.0, Culture=neutral, PublicKeyToken=tokenhere'. Either explicitly load this assembly using a method such as LoadFromAssemblyPath() or use a MetadataAssemblyResolver that returns a valid assembly.' + +This may happen if you upgrade to 2025 Q1 from an older version. With 2025 Q1, a new [licensing mechanism]({%slug installing-license-key%}) was introduced, which requires you to reference the `Telerik.Licensing.Runtime` dll. + +## Solution + +To resolve the error, reference the `Telerik.Licensing.Runtime.dll` file in the project or install the `Telerik.Licensing` NuGet package. + +If you install the Telerik UI for WPF assemblies using NuGet packages, the `Telerik.Licensing` package is installed automatically and you should not see the beforementioned error. \ No newline at end of file diff --git a/licensing/license-agreement.md b/licensing/license-agreement.md deleted file mode 100644 index fc01c0f490..0000000000 --- a/licensing/license-agreement.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: License Agreement -page_title: License Agreement -description: End User License Agreement for Telerik UI for {{ site.framework_name }}. -slug: license-agreement -tags: license,agreement -published: True -position: 1 ---- - -# License Agreement - -__Telerik End-User License Agreement__ - -The End User License Agreement for Telerik UI for {% if site.site_name == 'Silverlight' %}Silverlight{% endif %}{% if site.site_name == 'WPF' %}WPF{% endif %} can be found on the following page: - -{% if site.site_name == 'Silverlight' %}[http://www.telerik.com/purchase/license-agreement/silverlight](http://www.telerik.com/purchase/license-agreement/silverlight-dlw-s).{% endif %} -{% if site.site_name == 'WPF' %}[http://www.telerik.com/purchase/license-agreement/wpf](http://www.telerik.com/purchase/license-agreement/wpf-dlw-s).{% endif %} diff --git a/licensing/license-file.md b/licensing/license-file.md deleted file mode 100644 index ccd9c81663..0000000000 --- a/licensing/license-file.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: License File -page_title: License File -description: The license .licx file is generated automatically since 2015. -slug: license-file -tags: license -published: True -position: 2 ---- - -# License File - -As of Q1 2015, the Telerik UI for WPF suite uses the standard .NET licensing mechanism, which means that using the controls in design-time may cause Visual Studio to add a [license.licx](https://docs.microsoft.com/en-us/dotnet/framework/tools/lc-exe-license-compiler) to the __Properties__ folder of the project. This file is used only in design-mode and is not needed for deployment explicitly. - -Having this license file is not expected to bring any performance/compilation issues and __you can ignore it__. - -In case your project __build fails__ with errors pointing to the license file, you can delete it and rebuild. - -If you are working under __source control__, once the file is created, it will be detected as a change by your source control system. We would suggest that you check-in this file initially. Then, when it is checked-out again during your work, it is up to you to decide whether to check it in, or discard the changes. diff --git a/licensing/personal-data-collection.md b/licensing/personal-data-collection.md deleted file mode 100644 index cbaf99bf67..0000000000 --- a/licensing/personal-data-collection.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Personal Data Collection -page_title: Personal Data Collection -description: This article provides information about the types of personal data that is collected. -slug: common-personal-data-collection -tags: personaldatacollection, gdpr -position: 4 ---- - -# Personal Data Collection - -## How personal data is used by Telerik Products - -Telerik UI for {{ site.framework_name }} uses your account details, email address and a product usage data to better understand customer experience allowing us to focus development efforts on the products and features that matter most to our customers. Additionally, this information may be used by Marketing and / or Sales to ensure you receive relevant content updates, product news and materials to ensure your success with our products. Please see our [Privacy Policy](https://www.progress.com/legal/privacy-center) for more details. - -This information is for our own purposes and do not sell or otherwise provide this information to any third-parties for a commercial purpose. - -## How I can see what data about me is stored? - -You can see the information stored for your account by sending request to us via the following form [GDPR Data Subject Access Rights Request](https://app.onetrust.com/app/#/webform/7897e80a-b8a4-4797-883a-bdacfe1ab8e4) - -## How I can delete the data stored about me? - -You can request deletion of the information stored for your account by sending request to us via the following form [GDPR Data Subject Access Rights Request](https://app.onetrust.com/app/#/webform/7897e80a-b8a4-4797-883a-bdacfe1ab8e4) diff --git a/licensing/protecting-telerik-assembly.md b/licensing/protecting-telerik-assembly.md index fa77b25d07..f103ed37af 100644 --- a/licensing/protecting-telerik-assembly.md +++ b/licensing/protecting-telerik-assembly.md @@ -12,8 +12,6 @@ position: 0 The Telerik UI for {{ site.framework_name }} suite includes a limited run-time royalty-free license to redistribute the controls in your own solutions subject to the License Agreement. You can use the components in the suite to build your own solutions and redistribute your solutions to your end users who are not required to purchase a license from Telerik to access your solution. -{% if site.framework_name == 'WPF' %} - ## Examples of Permitted Uses * WPF applications for internal company use. @@ -28,8 +26,6 @@ The Telerik UI for {{ site.framework_name }} suite includes a limited run-time r >important The next sections in this article describe how to include additional protection to the Telerik assemblies redistributed with your application when necessary. -{% endif %} - ## Protecting Telerik UI Assemblies Technical guidelines for protecting **Telerik UI for {{ site.framework_name }} by Progress** binaries when redistributed with other applications. diff --git a/upgrade/images/Common_Installing_AlreadyInstalled_WPF.png b/upgrade/images/Common_Installing_AlreadyInstalled_WPF.png deleted file mode 100644 index f78dc66612..0000000000 Binary files a/upgrade/images/Common_Installing_AlreadyInstalled_WPF.png and /dev/null differ diff --git a/upgrade/images/Common_Installing_NuGetUpdate_WPF.png b/upgrade/images/Common_Installing_NuGetUpdate_WPF.png deleted file mode 100644 index d86705dc00..0000000000 Binary files a/upgrade/images/Common_Installing_NuGetUpdate_WPF.png and /dev/null differ diff --git a/upgrade/images/Common_Installing_PreviousVersionInstalled_WPF.png b/upgrade/images/Common_Installing_PreviousVersionInstalled_WPF.png deleted file mode 100644 index a415ecdea0..0000000000 Binary files a/upgrade/images/Common_Installing_PreviousVersionInstalled_WPF.png and /dev/null differ diff --git a/upgrade/installation-upgrading-from-trial-to-developer-license-wpf.md b/upgrade/installation-upgrading-from-trial-to-developer-license-wpf.md index 65695b4449..4fde398ae8 100644 --- a/upgrade/installation-upgrading-from-trial-to-developer-license-wpf.md +++ b/upgrade/installation-upgrading-from-trial-to-developer-license-wpf.md @@ -1,7 +1,7 @@ --- -title: Upgrading Telerik UI Trial to Developer License or Newer Version -page_title: Upgrading Telerik UI Trial to Developer License or Newer Version -description: Check how you can upgrade your Trial assemblies to Telerik UI Developer License or Newer Version. +title: Upgrading Trial to Developer License or Newer Version +page_title: Upgrading Telerik UI Trial to Developer License +description: Check how you can upgrade your Trial assemblies to Telerik UI Developer License. slug: installation-upgrading-from-trial-to-developer-license-wpf tags: upgrading,telerik,ui,trial,to,telerik,ui,developer,license,or,newer,version published: True @@ -9,51 +9,37 @@ position: 0 site_name: WPF --- -# Upgrading Telerik UI Trial to Telerik UI Developer License or Newer Version - -This article will guide you through the process of upgrading your Telerik UI Trial to a Developer license or a newer version. - -## Automatic Upgrade to a Newer Version of UI for WPF - -To automatically upgrade to the newer version, you can utilize the __Progress Telerik UI for WPF Extension__ wizards. You can find more information in the respective articles: - -* [Latest Version Acquirer Tool]({%slug radcontrols-vs-extensions-project-latest-version-acquirer%}) - -* [Project Upgrade Wizard]({%slug radcontrols-for-wpf-vs-extensions-upgrading%}) - -## Upgrade to Newer Version or Other License of UI for WPF - -In order to manually upgrade your controls to a newer version of the suite, you need to perform the following steps: - -* Download the installation method you prefer: - - * [MSI file for automatic installation]({%slug installation-installing-from-msi-wpf%}) - - * [ZIP file for manual (advanced) installation]({%slug installation-installing-from-zip-wpf%}) - -* If the upgrade is major (i.e. from Q1 2024 to Q2 2024), check the [Release History](https://www.telerik.com/support/whats-new/wpf) to see if there are any major changes. You can also run the [API Analyzer Tool]({%slug upgrade-api-analyzer%}) to check for any breaking changes. - -* Back up your application. - -* Manually update the Telerik references in your Visual Studio project to point to the new DLLs or use the [References Resolver](https://marketplace.visualstudio.com/items?itemName=DeyanYosifov.ReferencesResolverExtension) extension to achieve this automatically. - -* Clean the solution. - -* Recompile your project. - -* Run the project. - -## MSI Installation - -If you have installed the trial version of UI for WPF and try to install the developer version of the same release, you will receive the following message: - -![Common Installing Already Installed WPF](images/Common_Installing_AlreadyInstalled_WPF.png) - -In this case, you need to remove the trial version first. - -Alternatively, if a previous version is detected, you will observe the following prompt: - -![Common Installing Already Installed WPF](images/Common_Installing_PreviousVersionInstalled_WPF.png) +# Upgrading Telerik UI for WPF Trial to Developer License + +This article describes how to upgrade your Telerik references from trial to developer version. + +To upgrade you will need to replace the Telerik dlls referenced in the project and setup a license key. This can happen using any of the available [installation approaches]({%slug installation-installing-which-file-do-i-need%}). + +1. Install the new version of the Telerik UI for WPF product. + + * If you use assembly references in the project, you can [use the .msi installer]({%slug installation-installing-from-msi-wpf%}) or the [.zip archive with the dlls]({%slug installation-installing-from-zip-wpf%}). You can find these on the [Telerik UI for WPF download page](https://www.telerik.com/account/product-download?product=RCWPF). + + * If you are [using NuGet packages]({%slug nuget-package-source-setup%}), you can replace the Telerik NuGet packages that ends with `.Trial` with the ones which doesn't contain the trial postfix. For example: + + #### __[XML] Trial NuGet package__ + {{region installation-upgrading-from-trial-to-developer-license-0}} + + + + {{endregion}} + + #### __[XML] Developer NuGet package__ + {{region installation-upgrading-from-trial-to-developer-license-1}} + + + + {{endregion}} + + * If you prefer to use the __Visual Studio Extension__, you can use the automatic [Upgrade Wizard]({%slug radcontrols-for-wpf-vs-extensions-upgrading%}) which will allow you to download the developer licensed dlls and also to install a license key. + +2. [Download and install a license key]({%slug installing-license-key%}) in the Telerik's folder in the AppData directory or in the project's folder. + +3. If you hit any errors related to missing Telerik references, make sure that all required Telerik dlls (for the used UI components) are referenced, and also that all referenced Telerik dlls use the same version (ex: 2025.1.212). Additionally, you can delete the `bin` and `obj` folders of the project, and then Clean and Rebuild the project, in order to ensure that any project cache is cleaned. ## Checking the Assemblies' Version @@ -61,21 +47,14 @@ To check what type of license the binaries you're using have, you can check the 1. Right click on the Telerik.Windows.Controls.dll file and select the __Properties__ options from the context menu. 2. Go to the __Details__ tab in the Properties window. -3. Check the __File description__ attribute. It will contain the **"Trial Version"** suffix if the dlls are Trial. Otherwise, there will be only the dll's name. +3. Check the __File description__ attribute. It will contain the **"Trial Version"** suffix if the dlls are trial. Otherwise, there will be only the dll's name. + +__Telerik.Windows.Controls.dll Properties__ -#### Figure 1: Telerik.Windows.Controls.dll Properties ![Telerik.Windows.Controls.dll Properties](images/Common_Installing_TrialVersionDescription_WPF.png) -If your dll files contain this suffix in the description then they are of the Trial version and you have to replace them with the licensed assemblies. - -## Updating NuGet Packages - -If you're using the Telerik NuGet packages, you can update them via the **NuGet Package Manager**: - -#### Figure 2: Updating NuGet Packages -![Updating NuGet Packages](images/Common_Installing_NuGetUpdate_WPF.png) - -If you're upgrading from a Trial version, you will need to first remove the packages with the **.Trial** suffix before installing the Development packages (which lack this suffix). Alternatively, you can edit the project file and remove the suffix from the NuGet **PackageReferences**. +If your dll files contain this suffix in the description then they are of the trial version and you have to replace them with the licensed assemblies. ## See Also + * [Controls Dependencies]({%slug installation-installing-controls-dependencies-wpf%}) diff --git a/urlrewriter.config b/urlrewriter.config index a134ff161d..3b8b7ae2d2 100644 --- a/urlrewriter.config +++ b/urlrewriter.config @@ -599,5 +599,8 @@ - + + + +