Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual Studio 2012 Web Publish doesn't copy files
    text
    copied!<p>I have a Web Application project in VS 2012 and when I use the web publishing tool it builds successfully but doesn't copy any files to the publish target (File System in this case).</p> <p>If I look at the build output I can see everything gets copied over to obj\Release\Package\PackageTmp\ correctly but then all I see in the build output is this:</p> <blockquote> <p>4>Done building project "{Project}.csproj".<br> 4>Deleting existing files...<br> 4>Publishing folder /...<br> 4> ========== Build: 3 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========<br> ========== Publish: 1 succeeded, 0 failed, 0 skipped ==========</p> </blockquote> <p>Even though it says the publish succeeded there are not files in the target directory for the publish.</p> <p>I have seen this in multiple projects and sometimes it seems like the Solution/Platform configurations cause this problem but I haven't been able to pinpoint an exact cause for this.</p> <p>Has anyone else seen this happening or have an idea on how to get this working correctly?</p> <p><strong>UPDATE:</strong></p> <p>I may have found a workaround for this. I just had this happen again and I was messing around with the publish settings. Once I changed the selected Configuration on the Settings tab away to another configuration and then back to the one I wanted to use all my files started publishing again. Hopefully this works on other projects in the future. </p> <p><strong>UPDATE 2:</strong></p> <p>I posted a bug on Microsoft Connect and heard back from a developer on the VS Web Developer team. He said they have fixed this issue in their internal builds and will releasing an update to the publish tool soon that will fix this problem.</p> <p><strong>UPDATE 3:</strong></p> <p>This has been recently fixed with Visual Studio 2012 Update 2</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload