JohnGaby--I meant to add this
http://www.microsoft.com/w
Main Topics
Browse All TopicsI have an inproc ActiveX control. I have recently put IE8 on my development machine, and can not longer debug the control. Prior to IE8, the control was loaded into the address space of IE and to debug, I would start IE under the debugger, then when my control was loaded, the breakpoints would be activated.
Apparently with IE8, the control is no longer loaded into IE8's address space, but rather into a separate process. I have tried attaching the other process with the debugger, but I am unable to get any breakpoints to work, nor am I able to break the process.
Does anyone know how to debug ActiveX controls under IE8?
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.
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.
JohnGaby--I meant to add this
http://www.microsoft.com/w
JohnGaby--Since I do not know what your ActiveX control is, I can only offer general suggestions.
http://download.microsoftv
http://my.opera.com/sirnh1
Thanks again for the links. The ActiveX control is an ATL com control written in C++. Visual Studio 2008 is used as the debugger. The problem I am having is that the control (which runs as an 'inproc' com object) no longer runs within the address space of IE8, but rather a separate process. Unfortunately, I do not seem to be able to attach that process to my debugger in a manner that allows me to set breakpoints, or break execution.
The only articles I can find regarding debugging with IE8 concerns the built in debugging tools for CSS, HTML, and JavaScript. These are not helpful to me in debugging my C++ binary dll.
I too am struggline with this.
I managed to figure out a way to do it tonight. Here's the process I used.
1) Start IE on its own.
2) load my page which instantiates my ActiveX.
3) Use the MS SysInternals Process Explorer to find the process which loaded my ActiveX
4) Instruct the VS Debugger to "attach" to that process. Take care to switch the debugger manually to attach in 'native' mode. It seems to want to attach in 'script' mode now.
5) your break points should get hit.
MS has created a nightmare for developers faithful to their platform and who actually develop software for IE using the ActiveX model. This is going to have a major impact on development progress. Gone are the days where you just hit F5 and your break point triggers.
Good luck.
Thanks for the response. Have you actually done this? I tried it, and although I was able to attach the process, I was not able to set breakpoints or even break execution. Perhaps I was not attaching the correct process? How did you determine what process actually loaded the ActiveX control? What I did was to have my control throw up a message box, and then look for the process that owned that window. Attaching the debugger to that process did not work for me, however.
By the way, this is no longer an issue for me in this particular case, since I switched to using an .exe version of the control (for reasons other than debugging), and am able to attach and debug my own process without a problem. I am still interested in finding a solution for future projects, however.
Yes, I have done this. I used the MS SysInternals Process Monitor (step #3 above) to determine which process loaded my ActiveX. I then attached the debugger to it, overriding the default 'script' mode so that I could do 'native' debugging and it works. It's just realyl painful.
Have you seen the tech notes about IE8 and the Losely-Coupled IE architecture that explains all this?
read about it here:
http://blogs.msdn.com/ie/a
http://blogs.msdn.com/aski
I've had really strange results actually using this. When I set the TabProcGrowth=0 and I then start IE fro the debugger I get an IE error that there is connectivity issues; the browser can't see the network. When I use TabProcGrowth=1 the browser works but my tab/activeX is in a different process and I have to use the process stated above to debug. Long gone are the <press F5 & hit a breakpoint> days.
Business Accounts
Answer for Membership
by: jcimarronPosted on 2009-06-08 at 16:51:45ID: 24577222
JohnGaby--Perhaps of help en-us/libr ary/cc2884 72.aspx
http://msdn.microsoft.com/