The new v7.1213 seems to bring in so many dependencies, which has bloated the size of a simple (no touch) deployment by about 4MB.
Surely there is a way to only include the Windows Azure dependencies if they are actually desired. At the moment the Nuget package seems to bring in everything.. which is
AjaxControlToolkit (cool, this is needed obviously)
HtmlAgilityPack (yep, for the white-list parser)
Microsoft Ajax Minifier (ok..)
JSON.Net (ok...)
Windows Azure Storage (I don't want this..)
Windows Azure Configuration Manager (I really don't want this..)
ODataLib (getting annoying...)
WCF Data Services Client (I don't use OData so this is pointless)
EdmLib (getting super annoying now..)
System.Spatial (seriously??)
Why bundle in so much Azure stuff when most people won't really need it?
Perhaps splitting this into two packages, an AjaxControlToolkit Basic, and an AjaxControlToolkit Azure
Comments: I just used Nuget to get the AjaxControlToolKit and that is the version it stuck me with. It took about 5 minutes for it to load all that unwanted crap into my project. All I wanted was the AjaxControlToolKit that has existed without that crap for years. This is simply Microsoft's way of trying to shoehorn Azure into everything as they try to force developers to make everything depend on Azure so microsoft can add monthly revenue streams. There was no excuse for it to be in the AjaxControlToolKit.
Surely there is a way to only include the Windows Azure dependencies if they are actually desired. At the moment the Nuget package seems to bring in everything.. which is
AjaxControlToolkit (cool, this is needed obviously)
HtmlAgilityPack (yep, for the white-list parser)
Microsoft Ajax Minifier (ok..)
JSON.Net (ok...)
Windows Azure Storage (I don't want this..)
Windows Azure Configuration Manager (I really don't want this..)
ODataLib (getting annoying...)
WCF Data Services Client (I don't use OData so this is pointless)
EdmLib (getting super annoying now..)
System.Spatial (seriously??)
Why bundle in so much Azure stuff when most people won't really need it?
Perhaps splitting this into two packages, an AjaxControlToolkit Basic, and an AjaxControlToolkit Azure
Comments: I just used Nuget to get the AjaxControlToolKit and that is the version it stuck me with. It took about 5 minutes for it to load all that unwanted crap into my project. All I wanted was the AjaxControlToolKit that has existed without that crap for years. This is simply Microsoft's way of trying to shoehorn Azure into everything as they try to force developers to make everything depend on Azure so microsoft can add monthly revenue streams. There was no excuse for it to be in the AjaxControlToolKit.