You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* 10/11/2022 AM Publish (#4570)
* Document ARM64 unwind handling for return address signing
* Update date, fix step numbers
* Fix style, grammar in Arm64 Exception
Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
* example needed to mitigate dev floundering (MicrosoftDocs#4210)
It is not easy to match up variant vt types with POD types. Especially since there is a gradual transition to modern C++. I used a number of dev hours on attempts to match the variant type, vt, to make the true/false work. The m_bValue type for the simple property was a BOOL type, but trying to create a variant of type BOOL directly didn't work. Only by looking at VC Sample code for VisualStudioDemo did I see the (_variant_t)true construct, which becomes the standard_cast contruct in modern C++. I figured my Example code could make other programmer's efforts easier.
Co-authored-by: Taojunshen <[email protected]>
Co-authored-by: opbld17 <[email protected]>
Co-authored-by: Colin Robertson <[email protected]>
Co-authored-by: opbld16 <[email protected]>
Co-authored-by: opbld15 <[email protected]>
Co-authored-by: Martin Storsjö <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: rtischer8277 <[email protected]>
0 commit comments