Not sure, but have you considered the simple solution: Give developers of
the custom assemblies a "debug" (/optimize-) version of your program to debug
against? You don't have to give them the symbol (pdb) files for this to
work...
> Hi,
>
[quoted text clipped - 18 lines]
>
> Dierk Droth
Dierk Droth - 03 Jul 2006 14:07 GMT
Thanks for your reply.
Yes, I'm aware of this option. However this is quite cumersome, since
a) I had to provide a debug version ;-)
b) the user had to restart the app using this debug version. Note: my app
provides .NET scripting, so the user can edit, compile and run within the
app. But then had to start to debug.
I also considered providing a GetXXX() method for any XXX property, since
the optimizer probably won't optimize these methods away (have not yet tested
though). However, clumpsy as well ...
Any other ideas?
Thanks
Dierk Droth
> Not sure, but have you considered the simple solution: Give developers of
> the custom assemblies a "debug" (/optimize-) version of your program to debug
[quoted text clipped - 23 lines]
> >
> > Dierk Droth