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: Your publishing log differs from mine. Particularly, my Scripts folder publishing log looks like this: ``` 1>Publishing folder Scripts... 1>Publishing folder Scripts/AjaxControlToolkit... 1>Publishing folder Scripts/AjaxControlToolkit/Debug... 1>Publishing folder Scripts/AjaxControlToolkit/Release... 1>Web App was published successfully file:///D:/TestPublish ``` As you can see, there is no "packages" folder. It seems that your NuGet packages folder is inside the site's root folder, so all package contents are going to be published. This can be caused by the solution file located inside the project's folder, so NuGet packages are stored inside this folder as well. Please try the following steps: 1. Create a new solution and save the solution file one level above the folder of the project. 2. Add an existing project to the solution. 3. Add (or restore) all NuGet packages that were included in the project. 4. Try to publish it. Please let me know if this helped you.
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: Your publishing log differs from mine. Particularly, my Scripts folder publishing log looks like this: ``` 1>Publishing folder Scripts... 1>Publishing folder Scripts/AjaxControlToolkit... 1>Publishing folder Scripts/AjaxControlToolkit/Debug... 1>Publishing folder Scripts/AjaxControlToolkit/Release... 1>Web App was published successfully file:///D:/TestPublish ``` As you can see, there is no "packages" folder. It seems that your NuGet packages folder is inside the site's root folder, so all package contents are going to be published. This can be caused by the solution file located inside the project's folder, so NuGet packages are stored inside this folder as well. Please try the following steps: 1. Create a new solution and save the solution file one level above the folder of the project. 2. Add an existing project to the solution. 3. Add (or restore) all NuGet packages that were included in the project. 4. Try to publish it. Please let me know if this helped you.