In an attempt at improving the performance of our website application I have installed the AjaxControlToolkit Static Resources via Visual Studio 2013's Manage NuGet Packages feature.
I undertook all the manual steps required as stated [here](https://ajaxcontroltoolkit.codeplex.com/wikipage?title=How%20to%20use%20bundling%20and%20CDN)
Prior to the installation of the AjaxControlToolkit Static Resources I had no issues publishing the site using File System as the publishing method.
Now the site cannot be published as the following error is obtained:-
Copying file packages\AjaxControlToolkit.StaticResources.15.1.4.0\Content\Content\AjaxControlToolkit\Styles\HtmlEditor.Popups.AttachedTemplatePopup.min.css to C:\Users\mynamehere.ourdomain\AppData\Local\Temp\WebSitePublish\ManzenTrunk-1877587068\obj\Debug\AspnetCompileMerge\Source\packages\AjaxControlToolkit.StaticResources.15.1.4.0\Content\Content\AjaxControlToolkit\Styles\HtmlEditor.Popups.AttachedTemplatePopup.min.css failed. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
The issue is obviously associated with the introduction of AjaxControlToolkit Static Resources as publishing was fine until the feature was added.
Any help/advice/fixes would be appreciated
Comments: Tried adding a backslash to make the <AspnetCompileMergeIntermediateOutputPath> work but it has had no effect and still got the error message. Neither has shortening the temp & tmp variables to just c:\temp had any effect. However when I have <IntermediateOutputPath>D:\PublishFiles\</IntermediateOutputPath> in the publish profile I do get some but not all folders published to the intended destination of F:\Manzen.Net4. Any folder that should have been published which is alphabetically after 'packages' doesn't get published to F:\Manzen.Net4 BUT IS present in D:\PublishFiles\Package\PackageTmp I still get the message 'Web App was published successfully file:///f:/Manzen.Net4' but with 15 folders missing (the ones alphabetically after 'packages') it obviously hasn't!
I undertook all the manual steps required as stated [here](https://ajaxcontroltoolkit.codeplex.com/wikipage?title=How%20to%20use%20bundling%20and%20CDN)
Prior to the installation of the AjaxControlToolkit Static Resources I had no issues publishing the site using File System as the publishing method.
Now the site cannot be published as the following error is obtained:-
Copying file packages\AjaxControlToolkit.StaticResources.15.1.4.0\Content\Content\AjaxControlToolkit\Styles\HtmlEditor.Popups.AttachedTemplatePopup.min.css to C:\Users\mynamehere.ourdomain\AppData\Local\Temp\WebSitePublish\ManzenTrunk-1877587068\obj\Debug\AspnetCompileMerge\Source\packages\AjaxControlToolkit.StaticResources.15.1.4.0\Content\Content\AjaxControlToolkit\Styles\HtmlEditor.Popups.AttachedTemplatePopup.min.css failed. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
The issue is obviously associated with the introduction of AjaxControlToolkit Static Resources as publishing was fine until the feature was added.
Any help/advice/fixes would be appreciated
Comments: Tried adding a backslash to make the <AspnetCompileMergeIntermediateOutputPath> work but it has had no effect and still got the error message. Neither has shortening the temp & tmp variables to just c:\temp had any effect. However when I have <IntermediateOutputPath>D:\PublishFiles\</IntermediateOutputPath> in the publish profile I do get some but not all folders published to the intended destination of F:\Manzen.Net4. Any folder that should have been published which is alphabetically after 'packages' doesn't get published to F:\Manzen.Net4 BUT IS present in D:\PublishFiles\Package\PackageTmp I still get the message 'Web App was published successfully file:///f:/Manzen.Net4' but with 15 folders missing (the ones alphabetically after 'packages') it obviously hasn't!