"There is no source code available for the current location"... what the?!?


E

Eric A. Johnson

As the subject says, in my VB.NET 2003 project, whenever there is a bug that
causes the project to crash (or I insert a Stop into my project), it pops up
with a window telling me this. The only problem is... there IS source code!
I wrote it my ^#$%!&* self! Grrrr... I'm almost done with my project, but I
can only get any further if I can find out where the problems are being
caused. My breakpoints aren't working at all, no matter what I do, and I
strongly believe that this bizarrely freakish error is what is keeping my
breakpoints from working. The autos don't seem to be working as normal,
either. I'm still learning a lot about VS.NET; admittedly, much confuses
me, but I keep on slugging, futilely hoping that things will start making
more sense. How can I get it to see the source code that I have plainly put
in?!?!? The stupid program wouldn't work without source code in the first
place!!!

-- Frustrated Eric
 
Ad

Advertisements

J

James

Ran into this ... run in debug mode. Also check project configuration for
release type (set to debug).
 
E

Eric A. Johnson

I see.... grrr... Why can't M$ make it so that you only have to change one
area... why two areas to change? Furthermore, why can't they give an
adequate explanation anywhere?!? At any rate, I am extremely grateful for
your help. :)

-- Eric
 
Joined
Mar 9, 2006
Messages
1
Reaction score
0
Hello +

I have the same problem as you with my c++ program. Do you already hava solution for that probelm`?

Best regards
Geri
 
Ad

Advertisements

Joined
Sep 20, 2006
Messages
1
Reaction score
0
I came across the same problem. I was using a seperate dll project that a colleague had created that we were using for database access. The problem occured because the version he was sending me was a compiled 'Release' Version.

Another reason that it was happening was because of an exception within the dll project. When the exception occured the code accessing the dll could not see the assembly causing it to display this message.

To solve it, i just copied the dll project to my machine from source safe, recompiled it as a debug version, got rid of the reference and re added it.

It now works fine. Hope this helps



Rich
 

Top