DotNet equivlant of vb 6 instr

[Brian]

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

[Martin H.]

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:

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

[Steve Gerrard]

Brian wrote:

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

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. ;-)

[Tom Shelton]

On Mar 30, 7:42*am, "Brian" <[e-mail]:

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

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

[Herfried K. Wagner [MVP]]

"Brian" <bs********@community.nospamschrieb:

>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?

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/>

[Patrice]

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

"Brian" <bs********@community.nospama écrit dans le message de news:
OS**************@TK2MSFTNGP06.phx.gbl...

>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

[Michael D. Ober]

"Patrice" <http://www.chez.com/scribe/wrote in message
news:ur*************@TK2MSFTNGP04.phx.gbl...

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

"Brian" <bs********@community.nospama écrit dans le message de news:
OS**************@TK2MSFTNGP06.phx.gbl...

>>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

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

Mike.