Tracing with Visual Studio 2008 works only the 1st time

Hello

I use Visual Studio 2008 and TestStand 4.1.1.

I have a c# dll and I'll call a function of TestStand.

In VS, I "join to deal with...". "and choose to attach it to TestStand. I start my sequence and VS to get to the point break that I set myself in VS.

Everything is great.

Now if I "Stop debugging", I do some changes for my dll, recompile all right and reattach to TS, everything seems ok.

But if I start my sequence, do not strike my breakpoints and step runs without me trace in my c# code.

The only workaround is to close TestStand, restart it, reopen the sequence and reinstall VS on it, then works again my breakpoint.

What's wrong? I wouldn't restart TestStand whenever I do change the dll and reattach. I tried to unload all modules also with no success.

I do something wrong or solutions to avoid restarting TestStand after changes to the c# code and you want to draw it.

Thank you.

Hi Matt,

First of all, I tried to replicate what you experience following your instructions, but I couldn't recompile the DLL after the stop debugging in Visual Studio, because the DLL was still in use in TestStand.  After I unloaded all the modules, I could recompile.  I then re-attached and saw what you were doing.  So, to get around him, I tied to the process in a slightly different way.  In Visual Studio, I went to tools' attach to process, and then chose the seqedit.exe process.  Before mounting, I pressed the Select button on the right side of the dialog box in the middle of changing the type of code we are debugging.  Select the radio button "Debug these code types" and verify that "Managed".  This will ensure that the debugger attaches only to managed code (c#).  After I did, I could run my sequence again without having to restart TestStand.

I would like to know if it works for you.

Tags: NI Software

Similar Questions

Maybe you are looking for