Completed
Last Updated: 28 Sep 2015 07:48 by Niklas Boström
Jerome
Created on: 06 Jun 2013 03:00
Category: UI for ASP.NET AJAX
Type: Feature Request
4
nuget
The NuGet packages should not install directories into the project. If these directories are not needed when referencing the dlls traditionally, I can't see why they are needed with the Nuget package. Adding nuget references to ASP.Net AJAX in a non-website/application project results in a silly set of directories. Like, if you want to write a plain assembly that simply uses the Telerik controls in a Server Control.

An install.pl file should handle any web.config alteration on install.

The 
(Total attached files size should be smaller than 20mb. Allowed extensions: .zip, .rar, .jpg, .png, .gif)
3 comments
Niklas Boström
Posted on: 14 Jul 2015 09:08
Hi, as I understand the folders are updated on package update so it's not even possible to use them to customize (and not loose the customization on package update).

For our purposes it would work to add files in those directories if not already there but I understand the guys not wanting any folders added.

Thanks, Niklas
ADMIN
Rumen
Posted on: 14 May 2014 13:53
Hi guys,

Thank you for your sharing your constructive feedback with us.

Indeed, currently the UI.for.Asp.Net.Ajax.Trial.20xx.x.xxx.nupkg packages contain two folders meant for the Editor and Image Editor dialogs customization: http://screencast.com/t/9RD9IdRSIq. 

I agree that it could be inconvenient for the developers who do not won't to customize the dialogs to delete these folders after each upgrade. 

In regards to this I kindly invite all users that do not like the current nuget package structure to like this Feedback Portal item so that we can raise its priority and implement separate nuget packages for the dialogs' folders.

Best regards,
Rumen
Denis
Posted on: 08 Aug 2013 17:28
I second that. This is important feature. This is a real pain to manually clean up the big project after AUTOMATIC(!) update all references via Nuget.
Please implement it or provide a special Nuget package which doesn't add anything to the target project nor change the web.config.