"Michael D. Ober" <obermd.@.alum.mit.edu.nospamschrieb:
VBScript is a scaled back version of VB 5 (not 6).
Well, that's a fact, and thus I agree.
However, the fundamental language core when you remove the IO features has
not changed from VB 4 to VB 2005.
What do you consider the "fundamental language core"?
Arrays have been changed.
Properties have been changed.
Classes and UDTs (now called structures) have been changed
'ByVal'/'ByRef' as the default passing mode have been swapped.
'As New' has changed its semantics.
....
In some ways, a VBScript developer will actually have an easier time
moving to VB 2005 because the dotNet IO methods appear to have been
modeled after the Windows Scripting FileSystemIO class.
Using a class I have never used before was never a problem for me -- I just
open the documentation, check out the members, their descriptions, and
samples illustrating their usage. However, my concern was about using the
VBScript documentation when programming in VB.NET: As I stated, there are
many little differences. 'Replace', for example, has changed slightly,
'String' has been renamed to 'StrDup', ... That's why I'd really recommend
to use the VB.NET documentation when using VB.NET.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>