update takes forever

8 posts, 0 answers
  1. Maurice
    Maurice avatar
    36 posts
    Member since:
    Jan 2016

    Posted 14 Mar 2017 Link to this post

    Hi,

    I have a project and the upgrade wizard for going to a newer version of Telerik takes forever to complete (>18 hours).

    Is there a logfile to check why it takes so long?

    Is it possible to upgrade a project by hand?

    Maurice

  2. Momchil
    Admin
    Momchil avatar
    84 posts

    Posted 15 Mar 2017 Link to this post

    Hello Maurice,

    Usually the upgrade is slow when Global Resources are added to the project and the auto-sync option is enabled in project's _references.js file.

    I would suggest if possible to use the CDN support that we provide. You could follow these steps to do this:
    1. Select your project in Solution Explorer and in the menu select Telerik -> UI for ASP.NET MVC -> Configure project
    2. On the Project Settings page check the Use CDN Support check box and click the Finish button

    Enabling CDN support will remove the kendo resources folders located under the Content and Scripts folders of your project and will greatly improve the speed of the update.

    If you don't want or can't use the CDN you can disable the _references.js auto-sync option before running the upgrade.

    You could also update the project manually by following these steps:
    1. Update the project's Kendo.Mvc.dll reference with the one from the new version. It's located in "[NewVersionInstallLocation]\wrappers\aspnetmvc\Binaries\[ProjectTargetMVCVersion]" folder.
    2. Update UI for ASP.NET MVC scripts by replacing the "Scripts\kendo\[OldVersion]" folder in your project with "Scripts\kendo\[NewVersion]" folder and place inside the contents of the "[NewVersionInstallLocation]\js\" directory.
    3. Update the content by replacing the "Content\kendo\[OldVersion]" folder in your project with "Content\kendo\[NewVersion]" folder and place inside the contents of the "[NewVersionInstallLocation]\styles\" directory.
    4. Update editor templates by replacing the "Views\Shared\EditorTemplates" folder in your project with the contents of the "[NewVersionInstallLocation]\wrappers\aspnetmvc\EditorTemplates\razor" directory.
    5. Finally update the references to Kendo scripts and content at the beginning of the _Layout.cshtml file by replacing the old version in the references' path with the new one. These references point to some of the scripts and content in the folders you updated in steps 2 and 3 so the path should be updated accordingly.

    Please let us know if you need further assistance.

    Regards,
    Momchil
    Telerik by Progress
    Try our brand new, jQuery-free Angular 2 components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  3. Gordon
    Gordon avatar
    5 posts
    Member since:
    Dec 2014

    Posted 31 Jan 2018 in reply to Momchil Link to this post

    Ok, but Is it save to Kill this insane process after it has been running for several hours.

     

  4. Momchil
    Admin
    Momchil avatar
    84 posts

    Posted 01 Feb 2018 Link to this post

    Hi Gordon,

    If you kill the process, the project might end up partially updated but subsequent successful run of the Upgrade wizard should restore missing files. Please open a support ticket if you need assistance with the upgrade.

    Regards,
    Momchil
    Progress Telerik
    Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  5. Stefan
    Stefan avatar
    21 posts
    Member since:
    May 2018

    Posted 26 Jun 2020 in reply to Momchil Link to this post

    Hello,

    we're also having trouble upgrading our projects when using the Upgrade Wizard.

    Do the steps described for doing a manual upgrade still apply?

    In Step 1. of that process, do the language specific folders in that folder not have to be replaced?

     

    Kind regards.

  6. Vesko
    Admin
    Vesko avatar
    168 posts

    Posted 29 Jun 2020 Link to this post

    Hello Stefan,

    Yes, the steps are still valid and can be applied.

    The language specific folders contain satellite resource assemblies which conforms with the standard localization mechanism provided by the .NET Framework to build multi-language applications. If you build a multi-language application, these language specific folders have to be in the bin folder. Have in mind that you don't have to reference any of these resource assemblies in your application. You only have to reference the correct version of Kendo.Mvc.dll. When you build in Visual Studio, all the sub-folders are copied to the bin folder automatically.

    Here is an article about Telerik UI for ASP.NET MVC localization that may be useful.

    Regards,
    Vesko
    Progress Telerik

    Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
    Our thoughts here at Progress are with those affected by the outbreak.
  7. Stefan
    Stefan avatar
    21 posts
    Member since:
    May 2018

    Posted 01 Jul 2020 in reply to Vesko Link to this post

    Hello Vesko,

    thank you for the clarification.

    Besides the Kendo.Mvc.dll we noticed different other dlls referenced in out project, like Kendo.Mvc.Export.dll, Telerik.Documents.SpreadsheetStreaming, and so on.

    I assume that we have to also swap them with the newer versions?

    Kind regards.

     

  8. Vesko
    Admin
    Vesko avatar
    168 posts

    Posted 01 Jul 2020 Link to this post

    Hi Stefan,

    Yes, you are absolutely right.

    In addition, I can recommend using the Telerik NuGet feed to obtain the latest versions of our product assemblies. You can use it in conjunction with the CDN as an alternative to the Progress Control Panel, the product installers or the zip packages.

    The Telerik Private NuGet Feed

    Progress Control Panel Now Automatically Creates a Telerik NuGet Package Source

     

    Regards,
    Vesko
    Progress Telerik

    Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
    Our thoughts here at Progress are with those affected by the outbreak.
Back to Top