Clever Geek Handbook

Visual Studio publishing error in bin directory

I am using Visual Studio 2008 Service Pack 1 (SP1) and the web application I am trying to publish to a local directory does not work even though the project works fine. It doesn't give any build errors and doesn't show anything in the Output window why it failed:

Publish folder folder ...

========== Build: 2 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========

As you can see from above, this fails when publishing the bin folder. Does anyone know why he is doing this and what I can do to solve it? I should also point out that I can publish other web apps just fine, only this one has a problem.

+2


source to share


5 answers


You may have a problem if one of the DLLs in the BIN is being used by another process at your publishing location. I am assuming that you cannot manually delete the file if you go to that location directly.



You can try to stop IIS on the field you publish for this application pool and see if that gives a different result. Just keep in mind that this will make the site unavailable until you start IIS again for the application pool.

+2


source


I used to have the same strange anomaly. "Reconstruction", as opposed to build, solved the problem in my case.



+2


source


Please enable verbose build logging, it will give exact error as to why posting is not working.

In my case, the filename exceeded 256 characters and MSBuild didn't like it.

Follow these steps to enable verbose logging in build output

To change the amount of information included in the build log

  • On the menu bar, select Tools, Options.
  • On the Projects and Solutions page
  • select the Build and Run page.
  • In the list of output details for the MSBuild build project, select Detail , and then click OK.
+2


source


Your project may be missing files. This will cause the publication to fail as it cannot publish files that no longer exist.

+1


source


I have the same problem. I started Visual Studio as Administrator and got the error details.

In my case, some of the included files were deleted externally. VS tried to copy these deleted files to the output path.

0


source






More articles:


All Articles