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

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

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.

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

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.

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

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.

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