msbuild - How can I prevent Visual Studio from locking the xml documentation files in the bin directory? -


My visual studio solution includes a web application and a unit testing application. My web application uses log4net I want to be able to use msbuild from the command line to build my solution. However, whenever I create a solution from the command line, I create errors because it can not copy log4net.xml into the test project's bin directory.

The error message is:

"Unable to copy file '\ bin \ log4net.xml' from 'bin \ debug \ log4net.xml' '\ bin \ Log4net.xml is 'prohibited.'

It seems that the Visual Studio is locking this file, but I do not understand why it should be VS to XML in the project Prevent documentation files from locking? I had this problem with Visual Studio, too. We use NAnt instead of MSBuild, but the problem is the same. I was able to work around it by modifying the build file to ignore failures while copying the XML file.

Note that this does not really solve the original problem because xml files are still locked, but this solution does not change the actual content of our XML documentation very often because it is great for us.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -