Another OT: .Net=>WB

[spl]

This is an aside from the previous WOL thread that Tony ended quit effectively. The focus is the code for creating a byte array from hex. Curiosity for how that could be easily accomplished in .NET lead me to an unadvertised object System.Runtime.Remoting.Metadata.W3cXsd2001.SoapHexBinary

So I can get this far

Code Select Expand

hex = '1A:2B:3C:4D:5E:6F'
ObjectClrOption('useany','System')
cvt = ObjectClrNew('System.Runtime.Remoting.Metadata.W3cXsd2001.SoapHexBinary')
hex = StrReplace(hex,':','')
result = cvt.Parse(hex)
Message("",result)

but there is a Value Property and in PS

Code Select Expand

$result = ([System.Runtime.Remoting.Metadata.W3cXsd2001.SoapHexBinary]::Parse($hex).Value)

will return the byte array as text. I'm sure WB CLR can return the Value property but not sure if the return from .Parse() should be treated as a pointer or an object.

[td]

If you look at the documentation for SoapHexBinary, Parse returns an object of type SoapHexBinary. SoapHexBinary has a property named "Value." So proper usage would be

Code Select Expand

aBytes = Result.Value
Of course, if you used WinBatch Studio, the variable types would be self-evident in the variable watch window.

[spl]

I believe my original post specified that .Value was a property. So, if using your suggestion

Code Select Expand

hex = '1A:2B:3C:4D:5E:6F'
ObjectClrOption('useany','System')
cvt = ObjectClrNew('System.Runtime.Remoting.Metadata.W3cXsd2001.SoapHexBinary')
hex = StrReplace(hex,':','')
result = cvt.Parse(hex)
aBytes = result.Value
Message("",aBytes)

you get the attached, ergo back to my original question as to how to decode the .Parse() object