Convert to 12 or 13

Posted by: ecline on 21 March 2019, 2:18 pm EST

    • Post Options:
    • Link

    Posted 21 March 2019, 2:18 pm EST - Updated 30 September 2022, 8:47 am EST

    As part of our .Net upgrade, I’m upgrading all of our tools, including GrapeCity.

    I’ve changed my references in separate branches to try to upgrade to either 12 or 13 and am running into problems.

    Can I manually change the Licenses.licx? If so,where do I find my PublicKeyToken? My IT guy that handles licenses didn’t seem to know.

    If I go to Tools > Convert to 12 (or 13) I get the attached error

    We use LLBLGen for our entity framework and have recently upgraded to their v5.0 We’ve never had apackages.config file in the LLBL adapter file and we’ve upgraded GrapeCity prior with no problem.

    Please help me get through this as this is my last task to get our total update done. I’m stuck with errors on the License files that I can’t seem to figure out.

  • Posted 24 March 2019, 5:11 pm EST

    Hello,

    Can I manually change the Licenses.licx? If so,where do I find my PublicKeyToken?

    Yes, you can manually change the Licenses.licx file. You can refer to the “Required references in the licenses.licx file (for Standard and Professional Editions)” topic in the following documentation link to add license entry of AR13:

    https://help.grapecity.com/activereports/webhelp/AR13/webframe.html#arHOWLicensingActiveReports.html

    I get the attached error

    Could you please try after adding the blank “packages.config” in the same location.

    Also, please change the FW of your application to “4.5.2” or higher in case of AR12 and “4.6.2” or higher in case of AR13. As AR13 supports only 4.6.2 or higher .Net FW and AR12 supports only 4.5.2 or higher .Net FW.

    if the problem still exists, please feel free to revert.

    Thanks.

  • Posted 25 March 2019, 8:10 am EST

    I tried pasting inside the license file as told in the help page, but that didn’t help.

    
                            GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports
    GrapeCity.ActiveReports.PageReport, GrapeCity.ActiveReports
    GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win
    GrapeCity.ActiveReports.Viewer.Wpf.Viewer, GrapeCity.ActiveReports.Viewer.Wpf                                        
    
                        
    

    I noticed in another question that someone else posted their license code for v11 and it is the same as mine, so is the PublicKeyToken the same for everyone, and if so, what is it?

    I tried to adding a blank file to that location (there ended up being a few other blank files I had to end up adding also) and it finally made it through, but nothing happened.

    I just updated to the application to 4.7.2. Although, when I click on the Properties of my references, it is showing v4.0.30319, but it is grayed out and I am unable to change it. Is there a way to override that?

  • Posted 27 March 2019, 12:16 am EST

    Hello,

    PublicKeyToken is not necessary for the license file. You can add the license entry as follow:

    GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports.

    You are doing in the right way. Could you please elaborate on what problem are you facing now after adding the license entry.

    but it is grayed out and I am unable to change it. Is there a way to override that?

    This is the runtime version, you can’t change it. Please share the error that you are facing while compiling the application.

    Thanks.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels