Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

VB6 problemo

  • 30-03-2005 3:06pm
    #1
    Peace
    Registered Users, Registered Users 2 Posts: 2,758 ✭✭✭


    Folks,

    Forgive me if this is a stupid question but i googled and i didn't get anything (useful).

    I need to step into a VB6 dll which is referenced from another vb6 standard project.

    So the state of affairs is this, i am running the vb6 project (exe) and the dll in the same "Group" project.The compiler seems to be simply ignoring my break points... now i'm 100% sure there's a way to do it.

    Any help would be greatly appreciated. This is a project i inherited since someone left and its horrible.


Comments

  • #2
    Evil Phil
    Registered Users, Registered Users 2 Posts: 7,468 ✭✭✭Evil Phil


    Probably useless but is your exe project referencing the dll or the dll project? It needs to be the dll project (iirc). I also seem to remember that you need to be running the exe and dll in different instances of Visual Studio. Again that could be wrong. :confused:


  • #3
    Peace
    Registered Users, Registered Users 2 Posts: 2,758 ✭✭✭Peace


    Well buddy, i've got it and yes i think its the fact it was referencing a compiled version of the dll rather than the dll project.... but i just picked a difference reference of the same name from the references list.

    So i honestly don't know what file its referencing - there's no .dll file in the directory.


  • #4
    amen
    Registered Users, Registered Users 2 Posts: 2,781 ✭✭✭amen


    it doesn't (normally) make any difference if you are running 2 different VS instances or 1. VB debugger should still pick it up
    I would imagine the real issue is that Binary Compatibility is Set to None on your dll causing it get a new GUID each time the dll is compiled or placed in debug.

    You should fix this other wise you will have loads of problems once the dll has been release.

    if you unsure what to do post back


Advertisement