Why does a Teststand sequence pass leave Visual Studio Project in running state, after the sequence has stopped?

[InVI_MaW]

Hello!

What I did, why I post my question:

1.) I started NI Teststand 2012 (in evaluation mode)

2.) I started the Demo => .NET => "computer.seq" example in the original Teststand examples folder

3.) I placed a breakpoint at the first Teststand step, started sequence "Single Pass" and

     tried out Debug => "Step Into" as the Single Pass arrived at my Teststand breakpoint

4.) Visual Studio 2012 opened and I could step through the C- code

5.) Finishing debugging with "Continue" in Visual Studio and "Continue" in Teststand

6.) Teststand shows its report

      Now I expect that the Teststand sequence has finished and I can change the C- code project / recompile

      the Visual Studio project and Re-Run the Teststand sequence without closing and opening Teststand and

      Visual Studio all the time

7.) *** BUT ***: Visual Studio is still in "Running" state:

      I cannot recompile the C- code project, as the DLLs are still in use / read only.

      Even Teststand's "File=> Unload all modules" does not help in this situation.

I would like to use Teststand/Visual Studio combination in this way - developing my C-code routines

I tried out more:

o) Closing Teststand releases the C- code project again and I can recompile it.

o) Running the Teststand sequence "Single Pass" without "Step Into" the C-Code in combination with

    Teststands "File=> Unload all Modules" releases the C- code project and it can be recompiled

    BUT: As soon as "Step Into" has been done once, the C- Code Project is blocked until I close Teststand

Can someone explain me this behavior and give me a hint how to release the C-Code Project,

so that it can be "rebuild" after the Teststand sequence run?

Thanks

[Duffy2007]

Hello InVI_MaW,

How you can debug your Visual Studio Project into TestStand.

1. Open TestStand

2. Open the Visual Studio project

3. In Visual Studio under "Debug" attach your project manual to the SeqEdit.exe

4. Run your Sequence File in TestStand with a breakpoint on the position

    you want to step into your Visual Studio Code

5. Step into the Visual Studio code

6. Continue Visual Studio

7. Run the TestStand sequence to the end

8. Under "File" in TestStand "Unload all Moduls"

9. In Visual Studio under "Debug" Detach the process

I hope this helps.