Skip to main content
BuyLog In
General Information
Search in…
Docs > Development: Register Your License > Troubleshooting - Remove the Trial Version Message
All docs
V26.1
    • General Information
    Support Services
    Install DevExpress Products: Overview
    Install .NET Products: Unified Component Installer
    Install .NET Products: NuGet.org
    Development: Register Your License
    License Key for DevExpress Products
    Use DevExpress Products in CI/CD Systems
    Convert a Trial Version to a Licensed Version (.NET)
    Troubleshooting - Remove the Trial Version Message
    Install Updates
    Security Information
    AI Coding Assistant & Documentation
    Localization
    Frequently Asked Support Questions
    DevExpress EULAs
    DevExpress Trademarks
    Download CHM

    Troubleshooting - Remove the Trial Version Message

    • 4 minutes to read

    Note

    After you purchased a license, register your products as described in this help topic: Convert a Trial Version to a Licensed Version (.NET).

    If your .NET project continues to display a trial message, use the troubleshooting guide below.

    Common Steps

    The following steps help you clear up any IDE or NuGet cache that may include outdated licensing information.

    • Close your IDE.
    • Update your license key.
      • If you use our Unified Component Installer: run the setup wizard in Modify mode, and login with your DevExpress.com credentials. The wizard updates your license key automatically.
      • If you use other installation methods: download your up-to-date DevExpress license key from the DevExpress Download Manager and paste it to the corresponding text file or environment variable. See the following help topic for additional information: License Key for DevExpress Products.
    • Delete bin and obj folders and clear NuGet cache (see Clearing local folders).
    • Reboot your machine (avoid possible project binary locks and re-initialization issues in your IDE and other apps).
    • Open your IDE and rebuild your projects.

    For versions older than v16.1.12 and v16.2.7, the issue can occur if your machine has the FIPS algorithm policy enforced:

    Show the solution

    If you develop with an older DevExpress build and the use of FIPS Algorithm Policy at the OS level is required, you can disable FIPS Algorithm Policy only for Visual Studio. Include the following code in your Visual Studio’s devenv.exe.config file located in the Visual Studio’s .*\Common7\IDE subfolder. This action does not affect the information security on your computer, but allows the project to use the standard licensing mechanism utilized in our libraries:

    <configuration>  
  <runtime>  
    <enforceFIPSPolicy enabled="0" />  
  </runtime>  
</configuration>

    Alternatively, you can proceed at the application level and modify the enforceFIPSPolicy token similarly in the application’s configuration file. For more information, refer to the following article: <enforceFIPSPolicy> Element.

    You can also install a later version in which this problem was solved: 16.1.12+ and 16.2.7+.

    ASP.NET Web Forms and MVC

    For ASP.NET Web Forms and MVC applications, you can also clear “Temporary ASP.NET Files” directories. Use the DevExpress Temporary ASP.NET Files Clearer to clear the following “Temporary ASP.NET Files” directories (you can also clear these directories manually):

    • C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
    • C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\
    • C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\
    • C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\
    • C:\Users\[your_user_name]\AppData\Local\Temp\Temporary ASP.NET Files\

    Follow these guides for details:

    WinForms

    You can find information on most common issues that may occur after you migrate to a newer version of DevExpress products here: DevExpress WinForms Troubleshooting - Upgrade Projects.

    ASP.NET Core and MVC 5

    If you use DevExtreme components for ASP.NET Core or ASP.NET MVC 5 and see a trial message at the top of the application window, try the following solutions.

    Check Your DevExpress License Key Registration

    Symptoms:

    Solution:

    Update DevExtreme Public Key Registration Code

    Symptoms:

    • A W0019, W0020, or W0021 warning appears in the browser console.
    • Trial message links open js.devexpress.com. The message lists “DevExtreme Complete“ in the subscription.

    Solutions:

    • If you use both Razor and jQuery/JavaScript, render Razor-based components first.
    • Configure the DevExtreme license key. Use the devextreme-license CLI command to generate the DevExtreme runtime key file (devextreme-license.js), and load scripts in this order:
      1. jQuery scripts
      2. dx.all.js
      3. Generated devextreme-license.js
      4. Scripts with DevExtreme components
    • Use Razor syntax instead of jQuery or JavaScript.
    See Also