Phil,
If your on VS 2005, check out my generic IIf (link previously posted), you
can simplify your statement to:
| Dim PurchaseType As String _
| = IIf( drwData.Item("D ailyItem").Equa ls( "True" ) _
| , "ID" _
| , "PID" _
| )
The above line is with Option Strict On! My generic IIf uses generics & type
inference to "create" a "IIf(boolea n, String, String) As String" as needed
and call it, no ugly DirectCast needed, no boxing of value types. Totally
Option Strict On friendly!
Of course there may be side effects...
Consider the following:
' note we are explicitly setting the seed values in each case to
' ensure we get the same sequence of pseudo random numbers back.
Dim falseCounter As New Random(1)
Dim trueCounter As New Random(2)
Debug.WriteLine (IIf(True, trueCounter.Nex t(), falseCounter.Ne xt()),
"true")
Debug.WriteLine (IIf(False, trueCounter.Nex t(), falseCounter.Ne xt()),
"false")
In VB it displays:
true: 1655911537
false: 237820880
While in alleged direct equivalent in C#:
Random falseCounter = new Random(1);
Random trueCounter = new Random(2);
Debug.WriteLine (true ? trueCounter.Nex t() : falseCounter.Ne xt(),
"true");
Debug.WriteLine (false ? trueCounter.Nex t() :
falseCounter.Ne xt(), "false");
Displays:
true: 1655911537
false: 534011718
Notice that the second line doesn't match, this is because VB called the
falseCounter.Ne xt function twice (once on each line), while C# only called
it once (only on the second line).
If instead of IIf we use the code that Sean gave:
Dim value As Integer
If True Then
value = trueCounter.Nex t()
Else
value = falseCounter.Ne xt()
End If
Debug.WriteLine (value, "true")
If False Then
value = trueCounter.Nex t()
Else
value = falseCounter.Ne xt()
End If
Debug.WriteLine (value, "false")
We then get the same results as C#:
true: 1655911537
false: 534011718
Consider what happens if instead of calling Random.Next() you are calling a
GetNextSequence Number function, that simply increments a counter & return
it,
id = IIf(sequenceAlr eadyExists, theExistingSequ ence,
GetNextSequence Number())
For example you are creating records from some input source and if the
record doesn't have an ID you call GetNextSequence Number to assign a new
one. The above line in VB will cause gaps in the sequence number, as is
called for every "line" in the input source. Consider what happens if the
GetNextSequence Number() function is fairly expensive (performance, memory
pressure, network, other) to execute.
As I stated, in the case of constants like the OP & your example, using IIf
doesn't hurt, however I strongly recommend any one using IIf to understand
what it is actually doing!
--
Hope this helps
Jay [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley -
http://www.tsbradley.net
"Phill W." <p-***********@o-p-e-n.a-c.u-k> wrote in message
news:dr******** **@yarrow.open. ac.uk...
| ".Net Sports" <ba********@cox .net> wrote in message
| news:11******** *************@g 43g2000cwa.goog legroups.com...
| >I need to convert some C# ?Conditionals over to vb.net
| >
| > string PurchaseType = (Convert.ToStri ng(drwData["DailyItem"]) ==
| > "True") ? "ID" : "PID";
|
| The direct equivalent of the "?" operator is Visual Basic's IIf function:
|
| Dim PurchaseType As String _
| = DirectCast( IIf( drwData.Item("D ailyItem").Equa ls( "True" ) _
| , "ID" _
| , "PID" _
| ), String )
|
| (line breaks for clarity(?) only)
|
| HTH,
| Phill W.
|
|
