| 1. | Indicates that early - binding apis should be used
表示应使用早期绑定api 。 |
| 2. | Operators to test both early - bound and late - bound objects
运算符测试早期绑定和后期绑定的对象。 |
| 3. | Do not use late - binding invocation when early - binding is possible
只要可以用前期绑定就不要用后期绑定。 |
| 4. | Specifies the language in which to generate the early - bound managed class
指定用于生成早期绑定的托管类的语言。 |
| 5. | The name of the method or name of the field being accessed early - bound
以早期绑定方式访问的方法的名称或字段的名称。 |
| 6. | For this reason , rjcb bridges support only com apis that provide early - bound
出于这个原因， rjcb桥只支持那些提供前期绑定 |
| 7. | It only reports data about early - bound calls on late - bound interfaces
它只报告有关对后期绑定接口发出的早期绑定调用的数据。 |
| 8. | The windows management instrumentation class for which to generate an early - bound managed class
为其生成早期绑定的托管类的windows management instrumentation类。 |
| 9. | Code is attempting an early - bound call through a vtable via a class interface that is late - bound only
代码尝试在仅限后期绑定的类接口上通过vtable进行早期绑定调用。 |
| 10. | For an in - process com server in the same com apartment , an early - bound call is equivalent to a c
对于进程内com服务器（在相同的com进程中） ，前期绑定调用等价于c + +的 |
