初试ASP.NET5 & MVC6 发布错误

<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">  <PropertyGroup>    <PublishOutputPathNoTrailingSlash>C:\Temp\Publish</PublishOutputPathNoTrailingSlash>  </PropertyGroup></Project>

今天安装了VS2015，并且下载了ASP.NET5 RC1的安装包，简单实验了一下。文件结构确实和以前版本有很大的改变，期待ASP.NET Core的发布。说说今天碰到了一个问题，在生成默认项目和运行默认项目的时候都没有出现问题，而在发布的时候我选择了文件系统的发布，出现了如下的错误信息

Microsoft .NET Development Utility Clr-x86-1.0.0-rc1-16231Executing script 'prepublish' in project.jsonnpm WARN package.json ASP.NET@0.0.0 No descriptionnpm WARN package.json ASP.NET@0.0.0 No repository field.npm WARN package.json ASP.NET@0.0.0 No README datanpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\defaults requires clone@'~0.1.5' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\clone,npm WARN unmet dependency which is version 0.2.0npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\findup-sync requires glob@'~4.3.0' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\glob,npm WARN unmet dependency which is version 4.5.0npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\globule requires glob@'~3.1.21' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\glob,npm WARN unmet dependency which is version 4.5.0npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\globule requires minimatch@'~0.2.11' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\minimatch,npm WARN unmet dependency which is version 2.0.1npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\mkdirp requires minimist@'0.0.8' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\minimist,npm WARN unmet dependency which is version 1.1.0npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\through2 requires readable-stream@'>=1.0.33-1 <1.1.0-0' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp\node_modules\readable-stream,npm WARN unmet dependency which is version 1.1.13npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-concat\node_modules\through2 requires readable-stream@'>=1.0.33-1 <1.1.0-0' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-concat\node_modules\readable-stream,npm WARN unmet dependency which is version 1.1.13npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-cssmin\node_modules\gulp-util requires minimist@'^0.2.0' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-cssmin\node_modules\minimist,npm WARN unmet dependency which is version 1.1.1npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-cssmin\node_modules\through2 requires readable-stream@'~1.0.17' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-cssmin\node_modules\readable-stream,npm WARN unmet dependency which is version 1.1.13npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-uglify\node_modules\through2 requires readable-stream@'>=1.0.33-1 <1.1.0-0' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-uglify\node_modules\readable-stream,npm WARN unmet dependency which is version 1.1.13npm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-uglify\node_modules\uglify-js requires source-map@'0.1.34' but will loadnpm WARN unmet dependency E:\项目\KitFramework\src\KitFramework\node_modules\gulp-uglify\node_modules\source-map,npm WARN unmet dependency which is version 0.1.43[20:55:36] Using gulpfile E:\项目\KitFramework\src\KitFramework\gulpfile.js[20:55:36] Starting 'clean:js'...[20:55:36] Starting 'clean:css'...[20:55:36] Finished 'clean:js' after 2.25 ms[20:55:36] Finished 'clean:css' after 3.11 ms[20:55:36] Starting 'clean'...[20:55:36] Finished 'clean' after 4.78 μs[20:55:37] Using gulpfile E:\项目\KitFramework\src\KitFramework\gulpfile.js[20:55:37] Starting 'min:js'...[20:55:37] Starting 'min:css'...[20:55:37] Finished 'min:js' after 59 ms[20:55:37] Finished 'min:css' after 52 ms[20:55:37] Starting 'min'...[20:55:37] Finished 'min' after 7.64 μsCopying to output path C:\Users\Administrator.HBH0H2XBU8QTFTV\AppData\Local\Temp\PublishTemp\KitFramework54DNU(0,0): 错误 : ָ����·�����ļ���̫�����������߶�̫������ȫ�޶��ļ����������� 260 ���ַ�������Ŀ¼���������� 248 ���ַ���

并且最后的错误DNU居然是乱码，有知道如何解决这个问题的朋友期望赐教。

编译都成功了，但是发布不成功。

后来在网上找到一位老兄碰到了和我一样的问题，并得到了解决：

由于本人英文水平实在很差，英文好的可直接查看原文

原文地址：https://stackoverflow.com/questions/33832635/path-too-long-when-publishing-asp-net-5-from-visual-studio-2015

原文中对此问题的描述是发布的输出路径的问题，所以打开了.pubxml文件，pubxml文件就在 项目名称/Properties/PublishProfiles 结构下面。打开这个文件并在其中添加一组标记<PublishOutputPathNoTrailingSlash>。如下面这样

<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">  <PropertyGroup>    <PublishOutputPathNoTrailingSlash>C:\Temp\Publish</PublishOutputPathNoTrailingSlash>  </PropertyGroup></Project>

增加这样一个临时的短目录，就可以正常发布输出了。