I posted a reply on the newsgroup. Essentially, I think you need to Step Into rather than Start the .exe to cause the execution to stop on the first line of source and thus to bring in the debug info.
-----Original Message----- From: Yahya H. Mirza [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 9:27 AM To: [EMAIL PROTECTED] Subject: Problem launching VS debugger on Rotor Codebase, Note: This thread was posted to MS sscli newsgroup as well. Hi, I recently read a great MSDN article on Rotor by Jason Whittington, which described a command line argument to pass to Visual Studio to launch the VS Debugger to debug Unmanaged Code. The command line string was: devenv /debugexe \sscli\build\<buildversion>\clix.exe hello.exe Everytime I enter this string with the appropriate path for clix, I launch the Visual Studio Environment, but I can't seem to get the debugger to start ? Could somebody please tell me what I may be doing wrong here ? Thanks, Yahya Mirza Aurora Borealis Software
