Home/ Questions/Q 8544107
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T12:28:26+00:00

If output binaries were locked in Visual Studio 2010 (or older), the build would

  • 0

If output binaries were locked in Visual Studio 2010 (or older), the build would simply fail and say it could not copy because the files were in use.

Now it goes into a retry loop, which is really annoying because:

  • It can’t be interrupted
  • It doesn’t help the situation

It just means I have to wait longer for the build to fail.

Does anyone know how to turn this off?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The following lines should help:

    <PropertyGroup>
  <CopyRetryCount>0</CopyRetryCount>
</PropertyGroup>

    You should add them into your project file (which is *.*proj, e.g., csproj), right after the opening <Project> tag.

    To solve the problem globally, these lines should be placed in c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets right after the opening <Project> tag.
    More info: http://msdn.microsoft.com/en-us/library/3e54c37h.aspx

    Not sure if it can cause some build problems in future – I found this out right now.

    Update:
    For VS 2013 old location does not work anymore, so you can place these lines in c:\Program Files (x86)\MSBuild\12.0\Microsoft.Common.props.

    • 0