Problem with Build

My guess is that the company name does not matter.

hi,

thanks for your very informativ answers,

the problem exists no more. After checking the project-property-page and changing some entries in the

Assembly Information dialog, it hasn't occured up to now.

I still don't know what exactly it has been, my guess is it's been "noname" for company name.

thanks again

I think that Check for Running Processes in the previous reply is the most likely. It is possible for an application's window to be closed without the application ending. When that happens you won't see the window but you can see the application in the Task Manager. What kind of application is it? Is it WPF or Windows Forms? If it is Windows Forms then is the Program class (the Program.cs file) different than a typical Windows Forms appliation?

You say:

I have to close and reopen Visual Studio

But you do not say if you are able to build at least once after that. I assume so. It seems strange to me that restarting Visual Studio would free up the file. What happens if you execute without debugging (such as with Ctrl-F5)? What happens if youi execute the application outside of VS?

Your antivirus might be the problem but it seems to me that if it was then the other applications would have the problem.

As for checking the Output Window, also check it during the execution and after you think it has finished executing.

Sometimes the virusscan is interfering. Just to check, disable it, try again to see what happens and re-enable it.

Is myapp closed gracefully without errors? What does it do? Any COM, processes, threads or assemblies that could remain open?

1. Check for Running Processes: Before trying to delete the myapp.exe file, make sure the application is not running. Check the task manager for any instances of your application that might still be running.

2. Close Visual Studio: Ensure that you completely close Visual Studio before attempting to delete the myapp.exe file. This includes closing all instances of the IDE.

3. Clean Solution: Try performing a clean build of your solution. In Visual Studio, go to the "Build" menu and select "Clean Solution." After that, try building your solution again.

4. Check Output Window: Look at the "Output" window in Visual Studio after attempting a build. It may provide more information about what process is holding onto the file.

5. Restart Explorer: Sometimes, Windows Explorer might be holding onto the file. You can try restarting Windows Explorer to release any file locks. Open Task Manager, find "Windows Explorer" in the list, right-click, and choose "Restart."

6. Anti-virus or Anti-malware Interference: Some anti-virus or anti-malware software may interfere with the build process. Temporarily disable your anti-virus software and try building again.

7. File Locking Tools: Use tools like "Process Explorer" or "Unlocker" to identify and release file locks. These tools can help you identify which process is holding onto the file and release the lock.

8. Check for Project References: Make sure that your project references are correct and not causing conflicts. Incorrect references might lead to unexpected behaviors.

9. Update Visual Studio: Ensure that you are using the latest version of Visual Studio. Updates often include bug fixes and improvements that might address such issues.

10. Check for Extensions/Plugins: Some Visual Studio extensions or plugins might cause these kinds of problems. Try disabling extensions one by one to identify if any specific extension is causing the issue.