{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 趁早两清 的问题《Visual Studio Deployment Package - change the file》','https://www.manongdao.com/q-1379807.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Everything works as expected but I would like to improve the directory structure that the .zip produces.
When I create a deployment package I have it create in a custom directory which works fine but the .zip it creates is in the structure of:
content/c_c/users/pcName/documents/VS2010/Projects/ProjectName/obj/release/package/packageTmp
Only in the packageTmp directory do I get to the files I want!
Is there a way for the created zip to not include all of those empty directories?
I never understood the folder structure either. By using msdeploy to publish the site it uses that folder structure to deploy multiple sites/assets at once. It's annoying when looking at the package itself but it does "work". Just use msdeploy to actually deploy the package and you don't have to look at the crazy folder structure. :)