Visual Studio .NET - Cannot 'Attach to Process' successfully for debugging

I am developing on a new computer with VS2005 SP1 (Team Edition for Software Developers) and VB6.0 (SP6).

I am attempting to step into the VB.NET code (.dll) from VB 6.0 source code (.exe).  Others are able to do this on their machine, but I am unable on my machine.

When the .NET code is built into the .dll, the VB 6.0 code runs the .dll just fine.  However, when I go into VS2005 and attempt "Attach to Process" to vb.exe, I cannot step into the code.

- My bookmarks are solid red.

- My bookmarks are in the correct places to be hit.

- My project is in Debug mode.

- The Debug/Modules window is completely empty.  There are no rows.

- Again, this exact source code works for others and they have never had an issue running the code.

I've read many items online but have not found anyone with this type of problem.  I am willing to try just about anything at this point.

I appreciate any ideas and suggestions...

Does your application or dlls involves remote computer or debugger?

-Paresh

If yes then this could happen if the remote computer didn't send back an initial response within 45 seconds, but I am not sure why it would ever take that long.

Can you view the machine through file sharing (Start->Run->'\\<computer_name>')?

If you run the remote debugger on the server from the start menu (Sart->All Programs->VS 2005->VS Tools->Remote Debugger), then you will get a small UI. If you run the UI on the server and try to connect, is there a message printed out about someone connecting?

-Paresh

I am running both the VB 6.0 code and VB.NET code on my machine.

Hi,

Is your project File-Based or IIS-Based? If it is File-Based, the Visual Studio debugger will attach to built-in server process just like the member said; if it is IIS-Based, debugger will attach to IIS process.

In your case, please make sure you compile your project in debug mode. You can set it to debug mode in web.config file as follow:

<compilation debug="true" > <assemblies>

If this flag is already set then could you attach to the application process using Visual Studio debugger manually. You can get Attach To Process Dialog Box by Debug -> Attach to Process. For more information, see http://msdn.microsoft.com/en-us/library/aa290713(VS.71).aspx

-Paresh

Hi,

Please go through the http://msdn.microsoft.com/en-us/library/3s68z0b3(VS.71).aspx link and let me know if problem still persist. Could you also tell me what do you mean by "I cannot step into the code."

-Paresh

I am working with a desktop application, not a web application.  I am attempting to debug the VB.NET code, however cannot get into the code to debug it ("step into the code").  I have breakpoints at the correct places, but they are not being hit.  The VB.NET code is not 'attached' like it should be.

Also, again to clarify, this does work fine on other people's computers.  They have come over to my machine and done the exact same steps they do, and for some reason it does not work on my machine.  Their Debug/Modules window has all the symbols when they try"Attach to Process" however my window stays empty when I try it.

I am assuming this has nothing to do with the actual code, but something wrong with my computer or a setting that hasn't been set correctly.

Hi,

It's possible that your JIT Debugger is disabled for VS2005.  It requires COM+ permissions.  To test it out, prop open VS2005 or Snippet Compiler, or similar.

Write a small program to invoke the debugger.

Main(args[])
{
  System.Diagnostics.Debugger.Break();
}

Compile and run the program, if it shows you the vs2005 and vs2005 CLR, then there's other issues at hand.

-Paresh

Hi,

Couple things to try next: From Start/Run: dcomcnfg

Expand My Computer - > DCOM Confg -> Visual Studio Just-In-Time Debugger,
Ensure the proper security has been set for your current policy/user.

Check this key to make sure the correct JIT debugger is set.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\Debugger\JIT\

-Paresh

Hi,

From "Visual Studio Hacks" by James Avery (O'Reilly, 2005), page 167:
--
"To enable JIT debugging with Windows Forms, you will need to add a configuration setting either to the app.config of your application or, if you want to enable JIT debugging for all Windows Forms applications, to the machine.config.  To enable JIT debugging, you need to add the following element inside the <configuration> element:
<system.windows.forms jitDebugging="true" />"
...
"If you want to modify the machine.config file to enable JIT debugging for all Windows Forms applications, the file can be found in the following directory:
%SystemRoot%\Midrosoft.NET\Framework\v1.1.4322\machine.config
The machine.config file actually already has this element -- it simply needs to be uncommented."
--
It goes on about the JIT settings in the registry.

-Paresh

Murphy's Law:  No matter how long you've been trying to find a solution, post and ask for help and then you'll find your own solution!  :)

I found a website with this debugging technique below.  When I selected "Managed Code" and "Native Code" for some reason it now connects just fine.

=====================================================

To obtain specific information about why a code type failed to attach

stop worker process than try again for attached process

and also make sure that this did not degub on another m/c

To attach to a running process

*****************************************************
                                                                                                      
        SOLUTION WAS FOUND A FEW POSTS ABOVE             
                                                                
*****************************************************