Using Visual Studio 2022, I have recognized an issue in which attempting to run my project results in an error message in regards to the process id being unable to run one of the projects in the solution.

This was a pop up error, was very vague, not even including an error code, and wasn’t displayed in the output of visual studio. Unfortunately I did not save a screenshot of this pop-up, but here is what I did next:

I cleaned the solution and rebuilt, and received the following:

I have restarted visual studio several times before receiving this error, and so with this level of detail of being able to see what file specifically has a file-lock on it, I decided that perhaps I shut down my machine, somehow in the background there is a process running on my operating system that is accessing these DLLs. After all, I am notorious for putting the work computer to sleep at night so start up the following morning is faster. Of course, lots of processes happen on the operating system in a given day let alone a few weeks.

So, the issue went away for now. My question is what causes this in the first place in visual studio? Is there something I may have done incorrectly that would have caused a DLL to become file locked? Is this a known issue within VS 2022? I am having a hard time finding answers related to my version of Visual Studio, although I do at least see the same error code mentioned in older versions of VS, such as this link to another SO post.