mstorsjo
diff --git a/‎docs/build/arm64-exception-handling.md
Lines changed: 1 addition & 5 deletions b/‎docs/build/arm64-exception-handling.md
Lines changed: 1 addition & 5 deletions
diff --git a/‎docs/c-language/c-operators.md
Lines changed: 0 additions & 2 deletions b/‎docs/c-language/c-operators.md
Lines changed: 0 additions & 2 deletions
diff --git a/‎docs/ide/add-interface-definition-library-property-wizard.md
Lines changed: 122 additions & 0 deletions b/‎docs/ide/add-interface-definition-library-property-wizard.md
Lines changed: 122 additions & 0 deletions
@@ -15,12 +15,10 @@ The exception unwinding data conventions, and this description, are intended to:
 
   - Analyzing the code requires the code to be paged in. It prevents unwinding in some circumstances where it's useful (tracing, sampling, debugging).
 
-
   - Analyzing the code is complex; the compiler must be careful to only generate instructions that the unwinder can decode.
 
   - If unwinding can't be fully described by using unwind codes, then in some cases it must fall back to instruction decoding. Instruction decoding increases the overall complexity, and ideally should be avoided.
 
-
 - Support unwinding in mid-prolog and mid-epilog.
 
   - Unwinding is used in Windows for more than exception handling. It's critical that code can unwind accurately even when in the middle of a prolog or epilog code sequence.
@@ -277,14 +275,12 @@ The array of unwind codes is a pool of sequences that describe exactly how to un
 
 If exceptions were guaranteed to only ever occur within a function body, and never within a prolog or any epilog, then only a single sequence would be necessary. However, the Windows unwinding model requires that code can unwind from within a partially executed prolog or epilog. To meet this requirement, the unwind codes have been carefully designed so they unambiguously map 1:1 to each relevant opcode in the prolog and epilog. This design has several implications:
 
-
 - By counting the number of unwind codes, it's possible to compute the length of the prolog and epilog.
 
 - By counting the number of instructions past the start of an epilog scope, it's possible to skip the equivalent number of unwind codes. We can execute the rest of a sequence to complete the partially executed unwind done by the epilog.
 
 - By counting the number of instructions before the end of the prolog, it's possible to skip the equivalent number of unwind codes. We can execute the rest of the sequence to undo only those parts of the prolog that have completed execution.
 
-
 The unwind codes are encoded according to the table below. All unwind codes are a single/double byte, except the one that allocates a huge stack. There are 21 unwind codes in total. Each unwind code maps exactly one instruction in the prolog/epilog, to allow for unwinding of partially executed prologs and epilogs.
 
 | Unwind code | Bits and interpretation |
@@ -303,7 +299,7 @@ The unwind codes are encoded according to the table below. All unwind codes are
 | `save_fregp_x` | 1101101x'xxzzzzzz: save pair d(8+#X), at `[sp-(#Z+1)*8]!`, pre-indexed offset >= -512 |
 | `save_freg` | 1101110x'xxzzzzzz: save reg d(8+#X) at `[sp+#Z*8]`, offset \<= 504 |
 | `save_freg_x` | 11011110'xxxzzzzz: save reg d(8+#X) at `[sp-(#Z+1)*8]!`, pre-indexed offset >= -256 |
-| `alloc_l` | 11100000'xxxxxxxx'xxxxxxxx'xxxxxxxx: allocate large stack with size \< 256M (2^24 *16) |
+| `alloc_l` | 11100000'xxxxxxxx'xxxxxxxx'xxxxxxxx: allocate large stack with size \< 256M (2^24 * 16) |
 | `set_fp` | 11100001: set up x29: with: `mov x29,sp` |
 | `add_fp` | 11100010'xxxxxxxx: set up x29 with: `add x29,sp,#x*8` |
 | `nop` | 11100011: no unwind operation is required. |
 
@@ -9,10 +9,8 @@ ms.assetid: 13bc4c8e-2dc9-4b23-9f3a-25064e8777ed
 
 The C operators are a subset of the [C++ built-in operators](../cpp/cpp-built-in-operators-precedence-and-associativity.md).
 
-
 There are three types of operators. A unary expression consists of either a unary operator followed by an operand, or the **`sizeof`** or **`_Alignof`** keyword followed by an expression. The expression can be either the name of a variable or a cast expression. If the expression is a cast expression, it must be enclosed in parentheses. A binary expression consists of two operands joined by a binary operator. A ternary expression consists of three operands joined by the conditional-expression operator.
 
-
 C includes the following unary operators:
 
 | Symbol | Name |
 
@@ -0,0 +1,122 @@
+---
+description: "Learn more about: Use a Microsoft Visual Studio wizard to add an IDL property to an IDL interface in your project"
+title: "Add an IDL property"
+ms.date: 04/11/2022
+f1_keywords: ["vc.codewiz.prop.overview", "vc.codewiz.prop.idlattributes"]
+helpviewer_keywords: ["interfaces, adding properties", "properties [C++], adding to interfaces", "names, add property wizard", "IDL attributes", "stock properties, about stock properties", "stock properties"]
+ms.custom: devdivchpfy22
+---
+# Add an IDL property
+
+The **Add IDL Property** wizard adds a method to an interface defined in an Interface Definition Library (IDL). To use the **Add IDL Property** wizard, your project can't support MFC.
+
+For example, if you have an ATL project, and it has an `.idl` file in it, use the following procedure to add a property to an interface.
+
+This wizard differs from the **Add Property** wizard and **Add IDL MFC Property** wizard. The [Add Property](adding-a-property-visual-cpp.md) wizard adds a property to your project. The **Add IDL MFC Property** wizard is specific to MFC, ActiveX, or ATL projects that support MFC.
+
+**To add an IDL property**
+
+1. On the **View** menu, select **Class View**.
+
+1. In [Class View](/visualstudio/ide/viewing-the-structure-of-code), right-click the name of the interface to which you want to add the property.
+
+   > [!NOTE]
+   > You can also add properties to dispinterfaces, which, unless the project is attributed, are nested within the library node.
+
+1. From the shortcut menu, select **Add** > **Add Property**.
+
+1. In the **Add IDL Property** wizard, provide the information to create the property.
+
+1. Select **OK** to add the property.
+
+The `Get` and `Put` methods of the property are displayed as two icons in **Class View**, under the interface where it's defined. You can double-click either icon to view the property declaration in the `.idl` file.
+
+For ATL interfaces, the `Get` and `Put` functions are added to the `.cpp` and `.h` files.
+
+## Add an IDL property wizard
+
+The following section describes the UI that you'll use to add an IDL property:
+
+:::image type="content" source="media/add-interface-definition-library-property-wizard.png" alt-text="Screenshot of adding IDL property to the interface.":::
+
+- **Property name**
+
+  Sets the name of the property.
+
+- **Property type**
+
+  Sets whether your property will have a getter, setter, or both.
+
+- **Return type**
+
+  For ATL interfaces, sets the return type for the property.
+  For dual interfaces, `HRESULT` is always the return type, and select option is unavailable.
+  For custom interfaces, you can select a return type from the list. `HRESULT` is still recommended, as it provides a standard way to return errors.
+
+- **Get function**
+
+  For ATL interfaces, creates the `Get` method for retrieving the property value. Select **Get**, **Put**, or both.
+
+- **Put function**
+
+  For ATL interfaces, creates the `Put` method for setting the property value. Select **Get**, **Put**, or both. If you select **Put function**, you can choose from the following two ways to implement the method:
+
+  |Option|Description|
+  |------------|-----------------|
+  |**propput**|The [PropPut](../windows/attributes/propput.md) function returns a copy of the object. **propput** is the default and the most common way to make the property writable.|
+  |**propputref**|The [PropPutRef](../windows/attributes/propputref.md) function returns a reference to the object, rather than returning the copy of the object itself. Consider using **propputref** option for objects, such as large structs or arrays, that may have initialization overhead.|
+
+- **Parameters**
+
+  Displays the list of parameters added to the property. Each item in the list consists of the parameter name, parameter type, and attributes.
+
+  `in` indicates that the parameter is passed from the calling procedure to the called procedure.
+  `out` indicates that the pointer parameter is returned from the called procedure to the calling procedure (from the server to the client).
+
+- **+**
+
+  Add a parameter. In **Parameters**, type the parameter type and name. For example, `int x`, and select **OK**.
+
+- **x**
+
+  Removes the selected parameter from **Parameters**.
+
+- **Pencil icon**
+
+  Edit the selected parameter.
+
+- **Attributes**
+
+1. `helpcontext`
+
+    Specifies a context ID that lets the user view information about this property in the Help file. For more information, see [helpcontext](/windows/win32/Midl/helpcontext).
+
+1. `helpstring`
+
+    Specifies a character string that's used to describe the element to which it applies. By default, it's set to **`property`**&nbsp;*Property&nbsp;name*. For more information, see [helpstring](/windows/win32/Midl/helpstring).
+
+1. `id`
+
+    Sets the numerical identifier that identifies the property. This option isn't available for properties of custom interfaces. For more information, see [id](/windows/win32/Midl/id).
+
+- **Additional attributes**
+
+Keywords in the Microsoft Interface Definition Language (MIDL) are described in detail in the [MIDL language reference](/windows/win32/midl/midl-language-reference.md).
+
+  |Option|Description|
+  |------------|-----------------|
+  |`bindable`|Indicates that the property supports data binding. For more information, see [bindable](/windows/win32/Midl/bindable).|
+  |`defaultbind`|Indicates that this single, bindable property best represents the object. For more information, see [defaultbind](/windows/win32/Midl/defaultbind).|
+  |`defaultcollelem`|Indicates that the property is an accessor function for an element of the default collection. For more information, see [defaultcollelem](/windows/win32/Midl/defaultcollelem).|
+  |`displaybind`|Indicates that this property should be displayed to the user as bindable. For more information, see [displaybind](/windows/win32/Midl/displaybind).|
+  |`hidden`|Indicates that the property exists but shouldn't be displayed in a user-oriented browser. For more information, see [hidden](/windows/win32/Midl/hidden).|
+  |`immediatebind`|Indicates that the database will be notified immediately of all changes to this property of a data-bound object. For more information, see [immediatebind](/windows/win32/Midl/immediatebind).|
+  |`local`|Specifies to the MIDL compiler that the property isn't remote. For more information, see [local](/windows/win32/Midl/local).|
+  |`nonbrowsable`|Tags an interface or dispinterface member that shouldn't be displayed in a properties browser. For more information, see [nonbrowsable](/windows/win32/Midl/nonbrowsable).|
+  |`requestedit`|Indicates that the property supports the `OnRequestEdit` notification. For more information, see [requestedit](/windows/win32/Midl/requestedit).|
+  |`restricted`|Specifies that the property can't be called arbitrarily. For more information, see [restricted](/windows/win32/Midl/restricted).|
+  |`source`|Indicates that a member of the property is a source of events. For more information, see [source](/windows/win32/Midl/source).|
+
+## **See also**
+
+[Add Property](adding-a-property-visual-cpp.md)