Hi All,
I am having trouble debugging a Visual Basic DLL that is (or should be) called by ASP webpages. I have my VB project open and running with the Debug option set to "Wait for components to be created". The DLL itself is compiled and registered in my System32 directory. I have IIS running and the pages display at http://localhost/index.asp
However, when the active content is used which should then call the functions of the DLL, nothing happens. The code in the ASP that calls the DLL is:-
SET MyObj = Server.CreateObject ("GPSWDLL.clsGPSWHealthChe
strHealth = MyObj.GetHealth(date)
All the spellings are correct and it is a valid function call. However, the code never breaks into my VB project, nor does the registered DLL in System32 get called as nothing is returned.
What I really need is for it to break into my VB project so that I can step through the code.
If anyone can suggest anything I might be doing wrong or have forgotten to do it would be very much appreciated.
Thanks in advance.
Shivermetimbers.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
It may be a compatibility issue. I would unregister all copies of the dll on your system, and remove it from your sytem32 directory. Then, recompile, keeping only a copy of the dll in your development folder for the time being. Then go to Project -> Properties -> Component tab and ensure Binary Compatibility is set. Then rerun your DLL and then open the ASP page.
What I actually had to do in the end was open a new Visual Basic project and copy and paste the code from the old class files into new ones and recompile.
For some reason it didnt like the old project but when I made a new one with the same name it worked fine. Very strange. I dont know why this happenned.
Thanks for the suggestions.
Business Accounts
Answer for Membership
by: wraith821Posted on 2005-11-04 at 04:54:01ID: 15223975
goto Project properties in vb. on the debugging tab enable start brwser with URL. put the url to the page you that calls the dll. (run the dll from vb.) press play in vb. this will open your web browser to the url. as the web browser opens and runs your code from your dll. you can add breakpoints and debug from there.
make sure in IIS that your website is an application and that the debugging flags in the application configuration settings reflect server side debugging.