VB Reference

  • Thread starter Thread starter CGW
  • Start date Start date
C

CGW

I'm really, really frustrated. For some reason, help in Visual Studio
always brings up SQL help. I simply want a VB.Net reference for
functions like Left(), Right(), etc and I cannot find one anyway... what
I found on MSDN sucks. Anybody know where I can find a simple list of
string functions? Please.

Thanks,

CGW
 
CGW said:
Nevermind... I was able to get what I needed under VBScripting.
Click to expand...

Be careful, this may be the documentation for VBScript and not VB.NET, which
are entirely different programming languages.
 
entirely?

Cor

Herfried K. Wagner said:
Be careful, this may be the documentation for VBScript and not VB.NET,
which are entirely different programming languages.
Click to expand...
 
Cor Ligthert said:
if YourStateMent = true then
ShowMeThisOneInVBS
End if
Click to expand...

You are picking a trivial sample which is almost similar in VBScript and
VB.NET. However, there is absolutely no guarantee that anything mentioned
in the documentation on VBScript will work the same way in VB.NET. There
are many subtle differences between the two programming languages.
 
True, but I agree with Cor. VBScript is a scaled back version of VB 5 (not
6). However, the fundamental language core when you remove the IO features
has not changed from VB 4 to VB 2005. 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.

As for OP's question, the VS 2005 local help system is easily confused. I
frequently get SQL Server or MS Office help pages instead of the help for
the VB or C# keyword I'm looking for. The on-line help is worse and
frequently returns help for environments I don't even have installed. I
suspect this is not a problem in the help system, but is an IDE issue where
it specifies the wrong development environment.

Mike.
 
Michael D. Ober said:
VBScript is a scaled back version of VB 5 (not 6).
Click to expand...

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.
Click to expand...

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.
Click to expand...

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.
 
Back
Top