Is Control Panel dead?

[improwise]

Like most things with Telerik these days, the progress control panel is quite confusing? Is it dead and not supposed to be used? If not, why isn't it on the download page? And if it is dead, are we actually supposed to add necessary NPM source manually?

 

What is the recommended way to install and maintain Telerik products and configuration?

[Nikola]

Hi Patrik,

The Progress Control Panel is still actively developed and you could download it through the Overview page in Your Account (see attached image).  

The Progress Control Panel was never able to manage and register NPM feeds. There are several products listed that are distributed through NPM, but they were never installed through the Control Panel. 

You could use the application to install and manage installations of products distributed as windows installers and also through the Control Panel you can register the Telerik private NuGet feed to install and manage packages for products that distribute such. 

If you could share more details as to what do you find confusing about the Progress Control Panel we could provide clarification. I am looking forward to your reply.

Regards,
Nikola
Progress Telerik

[improwise]

Hi,

A bit strange to have an important download that isn't listed under "Downloads" where one would naturally look for it.

Not sure what you mean with the Control Panel not being able to manage and register NPM feeds when it does infact handle the Telerik Nuget which you have to add manually if not (at least the installer for Blazor componentes did not seem to offer this possibility)? What is the advantage of not using the Progress Control Panel? 

 

The Telerik private nuget is also problematic when you want to install other NuGet packages (like ABP), but perhaps that is as much Microsofts fault as yours. 

 

 

[Nikola]

Hi Patrik,

NPM is more commonly used when referring to the Node Package Manager rather than the NuGet one and therefore provided the information that we do not manage NPM feeds. Currently, NuGet feeds are registered only through the Progress Control Panel and the individual products' offline (msi) installers do not offer this feature. 

Some VS Extensions like the ones for Telerik UI for ASP.NET Core or Telerik UI for Blazor register local NuGet feeds,  but these are at a project level and not in the global config like when using the control panel. 

The Progress Control Panel's purpose is to ease multiple product installations and updates and to assist in managing existing installations. That said there is no real advantage of not using it, rather the contrary.

So far we have not received any complaints that our private feed affects other NuGet feeds and package installations, so would you please elaborate more on what issues you are facing.

Regards,

Nikola

[improwise]

Hi,

I can see the confusion here regarding the meaning of NPM. It seems then that the Contorl Panel is alive and kicking, and is probably the best option for most users. I would recommend that you actually make it visible on the Download page as that would be the natural place to look for downloads for obvious reasons.

Regading problems with other packages etc. you can read more about it here:

https://support.abp.io/QA/Questions/1270/Cannot-install-latest-Abp-suite

https://github.com/abpframework/abp/issues/2003

https://support.abp.io/QA/Questions/1270/Cannot-install-latest-Abp-suite

etc.

I would imagine that this isn't an ABP problem and that the same problem could occur with products/tools as well.

Thanks.

[Nikola]

Hi Patrik,

Thank you for your suggestion. I would forward it to the team responsible for managing the Your Account page. 

The NuGet installation issues seem to be caused by the fact that all sources are used when trying to install a package through the dotnet CLI. In the GitHub issue, someone mentioned the --ignore-failed-sources option which I would suggest too. Another way would be to disable the Telerik private feed through Visual Studio (Tools > NuGet Package Manager > Package Manager Settings > Package Sources ) but you will have to enable it again when you want to update the Telerik packages, which would be a bit more work.  

In case you have any other questions do not hesitate to get back to us.

Regards,

Nikola.