Re: debugging

I will give this a try and certainly keep everyone posted.  I tried
compiling to disk earlier and using the compiler context to retrieve
the generated assembly.  You are suggesting the use of
Assembly.LoadFrom and that may make the difference for me in getting
the debugger to work.  I will try this tomorrow morning.

And when that is working, then I'm onto the fun of getting my script
interface working and executing in another AppDomain.  I suspect it
won't be an issue for Boo at all, but for the rest of my object model.

FYI, I've embedded Boo in a proprietary 3-D parametric CAD application
that my company develops.  It's related to the product for sale at
http://www.dpearth.com

Thanks for your help (and to all the others as well).  Boo has a
really great community.

On 9/13/05, Rodrigo B. de Oliveira 
<rodrigobamboo-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:
> On 9/13/05, Clint Miller 
> <clintmiller-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:
> > Can anyone give some guidance on this scenario: I've embedded Boo as a
> > scripting platform in an application.  It is using the CompileToMemory
> > pipeline (by design choice).  I want to set a breakpoint (for now, I'm just
> > inserting a call to System.Diagnostics.Debugger.Break()) and run the script.
> >  When I run the script, visual studio does stop at that point, however it
> > doesn't have any sources for that point.  I've confirmed that it is
> > generating a PDB for my script file.
> >
> >  Any suggestions? Thanks!
> >
> 
> Apparently only .net 2.0 will have the capability of debugging in
> memory assemblies.
> 
> Right now I think you would have to go the (already suggested) route
> of emitting the assemblies to disk and loading the code with
> Assembly.LoadFrom to get the debugger to break on your breakpoints.
> 
> Please, let us know of how this works (or not) for you.
> 
> --
> bamboo
> http://blogs.codehaus.org/people/bamboo/
> Got objects? http://www.db4o.com/
>