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: There is an easier way to move a solution file: 1. Open the website in Visual Studio (File -> Open -> Web Site...). 2. Once you opened it, you can hit Ctrl+S and Visual Studio will prompt you to save the solution file. Choose a folder outside the website root folder and save the file. 3. After that, you can move the "packages" folder right beside the solution file. Then, you need to modify the "repositories.config" file inside "packages". It points to "packages.config" files that contain a list of NuGet packages for a particular project. You will need to add something like "Manzen.Net4" at the beginning of each path. If you lose something with that method, you can try to implement the way you described. It seems to be a correct approach to move the solution file, but you need to restore all packages as the NuGet package manager will lose references to it.
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: There is an easier way to move a solution file: 1. Open the website in Visual Studio (File -> Open -> Web Site...). 2. Once you opened it, you can hit Ctrl+S and Visual Studio will prompt you to save the solution file. Choose a folder outside the website root folder and save the file. 3. After that, you can move the "packages" folder right beside the solution file. Then, you need to modify the "repositories.config" file inside "packages". It points to "packages.config" files that contain a list of NuGet packages for a particular project. You will need to add something like "Manzen.Net4" at the beginning of each path. If you lose something with that method, you can try to implement the way you described. It seems to be a correct approach to move the solution file, but you need to restore all packages as the NuGet package manager will lose references to it.