vbscript >> best practices

by Lynn » Sun, 30 Oct 2005 12:38:14 GMT

whats the best practices for managing scripts?
do you guys make use of .wsf to call scripts or do you only write your
scripts in a .vbs file?

vbscript >> best practices

by Lynn » Thu, 03 Nov 2005 11:19:55 GMT

whats the best practices for managing scripts?
do you guys make use of .wsf to call scripts or do you only write your
scripts in a .vbs file?

vbscript >> best practices

by de Graff » Thu, 03 Nov 2005 23:21:49 GMT

It depends. For quick and dirty scripts, or scripts that don't reference
other scripts I use .vbs. If I have to get fancier and create scripts that
have to include other code (from my script library) I use .wsf.

Similar Threads

1. Good resource for Classes - best practices - Visual Basic/VB

2. Best Practices for DataAccess Layer in VB6

I am trying to conceptualize the best approach to handle data access 
throughout my VB6 app.  As it is now, I have been creating ClassModules for 
each specific ADO recordset, which is just fine but I end up with many 
ClassMod's (took the "NamesData" example from MSDN and re-built this for each 
ADOrs I needed to access).

Anyway...  Just wondering if there are other, perhaps better organized ways 
to structure the DataAccess process.  

Your comments, insights, and ideas are greatly appreciated!


3. Best practices for a handheld application for a visual basic .net application

4. Best practice to lock DB SQLServer records in VB.NET application

5. Best Practice - Destroying objects - VB.Net

6. Database Samples (Best Practices)

Are there any sample projects or web-sites out there that discuss best 
practices with regards to inserting, editing and deleting records in a 
database with VB.Net. I know how I can do all this, I am just looking to see 
some best practice solutions that are out there to get some better ideas on 
how I want to be approaching this. 

Most often it seems when I find something with regards to this topic, it's 
quite limited. I'd like to see some examples of how these utilities are 
implemented to give me some better ideas of how I want to approach this on 
project that will contain many, many tables, thus I want to use as much code 
re-use as possible. 

Thanks, Greg

7. what is best practice to populate large combobox? - VB.Net

8. MDIForm Parent/Child forms BEST Practice

Hi everyone,

could someone give me some thoughts on the best way to manage mdi
parent and child forms?

in vb6 i could scroll through the forms collection and determine which
forms were open/closed and their current state.  now i can't.

before i didn't have to declare numerous named instances each time i
loaded or unloaded a form.

if i open a child form from another child form and try to assign
mdimain as the mdiparent it doesn't permit it, if i say f1.mdiparent =
me.mdiparent i get memory problems (as have others judging from the

all my current forms are declared public shared in mdiMain, but should
these be in a user made forms collection owned by a global module

if i am finished with a child form, i want to unload it, not hide it,
but if i close a form in vb.net it extinguishes the instance.

when the mdi parent closes, i would like the app to terminate.

should i be setting mdi children to nothing or disposing them?

basically, what can/should i do to get the same mdi parent/child
management present in vb6 while still preserving the smallest
footprint possible in memory?

all comments/code greatly appreciated.  i am probably not the only
programmer to ponder this question.