VS Error on Start

I've been having this error off and on, different projects.

"Unable to copy file "obj\Debug\ImportSenateRules.exe" to "bin\Debug\ImportSenateRules.exe". Access to the path 'bin\Debug\ImportSenateRules.exe' is denied."

This is a simple project on my local machine and I have full permissions and I am the Administrator.

I can switch to release mode and it runs just fine.

:(

I see that every now and then. Sometimes, it just appears to have no impact, other times...well, I guess I'm not really sure what I do to fix it. Apparently, it's so insignificant that I don't remember.

Quote:

---

Originally Posted by dbasnett

I've been having this error off and on, different projects.

"Unable to copy file "obj\Debug\ImportSenateRules.exe" to "bin\Debug\ImportSenateRules.exe". Access to the path 'bin\Debug\ImportSenateRules.exe' is denied."

This is a simple project on my local machine and I have full permissions and I am the Administrator.

I can switch to release mode and it runs just fine.

:(

---

I believe it was an old Borland C compiler that would give a message like "Is it running?" when the compiled .exe file couldn't be generated.

So, that is the question. Is the .exe file in your bin\Debug folder currently running? You may need to check task manager to find out.

Quote:

---

Originally Posted by OptionBase1

I believe it was an old Borland C compiler that would give a message like "Is it running?" when the compiled .exe file couldn't be generated.

So, that is the question. Is the .exe file in your bin\Debug folder currently running? You may need to check task manager to find out.

---

No. Unless when I press start it is running twice.

If I clean the project and then rebuild the project the error goes away for awhile.

Most of the time I could fix this by deleting the bin/debug/release folders. But I did have one project that I couldn't fix and had to start a new project and add the existing files to it. I never did get an answer to what actually caused the error to start happening. Good luck

Edit: Come to think of it, I believe one time I found the offending xxx.Exe file in the obj folder.

The most common cause of that is trying to compile the project while the EXE is already running.

Quote:

---

Originally Posted by Niya

The most common cause of that is trying to compile the project while the EXE is already running.

---

All I do is press Start.

What version of Visual Studio are you using?

Quote:

---

Originally Posted by Niya

What version of Visual Studio are you using?

---

Most up to date version of VS 2022 Professional. (Doesn't it say that in the thread listing?)

Quote:

---

Originally Posted by dbasnett

Most up to date version of VS 2022 Professional. (Doesn't it say that in the thread listing?)

---

Hmmm....So lets say you restart the system completely, start Visual Studio, open the project and pressed start, does it still not work under these conditions?

Quote:

---

Originally Posted by Niya

Hmmm....So lets say you restart the system completely, start Visual Studio, open the project and pressed start, does it still not work under these conditions?

---

IDK... I can't seem to get it to fail today. Made up some new nonsense code, clearing labels, etc. and it won't fail.

That sounds right to me. When I've seen it, it's always just gone away. Not enough predictability to form a pattern.