Re: why write a script when u can write a vb6 app

From: Richard Mueller [MVP] (rlmueller-NOSPAM_at_ameritech.NOSPAM.net)
Date: 03/31/04 

Date: Tue, 30 Mar 2004 19:55:46 -0600

"Jordan Mills" <usenet at jordan mills dot net> wrote in message
news:%23rf29AoFEHA.696@TK2MSFTNGP12.phx.gbl...
>
> "R Giskard Reventlov" <rgiskard@nospam.com> wrote in message
> news:OCRt1YnFEHA.580@TK2MSFTNGP11.phx.gbl...
> > Ofcourse writing a script is easier and faster, but writing an app using
> VB
> > 6 is also not that difficult.
> > And I get to use visual studio which is much much better than using text
> > editor or some other not so good editors.
> >
> > What are the things that can NOT be done in a VB 6 app that could be
done
> in
> > vbscript/wsh ?
> > Thoughts?
> >
> > -R Giskard
> >
> Because nobody can see what it does, take it apart, modify it, or upgrade
it
> if it's an exe file.
>
Hi,

To be honest, the only time I code in VB is when I don't want people to see
my code. Because I have to assume that only I will modify a VB app, I spend
a great deal more time making sure it is rock solid, accounting for
everything that could ever possibly go wrong. I also tend to expose more
public attributes, so people can adjust things like timeout values. I also
spend considerable time documenting how to use the app. With a script, I
figure a knowledgeable person can do whatever, as long as I added enough
comments. They can even cut and paste parts from several sources to meet
requirements I never anticipated. Still, it's perhaps a matter of taste.

The only situation that comes to mind where something can be done in one and
not the other is to declare byte arrays, although I'm sure there are others.
VBScript can deal with byte arrays, but cannot declare or modify them. Since
VBScript is a subset of VB, almost by definition anything that can be done
in VBScript can be done in VB. However, I recall people having trouble
duplicating the Wscript.Sleep method. 

-- 
Richard
Microsoft MVP Scripting and ADSI
HilltopLab web site - http://www.rlmueller.net
--

Relevant Pages

  • Re: why write a script when u can write a vb6 app
    ... > Ofcourse writing a script is easier and faster, ... > What are the things that can NOT be done in a VB 6 app that could be ... Both may be key requirements for unattended, scheduled script execution, ... support cross-platform job dependency chains based on exit codes. ...
    (microsoft.public.scripting.vbscript)
  • RedirectStandardOutput & OpenTextFile Conflict
    ... of the standard output after that call is made. ... VBScript output via CSript.exe ... ' Include Library Script ... the C# app picks up the Echo's just fine. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: RedirectStandardOutput & OpenTextFile Conflict
    ... of the standard output after that call is made. ... VBScript output via CSript.exe ... ' Include Library Script ... the C# app picks up the Echo's just fine. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Passing Data Between Applications
    ... you never said if your .net app is running on all of the client's machines ... if you want/need the vbscript to start your app. ... this script is provided by out telecom provide. ... > My aim is to pass data from this vb script to my .net app. ...
    (microsoft.public.dotnet.general)
  • Re: why write a script when u can write a vb6 app
    ... > Ofcourse writing a script is easier and faster, ... > editor or some other not so good editors. ... > What are the things that can NOT be done in a VB 6 app that could be done ...
    (microsoft.public.scripting.vbscript)