Your intuition that you're running a kind of script that can be stopped is
leading you astray. :)
When you program in IronPython, it's very much like programming in C# -- the
objects you create will stay alive until they are garbage collected or the
program ends. So to unhook the delegate from
An alternate plan would be to run your script in another app domain. Then you
can just unload the app domain and all shared state will be cleared. The
hosting APIs make this pretty easy to do as well.
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On
Caglar Toklu wrote:
Hi to all,
We are developing our product depending on another DLL acting as Database
Layer. I have searched this forum and found the following posts:
http://www.nabble.com/-IronPython--Application.config-td14159166.html#a14159166
