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

Discussion in 'ASP .Net' started by Eric A. Johnson, Feb 12, 2006.

  1. 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

    -- Frustrated Eric
    Eric A. Johnson, Feb 12, 2006
    1. Advertisements

  2. Is this a Windows or Web application?
    Christopher Reed, Feb 12, 2006
    1. Advertisements

  3. This is a Windows application. :)

    Eric A. Johnson, Feb 12, 2006
  4. Eric A. Johnson

    James Guest

    Ran into this ... run in debug mode. Also check project configuration for
    release type (set to debug).
    James, Feb 12, 2006
  5. 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
    Eric A. Johnson, Feb 12, 2006
  6. Eric A. Johnson


    Mar 9, 2006
    Likes Received:
    Hello +

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

    Best regards
    Geri, Mar 9, 2006
  7. Eric A. Johnson


    Sep 20, 2006
    Likes Received:
    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

    rich2403, Sep 20, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.