tag:blogger.com,1999:blog-5384857.post5890876888424491354..comments2023-10-10T03:52:55.494+01:00Comments on Under The Stairs: PowerShell and .NET Framework – Similarities and Differences!Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5384857.post-15288049294509768622021-06-02T12:21:45.673+01:002021-06-02T12:21:45.673+01:00I assume it;s a bit pattern.
12,229, in hex os 0x...I assume it;s a bit pattern.<br /><br />12,229, in hex os 0x3000 and in bonary 11 0000 0000 0000<br /><br />Without looking closely, I assume those bits are relevant to the API/ENUM.<br /><br />Thomas Leehttps://www.blogger.com/profile/05591926562143348089noreply@blogger.comtag:blogger.com,1999:blog-5384857.post-68230599452919359562021-02-28T08:04:02.657+00:002021-02-28T08:04:02.657+00:00Hi Thomas, I have been playing with Powershell and...Hi Thomas, I have been playing with Powershell and the .NET Framework and I found something that is puzzling me. Can you think of why the Net.SecurityProtocolType enum would have constants of 48,192,768,3072 and 12288? Values of 1,2,4,8,16 etc would suffice for bitwise operations so I feel like I'm missing something.<br /><br />WillWillhttps://www.blogger.com/profile/03387921294428537675noreply@blogger.com