 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
VB Forum / COM / April 2005debug vb6 dll
Hi all, I have a vb6 dll, that use in a vb6 application. I need to debug my dll. Is there a way to do this?. I open my dll project and place break points, then place break points in application too. When I run this app, it does not go to the break points in the DLL. Thanks in advance. You may have a problem with binary compatibility. Check that compatibility in the dll project is set to binary, and that it points to the compiled version of the dll. Hi all, I have a vb6 dll, that use in a vb6 application. I need to debug my dll. Is there a way to do this?. I open my dll project and place break points, then place break points in application too. When I run this app, it does not go to the break points in the DLL. Thanks in advance. "Podi" <Podi@discussions.microsoft.com>'s wild thoughts were released on Mon, 7 Mar 2005 17:07:03 -0800 bearing the following fruit: >Hi all, > [quoted text clipped - 4 lines] >application too. When I run this app, it does not go to the break points in >the DLL. Both the dll and your application must be in the same project group. Your application must reference the dll's vbp instead of the compiled dll. If both these conditions are true, then you should be able to debug your dll. Jan Hyde (VB MVP)  SignatureWhat's the difference between a tale of lost cash and a secluded religious community? One is a money story, and the other is a monastery (Lars Hanson) [Abolish the TV Licence - http://www.tvlicensing.biz/] Jan, you are wrong here, its not mandate to have DLL and other project in the same project group. If you are tryiung to debug ActiveX exe only then you need to have both projects in the same project group. To be able to debug DLL, make sure that you refer to the DLL which is to be debugged. If you are not sure about the DLL reference, go to Project > References and then un-check all existing reference(s) to your DLL and then click on the "Browse" button and locate your DLL and try to debug now. Also, make sure that your DLL project is running (if its not in the same project group). Hope this helps. Ashok Gupta > "Podi" <Podi@discussions.microsoft.com>'s wild thoughts were > released on Mon, 7 Mar 2005 17:07:03 -0800 bearing the [quoted text clipped - 19 lines] > > Jan Hyde (VB MVP) > Jan, you are wrong here, its not mandate to have DLL and other project in > the same project group. If you are tryiung to debug ActiveX exe only then > you need to have both projects in the same project group. Actually, you can't debug an ActiveX EXE using a project group.. That's a case where you always need two instances of VB (afaik). fwiw, I've never debugged a DLL using separate instances of VB but it's possible. I always create a group project. To me, it seems that it would be the easiest way. SignatureKen Halter - MS-MVP-VB - http://www.vbsight.com Sign up now to help keep VB support alive - http://classicvb.org/petition Please keep all discussions in the groups.. Hi, Open your dll project. Keep the break points where ever you want. Go to Project/Properties menu it opens the Project properties dialogs. In this dialog go to Dubugging tab. You can find the "Start program" radio button. Select this option. Select the Application exe.Then you can run the DLL. First it start the selected application. I hope this will help you. > > Jan, you are wrong here, its not mandate to have DLL and other project in > > the same project group. If you are tryiung to debug ActiveX exe only then [quoted text clipped - 4 lines] > debugged a DLL using separate instances of VB but it's possible. I always > create a group project. To me, it seems that it would be the easiest way. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.