I can reproduce this 1 line all the time & I'm thrown off why .Net 8 x64 is converting to a negative decimal. BigIntegers have to be used because of the hex sizes. Conversion URL fact checking .Net BigInteger.Parse

BigInteger.Parse("D0752364CFB600E410619304BE135C", System.Globalization.NumberStyles.HexNumber).ToString()

2 Examples:

• Hex: 9F4F4108B0BC1F2E02662669A635B9C
• Wrong .Net conversion: -8032725318385391486974673232284394596
• Correct conversion: 13234922614173262479486239732201118620
• Pad 0s & .Net converts correctly: 0000009F4F4108B0BC1F2E02662669A635B9C
• .Net Padded 0s conversion: also 13234922614173262479486239732201118620

• Hex: D0752364CFB600E410619304BE135C
• Wrong .Net conversion: -246854403100748367549686509950069924
• Correct conversion: 1082373592684167505354120550330274652
• .Net padded 0s converts correctly: also 1082373592684167505354120550330274652

& my list goes on with wrong .Net BigInteger.Parse issues. It's that 1 single line involved.

Anyone around with some suggestions?

I have workarounds but I don't like sloppy band-aids

I can reproduce this 1 line all the time & I'm thrown off why .Net 8 x64 is converting to a negative decimal. BigIntegers have to be used because of the hex sizes. Conversion URL fact checking .Net BigInteger.Parse

BigInteger.Parse("D0752364CFB600E410619304BE135C", System.Globalization.NumberStyles.HexNumber).ToString()

2 Examples:

• Hex: 9F4F4108B0BC1F2E02662669A635B9C
• Wrong .Net conversion: -8032725318385391486974673232284394596
• Correct conversion: 13234922614173262479486239732201118620
• Pad 0s & .Net converts correctly: 0000009F4F4108B0BC1F2E02662669A635B9C
• .Net Padded 0s conversion: also 13234922614173262479486239732201118620

• Hex: D0752364CFB600E410619304BE135C
• Wrong .Net conversion: -246854403100748367549686509950069924
• Correct conversion: 1082373592684167505354120550330274652
• .Net padded 0s converts correctly: also 1082373592684167505354120550330274652

& my list goes on with wrong .Net BigInteger.Parse issues. It's that 1 single line involved.

Anyone around with some suggestions?

I have workarounds but I don't like sloppy band-aids

• parsing
• hex
• biginteger

• This question is similar to: Converting a hex string to its BigInteger equivalent negates the value. If you believe it’s different, please edit the question, make it clear how it’s different and/or how the answers on that question are not helpful for your problem. – Charlieface Commented Nov 20, 2024 at 16:28

1 Answer 1

This is the documented behavior:

If value is a hexadecimal string, the Parse(String, NumberStyles) method interprets value as a negative number stored by using two's complement representation if its first two hexadecimal digits are greater than or equal to 0x80. In other words, the method interprets the highest-order bit of the first byte in value as the sign bit. To make sure that a hexadecimal string is correctly interpreted as a positive number, the first digit in value must have a value of zero. For example, the method interprets 0x80 as a negative value, but it interprets either 0x080 or 0x0080 as a positive value.

So the method is working as documented, just not the way you'd like it to work. If you want the value to always be interpreted as a positive value, just prepend "0".