>My concern isn't for the memory footprint but for the overhead of loading it over and over in Web applications. It's a large runtime and loading it over and over takes up a lot of machine resources.
>
>Again, for some low impact things you do for administration this isn't going to matter. But trying to write file output this way for example? I don't think so...

In my experience, I haven't noticed any performance loss when using WSH.

Did you try to keep it in memory all the time? By adding it to the well known dlls? Or by keeping an object in the Session object?

Vlad