DotNet equivlant of vb 6 instr

what is the equivlant of the vb 6 instr

I have a string there has "*D*N"
I want to find the position that the D is in with a dotnet (VB) function

Hi Brian,You might not believe it, but you can use InStr ;-)Strings.

Hi Brian,

You might not believe it, but you can use InStr ;-)

Strings.InStr

If you want to go the .NET way, then you might want to use Strings.IndexOf.

Please note that like in VB6, InStr is 1-based while IndexOf is 0-based.

Best regards,

Martin

Am 30.03.2008 11:22, Brian schrieb:

DotNet equivlant of vb 6 instr

http://msdn2.microsoft.com/en-us/library/microsoft.visualbasic.strings.instr.aspx

As you see this method is part of the VB.Net syntax , so i guess you would
bether refrace that comment as
if you want to abandon the VB namespace   .

if you want to do this
http://www.codeproject.com/KB/vb/novbruntimeref.aspx    ( see my comments on
Rafael for further detail )

Then it might be bether to use only the comonly shared framework classes
although , there is nothing that keeps a C# , J# , etc etc etc ( other
framework languages ) from setting a reference to the microsoft visual basic
dll and use the handy VB methods ,   note that this dll is NOT for backwords
compatibility !! but contains specific VB methods ( shortcuts , behaviors ,
Contstants  )  that are part of the VB namespace and in it`s turn is  part
of the  Framework


Michel

I once heard that those VB methods would be removed in future versions of vb.

I once heard that those VB methods would be removed in future versions of
vb.net.  I am using VB.2005 and have not seen vb2008.  Do you know if what I
heard is true, or just a rumour?
Brian

Well in VB.

Well in VB.Net 2008  they are still there  , and i  personally can`t
inmagine that they would be removed unless MS would fase out VB wich is not
likely to happen


HTH

Michel

DotNet equivlant of vb 6 instr

That's FUD.

As Michel said, the msvb namespace is part of the framework. That means it is
there forever in 2.0, 3.0, and 3.5. If some future version of the framework
drops them, just stick to the versions that already have it. ;-)

DotNet equivlant of vb 6 instr

Nonsense.  They are part of Visual Basic and they have even survived the
transition from VB6 to VB.NET, so there is no reason for removing them.  In
addition, they are well-tested code.

--
M S   Herfried K. Wagner
M V P  <URL:http://dotnet.mvps.org/>
V B   <URL:http://dotnet.mvps.org/dotnet/faqs/>

DotNet equivlant of vb 6 instr

what I

It's confusion.  Microsoft.VisualBasic will always be there.  It's
what makes VB.NET, well, VB.NET.  What is likely to be removed at some
point (and probably not in the immediate future) is
Microsoft.VisualBasic.Compatability - which is the library used to
contains some of the deprecated VB methods to VB.NET

--
Tom Shelton

Perhaps a misunderstanding.

Perhaps a misunderstanding. I never seen that so this is what I would called
a rumour... It's true though that some of the VB specific helpers are not
included in the compact framework...

So if plan to target the compact framework, it could make sense to avoid
using some of those VB specifics features....

--
Patrice

DotNet equivlant of vb 6 instr

Take a look in the help files.  They tell you which parts of the language
are included in the compact framework.

Mike.