vb6 - Is using the windows scripting runtime, especially the FileSystemObject thereof a good idea? -

Recently I have been asked to do some maintenance on the VB6 application. It contains some file Io, I get an IO operation while referring to the Windows Script Host and the filesystem object makes it very friendly compared to the IO operation with VC6.

But what is the problem with the security problems or the problem that the script host will be disabled on some users' computers?

Update (August 20, 2012): Since asking this question, we have faced the problem of a non-functional scrrun.dll between 3000 customers. We had to fix them manually through remote support. It seems that sometimes a virgin has to blame.

As Robert Harvey described in his comment, usually a problem in practice is possible That scrrun.dll can not be properly registered on a machine either on a machine installed, while we have faced both scenarios while installing our own VB6 application on the customer's machines.

To disable scripting, we actually run with other applications (such as Microsoft InfoPath) in this problem, and the Infage form (whatever file I / O) calls a VB6 DLL Which used the WSH filesystem object , so if you can work with VB6, you can actually work as script security problems by using the library. As far as I know, WSH security settings typically apply to actual scripts, not for programs that use components of scripting runtime.

In fact, you can use WSH components, such as FileSystemObject , from a VB6 application.