Hi,
sorry for posting here... since I'm programming in VB it seemed to make the most sense. But basically I guess it's Visual Studio itself giving me problems.
The funny effect is: After debugging my application and making any changes (re-building or not doesn't make a difference) then, trying to debug again, nothing happens... I have to close and restart Visual Studio (2010).
Sometimes - but that seems more or less randomly - I get an error message that "the file is in use by another process". So I figure it must be something in my code that produces that, maybe any remains of a thread (I'm not experienced with them and don't fully understand) still in memory.
Does anyone here have an idea where I could begin tracing that? It's really annoying.
I would also be thankful for information about how I could find out if some code (and possibly which) remains in memory despite of having closed the application i.e. terminated the debugging.
Thank you for any hints,
Michael
EDIT: Thank you for the help! It seems to turn out that some twisted code was responsible for the effect. After several massive changes, cleans, etc. it didn't happen anymore for some hours now - having bothered me for days before.
What I have tried:
(not relevant for this question, I suppose)