Welcome to the Xceed Community | Help
Community Search  

Deploying a DotNet Application using XceedCry.dll

Sort Posts: Previous Next
  •  06-11-2007, 6:50 AM Post no. 6177

    Deploying a DotNet Application using XceedCry.dll

    Our application is developed using Visual Studio 2005 and uses XceedCry.dll as an interop control. We use the RSA encryption class. If we build the application on our development machine, and generate a random key pair, it works fine.

    We then create a setup project to deploy the application and install it on another machine. When we run the DotNet application and try to generate the random key pair we get the exception:

    ************** Exception Text **************
    System.Runtime.InteropServices.COMException (0x80045001): The license key required to use Xceed Encryption Library was not found or is invalid. Make sure that you have called the License method with a valid license key as described in the documentation.

    The license key we load is valid and a test VB6 program that does the same thing works fine on the same machine.

    If we run the Exceed Ultimate Suite installation on the test machine and install the Xceed Encryption module, then the DotNet program works!

    What else, besides XCeedCry.dll and Interop.XceedEncryptionLib.dll do we have to install on the test machine to get a DotNet application working.
  •  06-11-2007, 2:32 PM Post no. 6178 in reply to 6177

    Re: Deploying a DotNet Application using XceedCry.dll

    Two questions. First, do you set the key in code, through the License method (and if so, when do you set it)? Second, are you deploying on Vista?

    André
    Software Developer and Tech Support
    Xceed Software Inc.
  •  09-10-2007, 2:59 PM Post no. 6179 in reply to 6178

    Re: Deploying a DotNet Application using XceedCry.dll

    I am running into the same problem with this control. I have also built an application using VS 2005 and built my setup program with VS 2005. I am calling the License method at the start of any routine where I am using this component.

    -Dave
  •  09-13-2007, 12:47 PM Post no. 6180 in reply to 6179

    Re: Deploying a DotNet Application using XceedCry.dll

    This problem is related to the .dll not being registered on the deployment machine.

    e.g.,
    Start -- Go to run -- Type in : Regsvr32 "path of the XceedCry.dll".
    Charles Bérubé-Rémillard
    Technical Support
    Xceed Software Inc.
  •  09-13-2007, 2:40 PM Post no. 6181 in reply to 6180

    Re: Deploying a DotNet Application using XceedCry.dll

    Actually, it is getting registered. I even registered the XceedCry.dll file manually to make sure.
    What I ended up doing was creating a ActiveX dll that wrapped the functionality that I needed from this component and referenced that from my .NET app. It seems to be working now.

    -Dave
View as RSS news feed in XML
Contact | Site Map | Reviews | Legal Terms of Use | Trademarks | Privacy Statement Copyright 2008 Xceed Software Inc.