Which one is better to use? CInt(string) or Integer.Parse(string)? thanks!

* "Brian Henry" <(E-Mail Removed)> scripsit:
> Which one is better to use? CInt(string) or Integer.Parse(string)? thanks!

Personal preference.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

"Brian Henry" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...

> Which one is better to use? CInt(string) or Integer.Parse(string)? thanks!

Depends on whether you want to retain the VB "feel" or go hardcore Framework
all the way.

been trying to knock out all the old vb stuff out of my head so sounds like
the parse one is good to go with


"Jeff Johnson [MVP: VB]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Brian Henry" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
> > Which one is better to use? CInt(string) or Integer.Parse(string)?
thanks!
>
> Depends on whether you want to retain the VB "feel" or go hardcore
Framework
> all the way.
>
>

Brian,
I would use CInt, unless I specifically needed to use Integer.Parse. As
Herfried stated its largely personal preference.

For details on CInt vs. Integer.Parse and details on other myths about
avoiding VB in your VB.NET see:

http://www.panopticoncentral.net/arc...5/31/1100.aspx

http://www.panopticoncentral.net/arc...6/07/1200.aspx

Hope this helps
Jay


"Brian Henry" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Which one is better to use? CInt(string) or Integer.Parse(string)? thanks!
>
>

* "Brian Henry" <(E-Mail Removed)> scripsit:
> been trying to knock out all the old vb stuff out of my head so sounds like
> the parse one is good to go with

'CInt' is not "old vb". It's current VB syntax that /should/ be used
/instead/ of the framework functions whenever possible. That's why we
have these commands.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

I agree that Integer.Parse is the wrong thing to use - but CType(xx,
Integer) is functionally identical to CInt - and if you happen to not have
Microsoft.VisualBasic referenced... it's fine
_______________________________
The Grim Reaper

"Herfried K. Wagner [MVP]" <hirf-spam-me-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> * "Brian Henry" <(E-Mail Removed)> scripsit:
> > been trying to knock out all the old vb stuff out of my head so sounds
like
> > the parse one is good to go with
>
> 'CInt' is not "old vb". It's current VB syntax that /should/ be used
> /instead/ of the framework functions whenever possible. That's why we
> have these commands.
>
> --
> Herfried K. Wagner [MVP]
> <URL:http://dotnet.mvps.org/>

* "The Grim Reaper" <(E-Mail Removed)> scripsit:
> I agree that Integer.Parse is the wrong thing to use - but CType(xx,
> Integer) is functionally identical to CInt - and if you happen to not have
> Microsoft.VisualBasic referenced... it's fine

Both, 'CInt' and 'CType' are VB /keywords/ that should work without
referencing this library.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

any reason specific reason why you suggest i should use CInt instead of the
framework versions? I'm trying to maintain as much compatability in tearms
of code with C# incase they ever want this code directly coverted over to
it..


"Herfried K. Wagner [MVP]" <hirf-spam-me-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>* "Brian Henry" <(E-Mail Removed)> scripsit:
>> been trying to knock out all the old vb stuff out of my head so sounds
>> like
>> the parse one is good to go with
>
> 'CInt' is not "old vb". It's current VB syntax that /should/ be used
> /instead/ of the framework functions whenever possible. That's why we
> have these commands.
>
> --
> Herfried K. Wagner [MVP]
> <URL:http://dotnet.mvps.org/>

Hi Brian,

One of the things in the language itself where VB is much better than all
the other languages in dotNet are the *convert* functions.

You have the change to use that benefit, not using them is for me the same
as getting a million and not accepting it because it is not given to
everybody.

Just my thougth,

Cor