| title |
nonextensible Attribute | Microsoft Docs |
| ms.custom |
|
| ms.date |
11/04/2016 |
| ms.reviewer |
|
| ms.suite |
|
| ms.technology |
|
| ms.tgt_pltfrm |
|
| ms.topic |
article |
| f1_keywords |
|
| dev_langs |
|
| helpviewer_keywords |
nonextensible attribute |
dual interfaces, nonextensible attribute |
|
| ms.assetid |
02a4a18b-ffd3-4d53-8fd1-feb1c05ad5ac |
| caps.latest.revision |
10 |
| author |
mikeblome |
| ms.author |
mblome |
| manager |
ghogen |
| translation.priority.ht |
cs-cz |
de-de |
es-es |
fr-fr |
it-it |
ja-jp |
ko-kr |
pl-pl |
pt-br |
ru-ru |
tr-tr |
zh-cn |
zh-tw |
|
If a dual interface will not be extended at run time (that is, you won't provide methods or properties via IDispatch::Invoke that are not available via the vtable), you should apply the nonextensible attribute to your interface definition. This attribute provides information to client languages (such as Visual Basic) that can be used to enable full code verification at compile time. If this attribute is not supplied, bugs may remain hidden in the client code until run time.
For more information on the nonextensible attribute and an example, see nonextensible.
Dual Interfaces and ATL