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: I set <AspnetCompileMergeIntermediateOutputPath>D:\PublishFiles</AspnetCompileMergeIntermediateOutputPath> in the publish profile. The destination for the published files was still set as F:\Manzen.Net4 The publish failed with the same error message as per the original post. I then tried the setting <IntermediateOutputPath>D:\PublishFiles</IntermediateOutputPath> and saw some strange activity When I published the site the following folders (& subfolders ---->) were created under D:\PublishFiles:- AspnetCompileMerge ---->Source (Contains all the source files) ---->TempBuildDir (Looks like the published web site) Package ---->PackageTmp (Looks like the published web site) ProfileTransformWebConfig ---->transformed (empty) TransformWebConfig ---->transformed (empty) The attached file was also created in the D:\PublishFiles folder Nothing was published into F:\Manzen.Net4 So I now have the situation where something is published to an intermediate folder but not to the final destination.
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: I set <AspnetCompileMergeIntermediateOutputPath>D:\PublishFiles</AspnetCompileMergeIntermediateOutputPath> in the publish profile. The destination for the published files was still set as F:\Manzen.Net4 The publish failed with the same error message as per the original post. I then tried the setting <IntermediateOutputPath>D:\PublishFiles</IntermediateOutputPath> and saw some strange activity When I published the site the following folders (& subfolders ---->) were created under D:\PublishFiles:- AspnetCompileMerge ---->Source (Contains all the source files) ---->TempBuildDir (Looks like the published web site) Package ---->PackageTmp (Looks like the published web site) ProfileTransformWebConfig ---->transformed (empty) TransformWebConfig ---->transformed (empty) The attached file was also created in the D:\PublishFiles folder Nothing was published into F:\Manzen.Net4 So I now have the situation where something is published to an intermediate folder but not to the final destination.