Ok, here's an idea.
Create a script that will sweep a certain configured (in Windows registry) directory for files named *.js, *.vb. Maybe scan them for special comment line to get nice description, or use some xml catalog for scripts. Then display the floating window with the list of available scripts. At this point .NET engine started and grabbed the necessary memory, so running subsequent scripts from this window is faster. Also, proper programming will allow to organise scripts in this window nicely: cascaded lists, sorting, etc.
Still clumsy and only useful if you have a lot of scripts and run them on a regular basis.
Anyway, just wanted to share.
Alexei
Create a script that will sweep a certain configured (in Windows registry) directory for files named *.js, *.vb. Maybe scan them for special comment line to get nice description, or use some xml catalog for scripts. Then display the floating window with the list of available scripts. At this point .NET engine started and grabbed the necessary memory, so running subsequent scripts from this window is faster. Also, proper programming will allow to organise scripts in this window nicely: cascaded lists, sorting, etc.
Still clumsy and only useful if you have a lot of scripts and run them on a regular basis.
Anyway, just wanted to share.
Alexei