Hi there, I am just trying to install the MVC 5 version from the private nuget feed. Everytime I try to install it, it freezes Visual Studio, any of them. I've tried in 2012, 2013, and 2015. Same thing always happens. When I check the project, the package installs the Scripts and the fonts folder, no editor templates or content.

The output says Installing Telerik.UI.xxx.MVC5xxx, adding package Telerik.UI.MVC5. Added package Telerik.UI.MVC5, and that's where it freezes.

I cannot use the telerik template creators because I want to add kendo UI to my existing projects. Nuget package is the best way. I tried downloading the nuget package too and installing it that way, still same freeze. What is going on? Thanks.

Well I should comment that it did actually finally work in 2015, only after letting Visual Studio sit there for 45 minutes did it finally unfreeze with all the stuff properly loaded, seems like the hangup is the content folder. But why does it take such a long time? That's like not usable. Every project I want to add this in I should wait 45 minutes???

Hi Andrew,

We are sorry for the inconvenience.

The NuGet package upgrade should not take more than a few minutes. The source control system however may have a significant performance impact over the NuGet client speed which is not under our control. What kind of source control system do you use? Could you please turn off the source control integration and give it another try?

Regards,
Vesko
Telerik

Hi Vesko,

I'm having the same problem as Andrew, it takes over 30 min to install or uninstall Telerik.UI.for.AspNet.MVC4 v 2016.2.607 on VS 2015.

Could you please elaborate on how/why source control impacts the nuget performance (we use git and svn)? Why we don't have this kind of issue with any other nuget packages? Is there a workaround for this issue?

Thanks,

Victor

Hi guys,

I found that the significant slow down is caused by JavaScript files synchronization most probably. Telerik UI for ASP.NET MVC 5 package deploys a lot of script files that by default are synchronized during the package deployment.

I suggest to turn off the JavaScript references auto-sync. Here is how to do that:

1. Right-click _references.js and uncheck Auto-sync JavaScript References.
2. Install the NuGet package.
3. Right-click _references.js and click on Update JavaScript References.

Regards,
Vesko
Telerik by Progress

Vesko said:Hi guys,

I found that the significant slow down is caused by JavaScript files synchronization most probably. Telerik UI for ASP.NET MVC 5 package deploys a lot of script files that by default are synchronized during the package deployment.

I suggest to turn off the JavaScript references auto-sync. Here is how to do that:

1. Right-click _references.js and uncheck Auto-sync JavaScript References.
2. Install the NuGet package.
3. Right-click _references.js and click on Update JavaScript References.

Regards,
Vesko
Telerik by Progress

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items

How does this work in VS 2017? The option doesn't seem to be there. At the moment, on my absolute beast of a machine, attempting to update crashes VS every single time. It seems to be the network portion of TFS that is doing this.

Hi Kori,

The option mentioned is indeed not available in VS2017, however you could still disable the auto-sync when upgrading a project. To do that open the _references.js file in the project and modify the following line /// <autosync enabled="true" />. 

Another thing which could improve the upgrade speed is disconnecting the project from source control while running the Upgrade Wizard.

Please try that out and let us know if it worked our for you. I am looking forward to your reply.

Regards,
Nikola
Progress Telerik

The main question is why JavaScript files are in nuget package? This is the way providers are trying to avoid. We have now bower, nodejs and having javascript in nuget is pain. There is no control over it. It copies files not used. If  sombody only using .all version.

Shouldn't at least be 2 different nuget packages? one with JS and one without?

 

Hello,

Initially NuGet 3 did not support content files in packages. This seems to have changed since then and we'll review if it's possible to include the scripts in such manner.

Regards,
T. Tsonev
Progress Telerik

Hello

Even with that, I would like to avoid having any content without control.

For content I'm using npm. and only for js. For css I'm using "less" sources because that gives the best way to adjustment.

And often cdn

Kind Regards

Marcin

Hello Marcin,

Thank you for the suggestions.

I will forward them to the relevant team for consideration.

Regards,
Stefan
Progress Telerik

It would be nice if this was noted in the Getting Started documentation here: https://docs.telerik.com/aspnet-mvc/getting-started/nuget-install.

I've been sitting here waiting for the trial package to install for 30 minutes and it's still going.Usually installing a nuget package takes about 6 seconds. It has also gotten two errors stating "Collection was modified; enumeration operation may not execute" so far. No idea what that's referring to or if the package installation is now corrupted. By the way, is installing the Telerik.UI.for.AspNet.Mvc5.Trial nuget package even required if I already downloaded and installed Progress Telerik UI for ASP.NET MVC R3 2017 SP2?

Hello, Jesse,

Thank you for the suggestion, we will discuss this specific and document it for future reference.

As for the errors, please check if they still occur after using the suggested approach.

If the installation for Telerik UI for ASP.NET MVC R3 2017 SP2 is already installed the Nuget is not needed, as all of the needed files are available. Please check the following article:

https://docs.telerik.com/aspnet-mvc/introduction#installation

Regards,
Stefan
Progress Telerik

Thanks Stefan. I'm glad there is the alternative of the installation. It looks like Visual Studio 2017 does not use a _references.js file anymore so that option was out. I ended up just killing the Visual Studio process and undoing my changes and using the installed files after I found that article.