Is being used by another process, so the process cannot access this file.

I believe many people have encountered such problems.

Recently, my computer seems to be a bit exhausted. I don't know why the console program only needs to be used.Start execution (not debugging)It will inevitably remain in the process

And the process manager does not see ~~

The most disgusting thing is that even restarting VS still cannot generate

 

After some attempts, the process is displayed in tasklist in cmd.

 

This is easy to handle.

Use taskkill to end the process.

Taskkill/f/im "leleapplication2.exe"/t

 

However, due to the explosive growth of my character, every time the process is stuck, it is too troublesome to execute the cmd command every time.

So I thought

You can also use variables, so you are not afraid to generate a file name.

 

However, there are still problems in use.

If no stuck process exists, it cannot be generated.

 

So I try again

Finally, I finally found that the error will not occur if I add a filter condition.

Taskkill/f/fi "pid gt 0"/im "leleapplication2.exe"/t

The underlined part indicates a process whose pid is greater than 0.

This operation is executed again. Only "information", no "error" is returned.

 

So eventually

Set

Taskkill/f/fi "pid gt 0"/im "$ (TargetFileName)"/t

No matter whether there is any process residue, it can be generated smoothly...

 

 

Although this is the solution, I still think it is possible that vs is not installed and is preparing to reinstall vs2013 ....