Slick-c debugger does not stop at breakpoints

[DaveR]

Hi all, I'm very new to Slick-c, and want to just write a small macro to process a buffer.  I figured I could use the debugger to step through the macro as it runs but I can't get it to stop at any breakpoint.
I found a couple of posts on this and the correct procedure to debug seem to be the following (or at least this is what I'm doing):

1. write your macro and save that file
2. menu   Macro\Start Slick-C Debugger
3. in the new instance of VS that starts, open your my_new_macro.e file
4. set break point on the line you like with f9 (note red dot appears)
5. switch back to original instance of slick edit and then run your macro.  I hit escape, then just type my_new_macro

The macro runs.  Does almost what I want, but does not stop at a breakpoint.

I'm missing something here.   Any information would be helpful.

thanks,
DR

[chrisant]

Have you tried setting a bp on the first line of the macro?  (To rule out conditional code flow).

[DaveR]

Thanks for the reply.  Yes - I've tried in various spots including the first line.
Other info:
SlickEdit 2012 (v17.0.3.0 64-bit)
Build Date: November 27, 2012
Emulation: Brief
OS: Windows 7 x64
OS Version: 6.01.7601  Service Pack 1
Memory: 43% Load, 5352MB/12278MB Physical, 5434MB/24556MB Page File, 520MB/8388607MB Virtual
Shell Info: C:\Windows\system32\cmd.exe /q
Screen Size: 2560 x 1600, 1680 x 1050

Project Type: Microsoft Visual Studio Visual C++
Language: .cpp (C/C++)

[DaveR]

One more thing if anyone can please assist.  When I start the slick-c debugger I get at warning message:
"project 'c:\users\ ... \ My SlickEdit Config\17.0.3\SCDebug\project.vpe' should have a .vpj extension
?
DR

[DaveR]

Got it working.  It just started working when I moved my .e files to a sub directory of the Slickedit install directory.  I couldn't get it to work if they were in a "my documents"\slick_c directory, but it all works as advertised when they are in Program Files\SlickEidtV17.0.3 x64\macros\UserMacros

Regardless.  I'm happy it is working now.
DR