• Introduction
• Response Debugging
• Application Debugging
• Tips

Introduction

Most problems can be solved without using the debugger.

See the troubleshooting section first. Then try the debugger.

Since tradelink is open source, it's easy to debug problems.

Response Debugging

1. Obtain source code
2. install an ide if you haven't already
3. Open the TradeLinkSuite.sln file in c# express File->Open Solution
4. On project->Configuration Manager menu, change the solution from Release to Debug build
5. Build the project in debug mode
6. Close the solution
7. Open your response project (eg Resposnes.csproj).
8. Switch to debug mode in same way as above and build project.
9. Determine which tradelink application (Gauntlet/kadina/asp) you wish to debug with Response.
10. In solution explorer window, right click on solution and choose add project existing.
11. Browse to location where you saved tradelink source code in step #1
12. Locate the folder that corresponds to TradeLink application youwish to debug (eg Gauntlet)
13. Add project file from this application
14. Set a breakpoint in either application code or your Response code
15. Breakpoints determine where program will stop executing so you can examine output
16. You can set or unset a breakpoint by clicking on line number next to a line of code
17. when setting a breakpoint, a red dot will appear. If you do it again, it should disappear
18. Once you have set breakpoint, right click on Application and choose right click -> debug
19. the application will start
20. load your response, making sure to choose the debug path to your response
21. (eg ResponseFolder\bin\Debug rather than ResponseFolder\bin\Release)
22. When your breakpoint is hit, execution will stop and you can inspect variables inside your program
23. To continue executing, hit F5. You can also remove or set new breakpoints while debugging

TradeLink Application Debugging

1. Obtain source code
2. install an ide if you haven't already
3. Open the TradeLinkSuite.sln file in c# express File->Open Solution
4. On project->Configuration Manager menu, change the solution from Release to Debug build
5. Build the project in debug mode
6. Close the solution
7. Open your application project/solution (eg MyApp.sln).
8. Switch to debug mode in same way as above and build project.
9. Set a breakpoint in your application code
10. Breakpoints determine where program will stop executing so you can examine output
11. You can set or unset a breakpoint by clicking on line number next to a line of code
12. when setting a breakpoint, a red dot will appear. If you do it again, it should disappear
13. Once you have set breakpoint, right click on Application and choose right click -> debug
14. your application will start
15. When your breakpoint is hit, execution will stop and you can inspect variables inside your program
16. To continue executing, hit F5. You can also remove or set new breakpoints while debugging

Tips

• You can set breakpoints in your code or in tradelink code (or both), depending on what you wish to inspect
• You can add a variable to watch list by right clicking it and choosing add watch.
• If you wish to debug common libraries, you should also add TradeLinkAPI TradeLinkCommon and potentially TradeLinkAppKit or TradeLinkResearch depending on what you're testing