> Hi there! > > Is it possible to attach the Visual Studio .NET debugger to a sscli > executable and use it to step into the rotor source code when debugging?
Yes it is possible: See: http://msdn.microsoft.com/msdnmag/issues/02/07/SharedSourceCLI/default.a spx for details > Besides that, how do I build the sscli source code to be able to step into > the that source code when debugging with cordbg? Also covered in the article - you need to run "env checked" (or env "fastchecked" which I don't really recommend for debugging) before you run buildall.cmd. Jason
