[2005] program refuses to start in IDE

[JacquesLebrun]

I have a program that often refuses to start from the IDE. Without changing anything in my code, I quit and restart the IDE 5-10 times and suddently it allows me to compile and run my program.

When it refuses, I get the error "The operation could not be completed. Teh process cannot access the file because it is being used by another process.". If I try a second time without quitting the IDE, I get the error "Visual Studio could not copy a support file to this location: 'S:\DotNet-Apps\MyProg\bin\Debug\MyProg.vshost.exe'. Please verify the path exists and is writable."

I am 100% that I am the only one working in this program, so it cannot be locked by another user.

[Hack]

If you moved the project to a local drive and off the network, does the problem go away?

It could be network traffic. Is your project on a busy server?

[danasegarane]

You cannot able to run ur VS program from Network Drive(You can able to run with restricted access). U Have to copy the program to a local folder and then only it will run. Or try this one from bmahler

[JacquesLebrun]

My computer is very powerfull with lots of memory (WinXP). The server is really nor busy. I suspect it could be something that doesnot free up a resource properly when I quit my program, but I cannot put my finger on it.

[Hack]

Just try running it locally and see if there is any difference.

I'm not suggesting "moving" the source code, just copy the solution files, run a test or two, and then you can always delete it from your local drive.

[JacquesLebrun]

Ok, I did some more tests. If I run locally, I could never reproduce the problem.

However I did notice a pattern when I compile my program from the network drive. If I run my program without any programming errors, it works fine as many times as I want. However if make a typing mistake (like var = truw) and I run the program, I get the warning telling me that the program has errors, I click on NO to abort, fix the error and try to run it again. That is where I get the error message. I usually need to start and exit the package a dozen times before I can run my program again. It looks like the failed compiled created some king of lock on my executable.

It only happens if the package is located on a network drive. Has anyone experienced the same problem? Is there a solution (don't ask me not to make typing mistakes in my code ...)

[JacquesLebrun]

Does VB.NET Professionnal Edition supports having the source files on a shared drive?

We are two persons making changes to this program so it must reside on a network drive. Every time I make a change, the program refuses to start like if the executable was locked by another process (I know it is not the case). After quitting and restarting VB Studio about 10-15 times, my program finally starts.

This is a very inefficient way to work, anybody knows a solution to share a source code beteen two persons?

[techgnome]

Visual Source Safe....the source code then resides in the VSS database. When you need to make a change, you check it out to your local drive.... make changes, check it back in. Optionally at this point you can label it with what the change(s) were. Then when the other developer needs it, get the latest, etc.

-tg