Title: <solution> build fails with "Cannot access the file [file] because it is being used by another process"
I have found that the indexing service is a frequent culprit in this sort of scenario. Try adding appropriate entries** to exclude directories from being scanned by the service. [The indexing service is configured through an MMC snap-in accessible through administrative tools.]

-Troy

** Don't forget to include one for the Temporary ASP.NET files, typically: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files

Foster, Richard - PAL wrote:

Hi there,

I suspect this problem may be associated with something like (for example) the anti-virus software over which I have no control.

I see from the mailing list that it was believed resolved back in 2004. Well, I'm getting it (intermittently) with the most recent "nightly" build (the one dated December 13th).

It appears to occur most frequently under the following conditions:

1) The build must be a sub-build (i.e. triggered through a <nant … /> element)
2) The project being built by the <solution … /> is a small one consisting of one form, and at most two other classes.

The culprit which is "being used by another process" is almost invariably ResGen.exe. I guess it is copied to the temp folder before an attempt is made to compile the resource files.

Any suggestions for how I can resolve this?

Regards,
Richard

Reply via email to