Debugging into dotnet DLLs.

Hi Rajender,





Specify TestComplete as a host application for your assembly and start debugging by launching TestComplete from Visual Studio instead of attaching to a process.





Let me know whether this works.

Hello David,



Thanks for your prompt reply.



Please elaborate more on the process "Specify TestComplete as a host application for your assembly and start debugging by launching TestComplete from Visual Studio instead of attaching to a process". If you can share some example program, that will be really helpful.



Thanks,

Rajender Mehta

Hi Rajender,





Set your .NET assembly project as a startup project in your Visual Studio solution. Then, select the 'Project | Properties' item from the main menu and insert the full path to the TestComplete.exe file for the 'Command' field in the 'Configuration Properties | Debugging' option group. After this, just start debugging by pressing F5 or selecting the 'Debug | Start Debugging' item from the main menu. TestComplete must be closed before you start debugging.

Hello David,



Above option is also not working. Can you please replicate the same by some example creation and see if you are able to debug?



FYI: I am using VS Team Edition 2008 with TestComplete 7.52 trial version.



Thanks,

Rajender

Hi Rajender,





Sorry for wrong information, TestComplete works with .NET assemblies via a separate process: tcHostingProcess.exe. It cannot be run from Visual Studio, so you need to attach to this process. The process is launched by TestComplete when you try to use the CLR Bridge feature for the first time or when you click the 'Reload' button in the CLR Bridge feature properties editor.





Please let me know whether this information helps.

Hello David,



Yes it worked for me.



Thanks for your prompt response.



Thanks once again,

-Rajender

Hi Rajender / David,



I'm currently running into the same problem where TestComplete (8.20 Trial) cannot debug into the C# assembly code. I am able to call into the C# method from TestComplete using CLR Bridge, however.



I have TestComplete CLR Bridge point to the Debug version of the C# assembly and reloaded to startup the tcHostingProcess.exe. I then attached to this process via Visual Studios 2008. Immediately, I get a "The breakpoint cannot currently be hit. No symbols have been loaded in this document" warning.



Can anyone point out what I'm doing wrong?

Hi David,





After reloading the CLR Bridge feature, please open the Code Completion window in the editor and find an object from your assembly in this window. This will guarantee that the assembly is loaded into the hosting process.





Please let me know if this helps.

Hi David,



I am able to see the test function located in the assembly from within the Code Completion window. The test function I wrote simply returns a string back to Test Complete and I have confirmed this also to be working.



However, I'm still having a problem reaching the breakpoint I set in my assembly. This is after I already attached to the tcHosting process from VS2008.



Here are the steps I've taken:

1) Created a simple function called Hello() in my World Class which does some magic and returns a string.

2) Compiled a debug version of the assembly.

3) Open TC and CLRBridge and select the debug assembly. Click Reload.

4) Check to see if tcHosting Process is now running in Task Manager. (It is running)

5) Go back the Hello() function in VS2008 and set a breakpoint in the code.

6) Attach to the tcHosting Process



Immediately after step 6, I get the "breakpoint cannot be set" warning on the breakpoint. When running the script in TC, I get the string back from the assembly immediately (skipping my breakpoint).



Is there anything else I need to do?



Thanks.

Hi David,





Could you please send us your assembly solution along with the compiled assembly via the Contact Support form? I will look into this issue.