Well, I'm no longer having the problem, but VS would throw an error saying something to the extent of AccessViolation, or something like that, saying the memory may be corrupt. That led me to disabling the real time protection, so then it worked fine. I have now just dumped bit defender for ESET, which works fine.
I am searching since around two days for a solution of this problem. I'm using BD 2009 and VS 2008 with the same Debug-Start-AccessViolation. But in my BD it was not necessary to disable the ESET.But the option "Intrusion detection system" (Firewall) must be disabled. So the start problem in VS-Debugging was killed!