Microsoft/windows-Rs

7→19 windows_bindgen.type_name depends on windows_bindgen.config cycle✕

Type pairs

1 distinct (type in windows_bindgen.type_name → type in windows_bindgen.config) reference.

Which types

• windows_bindgen.type_name.TypeName → windows_bindgen.config.Config

Direction

windows_bindgen.type_name uses windows_bindgen.config. Changing windows_bindgen.config can break windows_bindgen.type_name, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

8→18 windows_bindgen.winmd.reader depends on windows_bindgen.types cycle✕

Type pairs

2 distinct (type in windows_bindgen.winmd.reader → type in windows_bindgen.types) references.

Which types

• windows_bindgen.winmd.reader.Reader → windows_bindgen.types.Type
• windows_bindgen.winmd.reader.reader$module → windows_bindgen.types.Type

Direction

windows_bindgen.winmd.reader uses windows_bindgen.types. Changing windows_bindgen.types can break windows_bindgen.winmd.reader, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

9→31 windows_reactor.element depends on windows_composition.bindings cycle✕

Type pairs

2 distinct (type in windows_reactor.element → type in windows_composition.bindings) references.

Which types

• windows_reactor.element.Brush → windows_composition.bindings.Color
• windows_reactor.element.ResourceValue → windows_composition.bindings.Color

Direction

windows_reactor.element uses windows_composition.bindings. Changing windows_composition.bindings can break windows_reactor.element, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

9→39 windows_reactor.element depends on windows_canvas.types cycle✕

Type pairs

1 distinct (type in windows_reactor.element → type in windows_canvas.types) reference.

Which types

• windows_reactor.element.View → windows_canvas.types.Ellipse

Direction

windows_reactor.element uses windows_canvas.types. Changing windows_canvas.types can break windows_reactor.element, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

10→6 windows_registry.bindings depends on windows_result.bool✕

Type pairs

1 distinct (type in windows_registry.bindings → type in windows_result.bool) reference.

Which types

• windows_registry.bindings.SECURITY_ATTRIBUTES → windows_result.bool.BOOL

Direction

windows_registry.bindings uses windows_result.bool. Changing windows_result.bool can break windows_registry.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

11→5 windows_strings.bstr depends on windows_core.type✕

Type pairs

1 distinct (type in windows_strings.bstr → type in windows_core.type) reference.

Which types

• windows_strings.bstr.BSTR → windows_core.type.TypeKind

Direction

windows_strings.bstr uses windows_core.type. Changing windows_core.type can break windows_strings.bstr, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

12→5 windows_strings.pcstr depends on windows_core.type✕

Type pairs

1 distinct (type in windows_strings.pcstr → type in windows_core.type) reference.

Which types

• windows_strings.pcstr.PCSTR → windows_core.type.TypeKind

Direction

windows_strings.pcstr uses windows_core.type. Changing windows_core.type can break windows_strings.pcstr, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

13→5 windows_strings.pstr depends on windows_core.type✕

Type pairs

1 distinct (type in windows_strings.pstr → type in windows_core.type) reference.

Which types

• windows_strings.pstr.PSTR → windows_core.type.TypeKind

Direction

windows_strings.pstr uses windows_core.type. Changing windows_core.type can break windows_strings.pstr, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

14→8 windows_clang depends on windows_bindgen.winmd.reader✕

Type pairs

2 distinct (type in windows_clang → type in windows_bindgen.winmd.reader) references.

Which types

• windows_clang.Constant → windows_bindgen.winmd.reader.Reader
• windows_clang.Field → windows_bindgen.winmd.reader.Reader

Direction

windows_clang uses windows_bindgen.winmd.reader. Changing windows_bindgen.winmd.reader can break windows_clang, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

14→18 windows_clang depends on windows_bindgen.types cycle✕

Type pairs

2 distinct (type in windows_clang → type in windows_bindgen.types) references.

Which types

• windows_clang.Constant → windows_bindgen.types.Type
• windows_clang.Field → windows_bindgen.types.Type

Direction

windows_clang uses windows_bindgen.types. Changing windows_bindgen.types can break windows_clang, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

15→1 windows_sys.Windows.Win32.oaidl depends on windows_bindgen.guid✕

Type pairs

4 distinct (type in windows_sys.Windows.Win32.oaidl → type in windows_bindgen.guid) references.

Which types

• windows_sys.Windows.Win32.oaidl.CUSTDATAITEM → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.oaidl.SAFEARR_HAVEIID → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.oaidl.TLIBATTR → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.oaidl.TYPEATTR → windows_bindgen.guid.GUID

Direction

windows_sys.Windows.Win32.oaidl uses windows_bindgen.guid. Changing windows_bindgen.guid can break windows_sys.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

15→11 windows_sys.Windows.Win32.oaidl depends on windows_strings.bstr✕

Type pairs

1 distinct (type in windows_sys.Windows.Win32.oaidl → type in windows_strings.bstr) reference.

Which types

• windows_sys.Windows.Win32.oaidl.EXCEPINFO → windows_strings.bstr.BSTR

Direction

windows_sys.Windows.Win32.oaidl uses windows_strings.bstr. Changing windows_strings.bstr can break windows_sys.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

16→7 windows_metadata.reader.tables depends on windows_bindgen.type_name✕

Type pairs

1 distinct (type in windows_metadata.reader.tables → type in windows_bindgen.type_name) reference.

Which types

• windows_metadata.reader.tables.TypeDef → windows_bindgen.type_name.TypeName

Direction

windows_metadata.reader.tables uses windows_bindgen.type_name. Changing windows_bindgen.type_name can break windows_metadata.reader.tables, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

16→8 windows_metadata.reader.tables depends on windows_bindgen.winmd.reader✕

Type pairs

3 distinct (type in windows_metadata.reader.tables → type in windows_bindgen.winmd.reader) references.

Which types

• windows_metadata.reader.tables.InterfaceImpl → windows_bindgen.winmd.reader.Reader
• windows_metadata.reader.tables.MethodDef → windows_bindgen.winmd.reader.Reader
• windows_metadata.reader.tables.TypeDef → windows_bindgen.winmd.reader.Reader

Direction

windows_metadata.reader.tables uses windows_bindgen.winmd.reader. Changing windows_bindgen.winmd.reader can break windows_metadata.reader.tables, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

16→14 windows_metadata.reader.tables depends on windows_clang✕

Type pairs

2 distinct (type in windows_metadata.reader.tables → type in windows_clang) references.

Which types

• windows_metadata.reader.tables.Constant → windows_clang.Value
• windows_metadata.reader.tables.Field → windows_clang.Constant

Direction

windows_metadata.reader.tables uses windows_clang. Changing windows_clang can break windows_metadata.reader.tables, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

16→18 windows_metadata.reader.tables depends on windows_bindgen.types cycle✕

Type pairs

5 distinct (type in windows_metadata.reader.tables → type in windows_bindgen.types) references.

Which types

• windows_metadata.reader.tables.Constant → windows_bindgen.types.Type
• windows_metadata.reader.tables.Field → windows_bindgen.types.Type
• windows_metadata.reader.tables.InterfaceImpl → windows_bindgen.types.Type
• windows_metadata.reader.tables.TypeDef → windows_bindgen.types.Type
• windows_metadata.reader.tables.TypeSpec → windows_bindgen.types.Type

Direction

windows_metadata.reader.tables uses windows_bindgen.types. Changing windows_bindgen.types can break windows_metadata.reader.tables, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

17→14 windows_result.hresult depends on windows_clang✕

Type pairs

1 distinct (type in windows_result.hresult → type in windows_clang) reference.

Which types

• windows_result.hresult.HRESULT → windows_clang.Error

Direction

windows_result.hresult uses windows_clang. Changing windows_clang can break windows_result.hresult, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

18→7 windows_bindgen.types depends on windows_bindgen.type_name✕

Type pairs

1 distinct (type in windows_bindgen.types → type in windows_bindgen.type_name) reference.

Which types

• windows_bindgen.types.Type → windows_bindgen.type_name.TypeName

Direction

windows_bindgen.types uses windows_bindgen.type_name. Changing windows_bindgen.type_name can break windows_bindgen.types, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

18→8 windows_bindgen.types depends on windows_bindgen.winmd.reader✕

Type pairs

2 distinct (type in windows_bindgen.types → type in windows_bindgen.winmd.reader) references.

Which types

• windows_bindgen.types.Type → windows_bindgen.winmd.reader.Reader
• windows_bindgen.types.types$module → windows_bindgen.winmd.reader.Reader

Direction

windows_bindgen.types uses windows_bindgen.winmd.reader. Changing windows_bindgen.winmd.reader can break windows_bindgen.types, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

18→16 windows_bindgen.types depends on windows_metadata.reader.tables✕

Type pairs

1 distinct (type in windows_bindgen.types → type in windows_metadata.reader.tables) reference.

Which types

• windows_bindgen.types.types$module → windows_metadata.reader.tables.TypeDef

Direction

windows_bindgen.types uses windows_metadata.reader.tables. Changing windows_metadata.reader.tables can break windows_bindgen.types, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

18→19 windows_bindgen.types depends on windows_bindgen.config cycle✕

Type pairs

2 distinct (type in windows_bindgen.types → type in windows_bindgen.config) references.

Which types

• windows_bindgen.types.Type → windows_bindgen.config.Config
• windows_bindgen.types.types$module → windows_bindgen.config.Config

Direction

windows_bindgen.types uses windows_bindgen.config. Changing windows_bindgen.config can break windows_bindgen.types, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

19→1 windows_bindgen.config depends on windows_bindgen.guid✕

Type pairs

1 distinct (type in windows_bindgen.config → type in windows_bindgen.guid) reference.

Which types

• windows_bindgen.config.Config → windows_bindgen.guid.GUID

Direction

windows_bindgen.config uses windows_bindgen.guid. Changing windows_bindgen.guid can break windows_bindgen.config, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

19→7 windows_bindgen.config depends on windows_bindgen.type_name✕

Type pairs

1 distinct (type in windows_bindgen.config → type in windows_bindgen.type_name) reference.

Which types

• windows_bindgen.config.Config → windows_bindgen.type_name.TypeName

Direction

windows_bindgen.config uses windows_bindgen.type_name. Changing windows_bindgen.type_name can break windows_bindgen.config, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

19→8 windows_bindgen.config depends on windows_bindgen.winmd.reader✕

Type pairs

1 distinct (type in windows_bindgen.config → type in windows_bindgen.winmd.reader) reference.

Which types

• windows_bindgen.config.Config → windows_bindgen.winmd.reader.Reader

Direction

windows_bindgen.config uses windows_bindgen.winmd.reader. Changing windows_bindgen.winmd.reader can break windows_bindgen.config, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

19→16 windows_bindgen.config depends on windows_metadata.reader.tables✕

Type pairs

2 distinct (type in windows_bindgen.config → type in windows_metadata.reader.tables) references.

Which types

• windows_bindgen.config.Config → windows_metadata.reader.tables.MethodDef
• windows_bindgen.config.Config → windows_metadata.reader.tables.TypeDef

Direction

windows_bindgen.config uses windows_metadata.reader.tables. Changing windows_metadata.reader.tables can break windows_bindgen.config, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

19→18 windows_bindgen.config depends on windows_bindgen.types✕

Type pairs

1 distinct (type in windows_bindgen.config → type in windows_bindgen.types) reference.

Which types

• windows_bindgen.config.Config → windows_bindgen.types.Type

Direction

windows_bindgen.config uses windows_bindgen.types. Changing windows_bindgen.types can break windows_bindgen.config, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

20→18 windows_core.runtime_type depends on windows_bindgen.types✕

Type pairs

1 distinct (type in windows_core.runtime_type → type in windows_bindgen.types) reference.

Which types

• windows_core.runtime_type.RuntimeType → windows_bindgen.types.Type

Direction

windows_core.runtime_type uses windows_bindgen.types. Changing windows_bindgen.types can break windows_core.runtime_type, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

21→7 windows_bindgen.types.interface depends on windows_bindgen.type_name✕

Type pairs

2 distinct (type in windows_bindgen.types.interface → type in windows_bindgen.type_name) references.

Which types

• windows_bindgen.types.interface.Interface → windows_bindgen.type_name.TypeName
• windows_bindgen.types.interface.interface$module → windows_bindgen.type_name.TypeName

Direction

windows_bindgen.types.interface uses windows_bindgen.type_name. Changing windows_bindgen.type_name can break windows_bindgen.types.interface, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

21→8 windows_bindgen.types.interface depends on windows_bindgen.winmd.reader✕

Type pairs

1 distinct (type in windows_bindgen.types.interface → type in windows_bindgen.winmd.reader) reference.

Which types

• windows_bindgen.types.interface.Interface → windows_bindgen.winmd.reader.Reader

Direction

windows_bindgen.types.interface uses windows_bindgen.winmd.reader. Changing windows_bindgen.winmd.reader can break windows_bindgen.types.interface, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

21→16 windows_bindgen.types.interface depends on windows_metadata.reader.tables✕

Type pairs

3 distinct (type in windows_bindgen.types.interface → type in windows_metadata.reader.tables) references.

Which types

• windows_bindgen.types.interface.Interface → windows_metadata.reader.tables.TypeDef
• windows_bindgen.types.interface.MethodItem → windows_metadata.reader.tables.MethodDef
• windows_bindgen.types.interface.interface$module → windows_metadata.reader.tables.MethodDef

Direction

windows_bindgen.types.interface uses windows_metadata.reader.tables. Changing windows_metadata.reader.tables can break windows_bindgen.types.interface, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

21→18 windows_bindgen.types.interface depends on windows_bindgen.types✕

Type pairs

1 distinct (type in windows_bindgen.types.interface → type in windows_bindgen.types) reference.

Which types

• windows_bindgen.types.interface.Interface → windows_bindgen.types.Type

Direction

windows_bindgen.types.interface uses windows_bindgen.types. Changing windows_bindgen.types can break windows_bindgen.types.interface, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

21→19 windows_bindgen.types.interface depends on windows_bindgen.config✕

Type pairs

2 distinct (type in windows_bindgen.types.interface → type in windows_bindgen.config) references.

Which types

• windows_bindgen.types.interface.Interface → windows_bindgen.config.Config
• windows_bindgen.types.interface.interface$module → windows_bindgen.config.Config

Direction

windows_bindgen.types.interface uses windows_bindgen.config. Changing windows_bindgen.config can break windows_bindgen.types.interface, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

22→5 windows_numerics.bindings depends on windows_core.type✕

Type pairs

5 distinct (type in windows_numerics.bindings → type in windows_core.type) references.

Which types

• windows_numerics.bindings.Matrix3x2 → windows_core.type.TypeKind
• windows_numerics.bindings.Matrix4x4 → windows_core.type.TypeKind
• windows_numerics.bindings.Vector2 → windows_core.type.TypeKind
• windows_numerics.bindings.Vector3 → windows_core.type.TypeKind
• windows_numerics.bindings.Vector4 → windows_core.type.TypeKind

Direction

windows_numerics.bindings uses windows_core.type. Changing windows_core.type can break windows_numerics.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

22→20 windows_numerics.bindings depends on windows_core.runtime_type✕

Type pairs

5 distinct (type in windows_numerics.bindings → type in windows_core.runtime_type) references.

Which types

• windows_numerics.bindings.Matrix3x2 → windows_core.runtime_type.RuntimeType
• windows_numerics.bindings.Matrix4x4 → windows_core.runtime_type.RuntimeType
• windows_numerics.bindings.Vector2 → windows_core.runtime_type.RuntimeType
• windows_numerics.bindings.Vector3 → windows_core.runtime_type.RuntimeType
• windows_numerics.bindings.Vector4 → windows_core.runtime_type.RuntimeType

Direction

windows_numerics.bindings uses windows_core.runtime_type. Changing windows_core.runtime_type can break windows_numerics.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

23→5 windows_strings.hstring depends on windows_core.type✕

Type pairs

1 distinct (type in windows_strings.hstring → type in windows_core.type) reference.

Which types

• windows_strings.hstring.HSTRING → windows_core.type.TypeKind

Direction

windows_strings.hstring uses windows_core.type. Changing windows_core.type can break windows_strings.hstring, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

23→14 windows_strings.hstring depends on windows_clang✕

Type pairs

1 distinct (type in windows_strings.hstring → type in windows_clang) reference.

Which types

• windows_strings.hstring.HSTRING → windows_clang.Value

Direction

windows_strings.hstring uses windows_clang. Changing windows_clang can break windows_strings.hstring, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

23→20 windows_strings.hstring depends on windows_core.runtime_type✕

Type pairs

1 distinct (type in windows_strings.hstring → type in windows_core.runtime_type) reference.

Which types

• windows_strings.hstring.HSTRING → windows_core.runtime_type.RuntimeType

Direction

windows_strings.hstring uses windows_core.runtime_type. Changing windows_core.runtime_type can break windows_strings.hstring, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

24→5 windows_time.bindings depends on windows_core.type✕

Type pairs

2 distinct (type in windows_time.bindings → type in windows_core.type) references.

Which types

• windows_time.bindings.DateTime → windows_core.type.TypeKind
• windows_time.bindings.TimeSpan → windows_core.type.TypeKind

Direction

windows_time.bindings uses windows_core.type. Changing windows_core.type can break windows_time.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

24→20 windows_time.bindings depends on windows_core.runtime_type✕

Type pairs

2 distinct (type in windows_time.bindings → type in windows_core.runtime_type) references.

Which types

• windows_time.bindings.DateTime → windows_core.runtime_type.RuntimeType
• windows_time.bindings.TimeSpan → windows_core.runtime_type.RuntimeType

Direction

windows_time.bindings uses windows_core.runtime_type. Changing windows_core.runtime_type can break windows_time.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

25→2 windows_canvas.reactor_bindings depends on windows_core.imp.can_into✕

Type pairs

4 distinct (type in windows_canvas.reactor_bindings → type in windows_core.imp.can_into) references.

Which types

• windows_canvas.reactor_bindings.DependencyObject → windows_core.imp.can_into.CanInto
• windows_canvas.reactor_bindings.ISurfaceImageSourceNativeWithD2D → windows_core.imp.can_into.CanInto
• windows_canvas.reactor_bindings.ImageSource → windows_core.imp.can_into.CanInto
• windows_canvas.reactor_bindings.SurfaceImageSource → windows_core.imp.can_into.CanInto

Direction

windows_canvas.reactor_bindings uses windows_core.imp.can_into. Changing windows_core.imp.can_into can break windows_canvas.reactor_bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

25→4 windows_canvas.reactor_bindings depends on windows_core.runtime_name✕

Type pairs

4 distinct (type in windows_canvas.reactor_bindings → type in windows_core.runtime_name) references.

Which types

• windows_canvas.reactor_bindings.DependencyObject → windows_core.runtime_name.RuntimeName
• windows_canvas.reactor_bindings.ISurfaceImageSourceNativeWithD2D → windows_core.runtime_name.RuntimeName
• windows_canvas.reactor_bindings.ImageSource → windows_core.runtime_name.RuntimeName
• windows_canvas.reactor_bindings.SurfaceImageSource → windows_core.runtime_name.RuntimeName

Direction

windows_canvas.reactor_bindings uses windows_core.runtime_name. Changing windows_core.runtime_name can break windows_canvas.reactor_bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

25→17 windows_canvas.reactor_bindings depends on windows_result.hresult✕

Type pairs

1 distinct (type in windows_canvas.reactor_bindings → type in windows_result.hresult) reference.

Which types

• windows_canvas.reactor_bindings.ISurfaceImageSourceNativeWithD2D → windows_result.hresult.HRESULT

Direction

windows_canvas.reactor_bindings uses windows_result.hresult. Changing windows_result.hresult can break windows_canvas.reactor_bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

25→20 windows_canvas.reactor_bindings depends on windows_core.runtime_type✕

Type pairs

7 distinct (type in windows_canvas.reactor_bindings → type in windows_core.runtime_type) references.

Which types

• windows_canvas.reactor_bindings.DependencyObject → windows_core.runtime_type.RuntimeType
• windows_canvas.reactor_bindings.IDependencyObject → windows_core.runtime_type.RuntimeType
• windows_canvas.reactor_bindings.IImageSource → windows_core.runtime_type.RuntimeType
• windows_canvas.reactor_bindings.ISurfaceImageSource → windows_core.runtime_type.RuntimeType
• windows_canvas.reactor_bindings.ISurfaceImageSourceFactory → windows_core.runtime_type.RuntimeType
• windows_canvas.reactor_bindings.ImageSource → windows_core.runtime_type.RuntimeType
• windows_canvas.reactor_bindings.SurfaceImageSource → windows_core.runtime_type.RuntimeType

Direction

windows_canvas.reactor_bindings uses windows_core.runtime_type. Changing windows_core.runtime_type can break windows_canvas.reactor_bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

25→21 windows_canvas.reactor_bindings depends on windows_bindgen.types.interface✕

Type pairs

8 distinct (type in windows_canvas.reactor_bindings → type in windows_bindgen.types.interface) references.

Which types

• windows_canvas.reactor_bindings.DependencyObject → windows_bindgen.types.interface.Interface
• windows_canvas.reactor_bindings.IDependencyObject → windows_bindgen.types.interface.Interface
• windows_canvas.reactor_bindings.IImageSource → windows_bindgen.types.interface.Interface
• windows_canvas.reactor_bindings.ISurfaceImageSource → windows_bindgen.types.interface.Interface
• windows_canvas.reactor_bindings.ISurfaceImageSourceFactory → windows_bindgen.types.interface.Interface
• windows_canvas.reactor_bindings.ISurfaceImageSourceNativeWithD2D → windows_bindgen.types.interface.Interface
• windows_canvas.reactor_bindings.ImageSource → windows_bindgen.types.interface.Interface
• windows_canvas.reactor_bindings.SurfaceImageSource → windows_bindgen.types.interface.Interface

Direction

windows_canvas.reactor_bindings uses windows_bindgen.types.interface. Changing windows_bindgen.types.interface can break windows_canvas.reactor_bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

25→29 windows_canvas.reactor_bindings depends on windows_core.inspectable cycle✕

Type pairs

4 distinct (type in windows_canvas.reactor_bindings → type in windows_core.inspectable) references.

Which types

• windows_canvas.reactor_bindings.IDependencyObject_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_canvas.reactor_bindings.IImageSource_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_canvas.reactor_bindings.ISurfaceImageSourceFactory_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_canvas.reactor_bindings.ISurfaceImageSource_Vtbl → windows_core.inspectable.IInspectable_Vtbl

Direction

windows_canvas.reactor_bindings uses windows_core.inspectable. Changing windows_core.inspectable can break windows_canvas.reactor_bindings, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

25→37 windows_canvas.reactor_bindings depends on windows_core.unknown cycle✕

Type pairs

9 distinct (type in windows_canvas.reactor_bindings → type in windows_core.unknown) references.

Which types

• windows_canvas.reactor_bindings.DependencyObject → windows_core.unknown.IUnknown
• windows_canvas.reactor_bindings.IDependencyObject → windows_core.unknown.IUnknown
• windows_canvas.reactor_bindings.IImageSource → windows_core.unknown.IUnknown
• windows_canvas.reactor_bindings.ISurfaceImageSource → windows_core.unknown.IUnknown
• windows_canvas.reactor_bindings.ISurfaceImageSourceFactory → windows_core.unknown.IUnknown
• windows_canvas.reactor_bindings.ISurfaceImageSourceNativeWithD2D → windows_core.unknown.IUnknown
• windows_canvas.reactor_bindings.ISurfaceImageSourceNativeWithD2D_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows_canvas.reactor_bindings.ImageSource → windows_core.unknown.IUnknown
• windows_canvas.reactor_bindings.SurfaceImageSource → windows_core.unknown.IUnknown

Direction

windows_canvas.reactor_bindings uses windows_core.unknown. Changing windows_core.unknown can break windows_canvas.reactor_bindings, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

26→1 windows_collections.bindings depends on windows_bindgen.guid✕

Type pairs

11 distinct (type in windows_collections.bindings → type in windows_bindgen.guid) references.

Which types

• windows_collections.bindings.IIterable_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IIterator_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IKeyValuePair_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IMapChangedEventArgs_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IMapView_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IMap_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IObservableMap_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IObservableVector_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IVectorChangedEventArgs_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IVectorView_Vtbl → windows_bindgen.guid.GUID
• windows_collections.bindings.IVector_Vtbl → windows_bindgen.guid.GUID

Direction

windows_collections.bindings uses windows_bindgen.guid. Changing windows_bindgen.guid can break windows_collections.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

26→2 windows_collections.bindings depends on windows_core.imp.can_into✕

Type pairs

11 distinct (type in windows_collections.bindings → type in windows_core.imp.can_into) references.

Which types

• windows_collections.bindings.IIterable → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IIterator → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IKeyValuePair → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IMap → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IMapChangedEventArgs → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IMapView → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IObservableMap → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IObservableVector → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IVector → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IVectorChangedEventArgs → windows_core.imp.can_into.CanInto
• windows_collections.bindings.IVectorView → windows_core.imp.can_into.CanInto

Direction

windows_collections.bindings uses windows_core.imp.can_into. Changing windows_core.imp.can_into can break windows_collections.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

26→3 windows_collections.bindings depends on windows_core.out_ref✕

Type pairs

1 distinct (type in windows_collections.bindings → type in windows_core.out_ref) reference.

Which types

• windows_collections.bindings.IMapView_Impl → windows_core.out_ref.OutRef

Direction

windows_collections.bindings uses windows_core.out_ref. Changing windows_core.out_ref can break windows_collections.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

26→4 windows_collections.bindings depends on windows_core.runtime_name✕

Type pairs

11 distinct (type in windows_collections.bindings → type in windows_core.runtime_name) references.

Which types

• windows_collections.bindings.IIterable → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IIterator → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IKeyValuePair → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IMap → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IMapChangedEventArgs → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IMapView → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IObservableMap → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IObservableVector → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IVector → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IVectorChangedEventArgs → windows_core.runtime_name.RuntimeName
• windows_collections.bindings.IVectorView → windows_core.runtime_name.RuntimeName

Direction

windows_collections.bindings uses windows_core.runtime_name. Changing windows_core.runtime_name can break windows_collections.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

26→5 windows_collections.bindings depends on windows_core.type✕

Type pairs

1 distinct (type in windows_collections.bindings → type in windows_core.type) reference.

Which types

• windows_collections.bindings.CollectionChange → windows_core.type.TypeKind

Direction

windows_collections.bindings uses windows_core.type. Changing windows_core.type can break windows_collections.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

26→17 windows_collections.bindings depends on windows_result.hresult✕

Type pairs

2 distinct (type in windows_collections.bindings → type in windows_result.hresult) references.

Which types

• windows_collections.bindings.MapChangedEventHandlerBox → windows_result.hresult.HRESULT
• windows_collections.bindings.VectorChangedEventHandlerBox → windows_result.hresult.HRESULT

Direction

windows_collections.bindings uses windows_result.hresult. Changing windows_result.hresult can break windows_collections.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

26→20 windows_collections.bindings depends on windows_core.runtime_type✕

Type pairs

14 distinct (type in windows_collections.bindings → type in windows_core.runtime_type) references.

Which types

• windows_collections.bindings.CollectionChange → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IIterable → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IIterator → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IKeyValuePair → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IMap → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IMapChangedEventArgs → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IMapView → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IObservableMap → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IObservableVector → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IVector → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IVectorChangedEventArgs → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.IVectorView → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.MapChangedEventHandler → windows_core.runtime_type.RuntimeType
• windows_collections.bindings.VectorChangedEventHandler → windows_core.runtime_type.RuntimeType

Direction

windows_collections.bindings uses windows_core.runtime_type. Changing windows_core.runtime_type can break windows_collections.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

26→21 windows_collections.bindings depends on windows_bindgen.types.interface✕

Type pairs

13 distinct (type in windows_collections.bindings → type in windows_bindgen.types.interface) references.

Which types

• windows_collections.bindings.IIterable → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IIterator → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IKeyValuePair → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IMap → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IMapChangedEventArgs → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IMapView → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IObservableMap → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IObservableVector → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IVector → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IVectorChangedEventArgs → windows_bindgen.types.interface.Interface
• windows_collections.bindings.IVectorView → windows_bindgen.types.interface.Interface
• windows_collections.bindings.MapChangedEventHandler → windows_bindgen.types.interface.Interface
• windows_collections.bindings.VectorChangedEventHandler → windows_bindgen.types.interface.Interface

Direction

windows_collections.bindings uses windows_bindgen.types.interface. Changing windows_bindgen.types.interface can break windows_collections.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

26→29 windows_collections.bindings depends on windows_core.inspectable cycle✕

Type pairs

11 distinct (type in windows_collections.bindings → type in windows_core.inspectable) references.

Which types

• windows_collections.bindings.IIterable_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IIterator_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IKeyValuePair_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IMapChangedEventArgs_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IMapView_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IMap_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IObservableMap_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IObservableVector_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IVectorChangedEventArgs_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IVectorView_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_collections.bindings.IVector_Vtbl → windows_core.inspectable.IInspectable_Vtbl

Direction

windows_collections.bindings uses windows_core.inspectable. Changing windows_core.inspectable can break windows_collections.bindings, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

26→31 windows_collections.bindings depends on windows_composition.bindings cycle✕

Type pairs

1 distinct (type in windows_collections.bindings → type in windows_composition.bindings) reference.

Which types

• windows_collections.bindings.IVector → windows_composition.bindings.CompositionShapeCollection

Direction

windows_collections.bindings uses windows_composition.bindings. Changing windows_composition.bindings can break windows_collections.bindings, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

26→32 windows_collections.bindings depends on windows_reactor.native.winui.bindings cycle✕

Type pairs

7 distinct (type in windows_collections.bindings → type in windows_reactor.native.winui.bindings) references.

Which types

• windows_collections.bindings.IObservableVector → windows_reactor.native.winui.bindings.ItemCollection
• windows_collections.bindings.IVector → windows_reactor.native.winui.bindings.BlockCollection
• windows_collections.bindings.IVector → windows_reactor.native.winui.bindings.ColumnDefinitionCollection
• windows_collections.bindings.IVector → windows_reactor.native.winui.bindings.InlineCollection
• windows_collections.bindings.IVector → windows_reactor.native.winui.bindings.RowDefinitionCollection
• windows_collections.bindings.IVector → windows_reactor.native.winui.bindings.TransitionCollection
• windows_collections.bindings.IVector → windows_reactor.native.winui.bindings.UIElementCollection

Direction

windows_collections.bindings uses windows_reactor.native.winui.bindings. Changing windows_reactor.native.winui.bindings can break windows_collections.bindings, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

26→37 windows_collections.bindings depends on windows_core.unknown cycle✕

Type pairs

20 distinct (type in windows_collections.bindings → type in windows_core.unknown) references.

Which types

• windows_collections.bindings.IIterable → windows_core.unknown.IUnknown
• windows_collections.bindings.IIterable_Impl → windows_core.unknown.IUnknownImpl
• windows_collections.bindings.IIterator → windows_core.unknown.IUnknown
• windows_collections.bindings.IIterator_Impl → windows_core.unknown.IUnknownImpl
• windows_collections.bindings.IKeyValuePair → windows_core.unknown.IUnknown
• windows_collections.bindings.IKeyValuePair_Impl → windows_core.unknown.IUnknownImpl
• windows_collections.bindings.IMap → windows_core.unknown.IUnknown
• windows_collections.bindings.IMapChangedEventArgs → windows_core.unknown.IUnknown
• windows_collections.bindings.IMapChangedEventArgs_Impl → windows_core.unknown.IUnknownImpl
• windows_collections.bindings.IMapView → windows_core.unknown.IUnknown
• windows_collections.bindings.IObservableMap → windows_core.unknown.IUnknown
• windows_collections.bindings.IObservableVector → windows_core.unknown.IUnknown
• windows_collections.bindings.IVector → windows_core.unknown.IUnknown
• windows_collections.bindings.IVectorChangedEventArgs → windows_core.unknown.IUnknown
• windows_collections.bindings.IVectorChangedEventArgs_Impl → windows_core.unknown.IUnknownImpl
• windows_collections.bindings.IVectorView → windows_core.unknown.IUnknown
• windows_collections.bindings.MapChangedEventHandler → windows_core.unknown.IUnknown
• windows_collections.bindings.MapChangedEventHandler_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows_collections.bindings.VectorChangedEventHandler → windows_core.unknown.IUnknown
• windows_collections.bindings.VectorChangedEventHandler_Vtbl → windows_core.unknown.IUnknown_Vtbl

Direction

windows_collections.bindings uses windows_core.unknown. Changing windows_core.unknown can break windows_collections.bindings, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

27→5 windows_strings.pcwstr depends on windows_core.type✕

Type pairs

1 distinct (type in windows_strings.pcwstr → type in windows_core.type) reference.

Which types

• windows_strings.pcwstr.PCWSTR → windows_core.type.TypeKind

Direction

windows_strings.pcwstr uses windows_core.type. Changing windows_core.type can break windows_strings.pcwstr, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

27→23 windows_strings.pcwstr depends on windows_strings.hstring✕

Type pairs

1 distinct (type in windows_strings.pcwstr → type in windows_strings.hstring) reference.

Which types

• windows_strings.pcwstr.PCWSTR → windows_strings.hstring.HSTRING

Direction

windows_strings.pcwstr uses windows_strings.hstring. Changing windows_strings.hstring can break windows_strings.pcwstr, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

28→5 windows_strings.pwstr depends on windows_core.type✕

Type pairs

1 distinct (type in windows_strings.pwstr → type in windows_core.type) reference.

Which types

• windows_strings.pwstr.PWSTR → windows_core.type.TypeKind

Direction

windows_strings.pwstr uses windows_core.type. Changing windows_core.type can break windows_strings.pwstr, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

28→23 windows_strings.pwstr depends on windows_strings.hstring✕

Type pairs

1 distinct (type in windows_strings.pwstr → type in windows_strings.hstring) reference.

Which types

• windows_strings.pwstr.PWSTR → windows_strings.hstring.HSTRING

Direction

windows_strings.pwstr uses windows_strings.hstring. Changing windows_strings.hstring can break windows_strings.pwstr, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

29→2 windows_core.inspectable depends on windows_core.imp.can_into✕

Type pairs

1 distinct (type in windows_core.inspectable → type in windows_core.imp.can_into) reference.

Which types

• windows_core.inspectable.IInspectable → windows_core.imp.can_into.CanInto

Direction

windows_core.inspectable uses windows_core.imp.can_into. Changing windows_core.imp.can_into can break windows_core.inspectable, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

29→4 windows_core.inspectable depends on windows_core.runtime_name✕

Type pairs

1 distinct (type in windows_core.inspectable → type in windows_core.runtime_name) reference.

Which types

• windows_core.inspectable.IInspectable → windows_core.runtime_name.RuntimeName

Direction

windows_core.inspectable uses windows_core.runtime_name. Changing windows_core.runtime_name can break windows_core.inspectable, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

29→9 windows_core.inspectable depends on windows_reactor.element✕

Type pairs

2 distinct (type in windows_core.inspectable → type in windows_reactor.element) references.

Which types

• windows_core.inspectable.IInspectable → windows_reactor.element.CommandBarFlyout
• windows_core.inspectable.IInspectable → windows_reactor.element.Flyout

Direction

windows_core.inspectable uses windows_reactor.element. Changing windows_reactor.element can break windows_core.inspectable, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

29→20 windows_core.inspectable depends on windows_core.runtime_type✕

Type pairs

1 distinct (type in windows_core.inspectable → type in windows_core.runtime_type) reference.

Which types

• windows_core.inspectable.IInspectable → windows_core.runtime_type.RuntimeType

Direction

windows_core.inspectable uses windows_core.runtime_type. Changing windows_core.runtime_type can break windows_core.inspectable, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

29→21 windows_core.inspectable depends on windows_bindgen.types.interface✕

Type pairs

1 distinct (type in windows_core.inspectable → type in windows_bindgen.types.interface) reference.

Which types

• windows_core.inspectable.IInspectable → windows_bindgen.types.interface.Interface

Direction

windows_core.inspectable uses windows_bindgen.types.interface. Changing windows_bindgen.types.interface can break windows_core.inspectable, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

29→25 windows_core.inspectable depends on windows_canvas.reactor_bindings✕

Type pairs

3 distinct (type in windows_core.inspectable → type in windows_canvas.reactor_bindings) references.

Which types

• windows_core.inspectable.IInspectable → windows_canvas.reactor_bindings.DependencyObject
• windows_core.inspectable.IInspectable → windows_canvas.reactor_bindings.ImageSource
• windows_core.inspectable.IInspectable → windows_canvas.reactor_bindings.SurfaceImageSource

Direction

windows_core.inspectable uses windows_canvas.reactor_bindings. Changing windows_canvas.reactor_bindings can break windows_core.inspectable, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

29→26 windows_core.inspectable depends on windows_collections.bindings✕

Type pairs

1 distinct (type in windows_core.inspectable → type in windows_collections.bindings) reference.

Which types

• windows_core.inspectable.IInspectable → windows_collections.bindings.IVectorChangedEventArgs

Direction

windows_core.inspectable uses windows_collections.bindings. Changing windows_collections.bindings can break windows_core.inspectable, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

29→31 windows_core.inspectable depends on windows_composition.bindings cycle✕

Type pairs

29 distinct (type in windows_core.inspectable → type in windows_composition.bindings) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionBatchCompletedEventArgs
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionBrush
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionColorBrush
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionContainerShape
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionDrawingSurface
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionEllipseGeometry
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionGeometry
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionGraphicsDevice
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionNineGridBrush
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionObject
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionRoundedRectangleGeometry
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionShape
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionShapeCollection
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionSpriteShape
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionSurfaceBrush
• windows_core.inspectable.IInspectable → windows_composition.bindings.CompositionTarget
• windows_core.inspectable.IInspectable → windows_composition.bindings.Compositor
• windows_core.inspectable.IInspectable → windows_composition.bindings.ContainerVisual
• windows_core.inspectable.IInspectable → windows_composition.bindings.CubicBezierEasingFunction
• windows_core.inspectable.IInspectable → windows_composition.bindings.DesktopWindowTarget
• windows_core.inspectable.IInspectable → windows_composition.bindings.DispatcherQueueController
• windows_core.inspectable.IInspectable → windows_composition.bindings.ICompositionAnimationBase
• windows_core.inspectable.IInspectable → windows_composition.bindings.ICompositionSurface
• windows_core.inspectable.IInspectable → windows_composition.bindings.KeyFrameAnimation
• windows_core.inspectable.IInspectable → windows_composition.bindings.LinearEasingFunction

Direction

windows_core.inspectable uses windows_composition.bindings. Changing windows_composition.bindings can break windows_core.inspectable, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

29→32 windows_core.inspectable depends on windows_reactor.native.winui.bindings cycle✕

Type pairs

132 distinct (type in windows_core.inspectable → type in windows_reactor.native.winui.bindings) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.AppBar
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.AppWindow
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.AppWindowPresenter
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.AppWindowTitleBar
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.Application
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.ApplicationInitializationCallbackParams
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.AutoSuggestBoxSuggestionChosenEventArgs
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.AutoSuggestBoxTextChangedEventArgs
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.AutomationPeer
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.AutomationProperties
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.BitmapImage
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.BitmapSource
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.Block
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.BlockCollection
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.BreadcrumbBarItemClickedEventArgs
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.ButtonBase
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.CalendarDatePickerDateChangedEventArgs
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.CalendarViewSelectedDatesChangedEventArgs
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.CharacterReceivedRoutedEventArgs
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.ColorChangedEventArgs
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.ColumnDefinition
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.ColumnDefinitionCollection
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.ContentDialogClosedEventArgs
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.ContentIsland
• windows_core.inspectable.IInspectable → windows_reactor.native.winui.bindings.Control

Direction

windows_core.inspectable uses windows_reactor.native.winui.bindings. Changing windows_reactor.native.winui.bindings can break windows_core.inspectable, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

29→37 windows_core.inspectable depends on windows_core.unknown cycle✕

Type pairs

2 distinct (type in windows_core.inspectable → type in windows_core.unknown) references.

Which types

• windows_core.inspectable.IInspectable → windows_core.unknown.IUnknown
• windows_core.inspectable.IInspectable_Vtbl → windows_core.unknown.IUnknown_Vtbl

Direction

windows_core.inspectable uses windows_core.unknown. Changing windows_core.unknown can break windows_core.inspectable, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

29→39 windows_core.inspectable depends on windows_canvas.types cycle✕

Type pairs

2 distinct (type in windows_core.inspectable → type in windows_canvas.types) references.

Which types

• windows_core.inspectable.IInspectable → windows_canvas.types.Brush
• windows_core.inspectable.IInspectable → windows_canvas.types.Ellipse

Direction

windows_core.inspectable uses windows_canvas.types. Changing windows_canvas.types can break windows_core.inspectable, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

29→40 windows_core.inspectable depends on windows.Windows.Foundation cycle✕

Type pairs

9 distinct (type in windows_core.inspectable → type in windows.Windows.Foundation) references.

Which types

• windows_core.inspectable.IInspectable → windows.Windows.Foundation.IClosable
• windows_core.inspectable.IInspectable → windows.Windows.Foundation.IGetActivationFactory
• windows_core.inspectable.IInspectable → windows.Windows.Foundation.IMemoryBuffer
• windows_core.inspectable.IInspectable → windows.Windows.Foundation.IMemoryBufferReference
• windows_core.inspectable.IInspectable → windows.Windows.Foundation.IStringable
• windows_core.inspectable.IInspectable → windows.Windows.Foundation.IWwwFormUrlDecoderEntry
• windows_core.inspectable.IInspectable → windows.Windows.Foundation.MemoryBuffer
• windows_core.inspectable.IInspectable → windows.Windows.Foundation.WwwFormUrlDecoder
• windows_core.inspectable.IInspectable → windows.Windows.Foundation.WwwFormUrlDecoderEntry

Direction

windows_core.inspectable uses windows.Windows.Foundation. Changing windows.Windows.Foundation can break windows_core.inspectable, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

30→1 windows_sys.Windows.Win32.winnt depends on windows_bindgen.guid✕

Type pairs

27 distinct (type in windows_sys.Windows.Win32.winnt → type in windows_bindgen.guid) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_sys.Windows.Win32.winnt.ACCESS_ALLOWED_CALLBACK_OBJECT_ACE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.ACCESS_ALLOWED_OBJECT_ACE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.ACCESS_DENIED_CALLBACK_OBJECT_ACE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.ACCESS_DENIED_OBJECT_ACE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.ANON_OBJECT_HEADER → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.ANON_OBJECT_HEADER_BIGOBJ → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.ANON_OBJECT_HEADER_V2 → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.COMPATIBILITY_CONTEXT_ELEMENT → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.ENLISTMENT_BASIC_INFORMATION → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.ENLISTMENT_CRM_INFORMATION → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.KTMOBJECT_CURSOR → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.NETWORK_APP_INSTANCE_EA → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.NOTIFY_USER_POWER_SETTING → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.OBJECTID → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.REPARSE_GUID_DATA_BUFFER → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.RESOURCEMANAGER_BASIC_INFORMATION → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.SERVERSILO_DIAGNOSTIC_INFORMATION → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.SET_POWER_SETTING_VALUE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.SYSTEM_ALARM_CALLBACK_OBJECT_ACE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.SYSTEM_ALARM_OBJECT_ACE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.SYSTEM_AUDIT_CALLBACK_OBJECT_ACE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.SYSTEM_AUDIT_OBJECT_ACE → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.TRANSACTIONMANAGER_BASIC_INFORMATION → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.TRANSACTIONMANAGER_LOG_INFORMATION → windows_bindgen.guid.GUID
• windows_sys.Windows.Win32.winnt.TRANSACTIONMANAGER_OLDEST_INFORMATION → windows_bindgen.guid.GUID

Direction

windows_sys.Windows.Win32.winnt uses windows_bindgen.guid. Changing windows_bindgen.guid can break windows_sys.Windows.Win32.winnt, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

30→27 windows_sys.Windows.Win32.winnt depends on windows_strings.pcwstr✕

Type pairs

4 distinct (type in windows_sys.Windows.Win32.winnt → type in windows_strings.pcwstr) references.

Which types

• windows_sys.Windows.Win32.winnt.ACTIVATION_CONTEXT_ASSEMBLY_DETAILED_INFORMATION → windows_strings.pcwstr.PCWSTR
• windows_sys.Windows.Win32.winnt.ACTIVATION_CONTEXT_DETAILED_INFORMATION → windows_strings.pcwstr.PCWSTR
• windows_sys.Windows.Win32.winnt.ASSEMBLY_FILE_DETAILED_INFORMATION → windows_strings.pcwstr.PCWSTR
• windows_sys.Windows.Win32.winnt.CUSTOM_SYSTEM_EVENT_TRIGGER_CONFIG → windows_strings.pcwstr.PCWSTR

Direction

windows_sys.Windows.Win32.winnt uses windows_strings.pcwstr. Changing windows_strings.pcwstr can break windows_sys.Windows.Win32.winnt, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

30→28 windows_sys.Windows.Win32.winnt depends on windows_strings.pwstr✕

Type pairs

6 distinct (type in windows_sys.Windows.Win32.winnt → type in windows_strings.pwstr) references.

Which types

• windows_sys.Windows.Win32.winnt.CLAIM_SECURITY_ATTRIBUTE_FQBN_VALUE → windows_strings.pwstr.PWSTR
• windows_sys.Windows.Win32.winnt.CLAIM_SECURITY_ATTRIBUTE_V1 → windows_strings.pwstr.PWSTR
• windows_sys.Windows.Win32.winnt.JOBOBJECT_IO_RATE_CONTROL_INFORMATION_NATIVE → windows_strings.pwstr.PWSTR
• windows_sys.Windows.Win32.winnt.JOBOBJECT_IO_RATE_CONTROL_INFORMATION_NATIVE_V2 → windows_strings.pwstr.PWSTR
• windows_sys.Windows.Win32.winnt.JOBOBJECT_IO_RATE_CONTROL_INFORMATION_NATIVE_V3 → windows_strings.pwstr.PWSTR
• windows_sys.Windows.Win32.winnt.TOKEN_BNO_ISOLATION_INFORMATION → windows_strings.pwstr.PWSTR

Direction

windows_sys.Windows.Win32.winnt uses windows_strings.pwstr. Changing windows_strings.pwstr can break windows_sys.Windows.Win32.winnt, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→1 windows_composition.bindings depends on windows_bindgen.guid✕

Type pairs

2 distinct (type in windows_composition.bindings → type in windows_bindgen.guid) references.

Which types

• windows_composition.bindings.ICompositionAnimationBase_Vtbl → windows_bindgen.guid.GUID
• windows_composition.bindings.ICompositionSurface_Vtbl → windows_bindgen.guid.GUID

Direction

windows_composition.bindings uses windows_bindgen.guid. Changing windows_bindgen.guid can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→2 windows_composition.bindings depends on windows_core.imp.can_into✕

Type pairs

40 distinct (type in windows_composition.bindings → type in windows_core.imp.can_into) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_composition.bindings.CompositionAnimation → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionAnimationGroup → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionBatchCompletedEventArgs → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionBrush → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionColorBrush → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionContainerShape → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionDrawingSurface → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionEasingFunction → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionEllipseGeometry → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionGeometry → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionGraphicsDevice → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionNineGridBrush → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionObject → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionRoundedRectangleGeometry → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionScopedBatch → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionShape → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionShapeCollection → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionSpriteShape → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionSurfaceBrush → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CompositionTarget → windows_core.imp.can_into.CanInto
• windows_composition.bindings.Compositor → windows_core.imp.can_into.CanInto
• windows_composition.bindings.ContainerVisual → windows_core.imp.can_into.CanInto
• windows_composition.bindings.CubicBezierEasingFunction → windows_core.imp.can_into.CanInto
• windows_composition.bindings.DesktopWindowTarget → windows_core.imp.can_into.CanInto
• windows_composition.bindings.DispatcherQueueController → windows_core.imp.can_into.CanInto

Direction

windows_composition.bindings uses windows_core.imp.can_into. Changing windows_core.imp.can_into can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→4 windows_composition.bindings depends on windows_core.runtime_name✕

Type pairs

40 distinct (type in windows_composition.bindings → type in windows_core.runtime_name) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_composition.bindings.CompositionAnimation → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionAnimationGroup → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionBatchCompletedEventArgs → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionBrush → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionColorBrush → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionContainerShape → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionDrawingSurface → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionEasingFunction → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionEllipseGeometry → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionGeometry → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionGraphicsDevice → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionNineGridBrush → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionObject → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionRoundedRectangleGeometry → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionScopedBatch → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionShape → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionShapeCollection → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionSpriteShape → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionSurfaceBrush → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CompositionTarget → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.Compositor → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.ContainerVisual → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.CubicBezierEasingFunction → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.DesktopWindowTarget → windows_core.runtime_name.RuntimeName
• windows_composition.bindings.DispatcherQueueController → windows_core.runtime_name.RuntimeName

Direction

windows_composition.bindings uses windows_core.runtime_name. Changing windows_core.runtime_name can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→5 windows_composition.bindings depends on windows_core.type✕

Type pairs

8 distinct (type in windows_composition.bindings → type in windows_core.type) references.

Which types

• windows_composition.bindings.AnimationIterationBehavior → windows_core.type.TypeKind
• windows_composition.bindings.Color → windows_core.type.TypeKind
• windows_composition.bindings.CompositionBatchTypes → windows_core.type.TypeKind
• windows_composition.bindings.CompositionBorderMode → windows_core.type.TypeKind
• windows_composition.bindings.CompositionStretch → windows_core.type.TypeKind
• windows_composition.bindings.DirectXAlphaMode → windows_core.type.TypeKind
• windows_composition.bindings.DirectXPixelFormat → windows_core.type.TypeKind
• windows_composition.bindings.Size → windows_core.type.TypeKind

Direction

windows_composition.bindings uses windows_core.type. Changing windows_core.type can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→17 windows_composition.bindings depends on windows_result.hresult✕

Type pairs

3 distinct (type in windows_composition.bindings → type in windows_result.hresult) references.

Which types

• windows_composition.bindings.ICompositionDrawingSurfaceInterop → windows_result.hresult.HRESULT
• windows_composition.bindings.ICompositionGraphicsDeviceInterop → windows_result.hresult.HRESULT
• windows_composition.bindings.TypedEventHandlerBox → windows_result.hresult.HRESULT

Direction

windows_composition.bindings uses windows_result.hresult. Changing windows_result.hresult can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→20 windows_composition.bindings depends on windows_core.runtime_type✕

Type pairs

83 distinct (type in windows_composition.bindings → type in windows_core.runtime_type) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_composition.bindings.AnimationIterationBehavior → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.Color → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionAnimation → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionAnimationGroup → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionBatchCompletedEventArgs → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionBatchTypes → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionBorderMode → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionBrush → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionColorBrush → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionContainerShape → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionDrawingSurface → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionEasingFunction → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionEllipseGeometry → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionGeometry → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionGraphicsDevice → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionNineGridBrush → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionObject → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionRoundedRectangleGeometry → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionScopedBatch → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionShape → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionShapeCollection → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionSpriteShape → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionStretch → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionSurfaceBrush → windows_core.runtime_type.RuntimeType
• windows_composition.bindings.CompositionTarget → windows_core.runtime_type.RuntimeType

Direction

windows_composition.bindings uses windows_core.runtime_type. Changing windows_core.runtime_type can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→21 windows_composition.bindings depends on windows_bindgen.types.interface✕

Type pairs

79 distinct (type in windows_composition.bindings → type in windows_bindgen.types.interface) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_composition.bindings.CompositionAnimation → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionAnimationGroup → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionBatchCompletedEventArgs → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionBrush → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionColorBrush → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionContainerShape → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionDrawingSurface → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionEasingFunction → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionEllipseGeometry → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionGeometry → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionGraphicsDevice → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionNineGridBrush → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionObject → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionRoundedRectangleGeometry → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionScopedBatch → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionShape → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionShapeCollection → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionSpriteShape → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionSurfaceBrush → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CompositionTarget → windows_bindgen.types.interface.Interface
• windows_composition.bindings.Compositor → windows_bindgen.types.interface.Interface
• windows_composition.bindings.ContainerVisual → windows_bindgen.types.interface.Interface
• windows_composition.bindings.CubicBezierEasingFunction → windows_bindgen.types.interface.Interface
• windows_composition.bindings.DesktopWindowTarget → windows_bindgen.types.interface.Interface
• windows_composition.bindings.DispatcherQueueController → windows_bindgen.types.interface.Interface

Direction

windows_composition.bindings uses windows_bindgen.types.interface. Changing windows_bindgen.types.interface can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→22 windows_composition.bindings depends on windows_numerics.bindings✕

Type pairs

9 distinct (type in windows_composition.bindings → type in windows_numerics.bindings) references.

Which types

• windows_composition.bindings.ICompositionEllipseGeometry → windows_numerics.bindings.Vector2
• windows_composition.bindings.ICompositionRoundedRectangleGeometry → windows_numerics.bindings.Vector2
• windows_composition.bindings.ICompositionShape → windows_numerics.bindings.Vector2
• windows_composition.bindings.ICompositor → windows_numerics.bindings.Vector2
• windows_composition.bindings.IVector3KeyFrameAnimation → windows_numerics.bindings.Vector3
• windows_composition.bindings.IVisual → windows_numerics.bindings.Vector2
• windows_composition.bindings.IVisual → windows_numerics.bindings.Vector3
• windows_composition.bindings.IVisual2 → windows_numerics.bindings.Vector2
• windows_composition.bindings.IVisual2 → windows_numerics.bindings.Vector3

Direction

windows_composition.bindings uses windows_numerics.bindings. Changing windows_numerics.bindings can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→24 windows_composition.bindings depends on windows_time.bindings✕

Type pairs

1 distinct (type in windows_composition.bindings → type in windows_time.bindings) reference.

Which types

• windows_composition.bindings.IKeyFrameAnimation → windows_time.bindings.TimeSpan

Direction

windows_composition.bindings uses windows_time.bindings. Changing windows_time.bindings can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→29 windows_composition.bindings depends on windows_core.inspectable✕

Type pairs

40 distinct (type in windows_composition.bindings → type in windows_core.inspectable) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_composition.bindings.ICompositionAnimation2_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionAnimationBase_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionAnimationGroup_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionAnimation_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionBatchCompletedEventArgs_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionBrush_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionColorBrush_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionContainerShape_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionDrawingSurface_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionEasingFunction_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionEllipseGeometry_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionGeometry_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionGraphicsDevice_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionNineGridBrush_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionObject2_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionObject_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionRoundedRectangleGeometry_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionScopedBatch_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionShape_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionSpriteShape_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionSurfaceBrush_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionSurface_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositionTarget_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositor2_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_composition.bindings.ICompositor5_Vtbl → windows_core.inspectable.IInspectable_Vtbl

Direction

windows_composition.bindings uses windows_core.inspectable. Changing windows_core.inspectable can break windows_composition.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

31→37 windows_composition.bindings depends on windows_core.unknown cycle✕

Type pairs

86 distinct (type in windows_composition.bindings → type in windows_core.unknown) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_composition.bindings.CompositionAnimation → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionAnimationGroup → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionBatchCompletedEventArgs → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionBrush → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionColorBrush → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionContainerShape → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionDrawingSurface → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionEasingFunction → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionEllipseGeometry → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionGeometry → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionGraphicsDevice → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionNineGridBrush → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionObject → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionRoundedRectangleGeometry → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionScopedBatch → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionShape → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionShapeCollection → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionSpriteShape → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionSurfaceBrush → windows_core.unknown.IUnknown
• windows_composition.bindings.CompositionTarget → windows_core.unknown.IUnknown
• windows_composition.bindings.Compositor → windows_core.unknown.IUnknown
• windows_composition.bindings.ContainerVisual → windows_core.unknown.IUnknown
• windows_composition.bindings.CubicBezierEasingFunction → windows_core.unknown.IUnknown
• windows_composition.bindings.DesktopWindowTarget → windows_core.unknown.IUnknown
• windows_composition.bindings.DispatcherQueueController → windows_core.unknown.IUnknown

Direction

windows_composition.bindings uses windows_core.unknown. Changing windows_core.unknown can break windows_composition.bindings, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

32→1 windows_reactor.native.winui.bindings depends on windows_bindgen.guid✕

Type pairs

3 distinct (type in windows_reactor.native.winui.bindings → type in windows_bindgen.guid) references.

Which types

• windows_reactor.native.winui.bindings.IApplicationOverrides_Vtbl → windows_bindgen.guid.GUID
• windows_reactor.native.winui.bindings.IElementFactory_Vtbl → windows_bindgen.guid.GUID
• windows_reactor.native.winui.bindings.IXamlMetadataProvider_Vtbl → windows_bindgen.guid.GUID

Direction

windows_reactor.native.winui.bindings uses windows_bindgen.guid. Changing windows_bindgen.guid can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→2 windows_reactor.native.winui.bindings depends on windows_core.imp.can_into✕

Type pairs

225 distinct (type in windows_reactor.native.winui.bindings → type in windows_core.imp.can_into) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_reactor.native.winui.bindings.AppBar → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AppBarButton → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AppBarSeparator → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AppWindow → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AppWindowPresenter → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AppWindowTitleBar → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.Application → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.ApplicationInitializationCallbackParams → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AutoSuggestBox → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AutoSuggestBoxSuggestionChosenEventArgs → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AutoSuggestBoxTextChangedEventArgs → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AutomationPeer → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.AutomationProperties → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.BitmapIcon → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.BitmapImage → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.BitmapSource → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.Block → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.BlockCollection → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.Border → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.BreadcrumbBar → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.BreadcrumbBarItemClickedEventArgs → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.Brush → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.Button → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.ButtonBase → windows_core.imp.can_into.CanInto
• windows_reactor.native.winui.bindings.CalendarDatePicker → windows_core.imp.can_into.CanInto

Direction

windows_reactor.native.winui.bindings uses windows_core.imp.can_into. Changing windows_core.imp.can_into can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→4 windows_reactor.native.winui.bindings depends on windows_core.runtime_name✕

Type pairs

217 distinct (type in windows_reactor.native.winui.bindings → type in windows_core.runtime_name) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_reactor.native.winui.bindings.AppBar → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AppBarButton → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AppBarSeparator → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AppWindow → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AppWindowPresenter → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AppWindowTitleBar → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.Application → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.ApplicationInitializationCallbackParams → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AutoSuggestBox → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AutoSuggestBoxSuggestionChosenEventArgs → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AutoSuggestBoxTextChangedEventArgs → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AutomationPeer → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.AutomationProperties → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.BitmapIcon → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.BitmapImage → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.BitmapSource → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.Block → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.BlockCollection → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.Border → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.BreadcrumbBar → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.BreadcrumbBarItemClickedEventArgs → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.Brush → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.Button → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.ButtonBase → windows_core.runtime_name.RuntimeName
• windows_reactor.native.winui.bindings.CalendarDatePicker → windows_core.runtime_name.RuntimeName

Direction

windows_reactor.native.winui.bindings uses windows_core.runtime_name. Changing windows_core.runtime_name can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→5 windows_reactor.native.winui.bindings depends on windows_core.type✕

Type pairs

50 distinct (type in windows_reactor.native.winui.bindings → type in windows_core.type) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_reactor.native.winui.bindings.AutomationHeadingLevel → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.Color → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.ContentDialogResult → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.CorePhysicalKeyStatus → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.CornerRadius → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.DataPackageOperation → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.DispatcherQueuePriority → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.DispatcherShutdownMode → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.ElementTheme → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.FlyoutPlacementMode → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.FocusState → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.FontStyle → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.FontWeight → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.GridLength → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.GridUnitType → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.HorizontalAlignment → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.InfoBarSeverity → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.KeyboardAcceleratorPlacementMode → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.ListViewSelectionMode → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.MicaKind → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.NavigationViewBackButtonVisible → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.NavigationViewDisplayMode → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.NavigationViewPaneDisplayMode → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.Orientation → windows_core.type.TypeKind
• windows_reactor.native.winui.bindings.PasswordRevealMode → windows_core.type.TypeKind

Direction

windows_reactor.native.winui.bindings uses windows_core.type. Changing windows_core.type can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→7 windows_reactor.native.winui.bindings depends on windows_bindgen.type_name✕

Type pairs

3 distinct (type in windows_reactor.native.winui.bindings → type in windows_bindgen.type_name) references.

Which types

• windows_reactor.native.winui.bindings.IXamlMetadataProvider → windows_bindgen.type_name.TypeName
• windows_reactor.native.winui.bindings.IXamlMetadataProvider_Impl → windows_bindgen.type_name.TypeName
• windows_reactor.native.winui.bindings.XamlBindingHelper → windows_bindgen.type_name.TypeName

Direction

windows_reactor.native.winui.bindings uses windows_bindgen.type_name. Changing windows_bindgen.type_name can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→9 windows_reactor.native.winui.bindings depends on windows_reactor.element✕

Type pairs

14 distinct (type in windows_reactor.native.winui.bindings → type in windows_reactor.element) references.

Which types

• windows_reactor.native.winui.bindings.AutomationProperties → windows_reactor.element.AutomationHeadingLevel
• windows_reactor.native.winui.bindings.IBorder → windows_reactor.element.CornerRadius
• windows_reactor.native.winui.bindings.IBorder → windows_reactor.element.Thickness
• windows_reactor.native.winui.bindings.IColumnDefinition → windows_reactor.element.GridLength
• windows_reactor.native.winui.bindings.IControl → windows_reactor.element.HorizontalAlignment
• windows_reactor.native.winui.bindings.IControl → windows_reactor.element.Thickness
• windows_reactor.native.winui.bindings.IControl → windows_reactor.element.VerticalAlignment
• windows_reactor.native.winui.bindings.IFrameworkElement → windows_reactor.element.HorizontalAlignment
• windows_reactor.native.winui.bindings.IFrameworkElement → windows_reactor.element.Thickness
• windows_reactor.native.winui.bindings.IFrameworkElement → windows_reactor.element.VerticalAlignment
• windows_reactor.native.winui.bindings.IKeyboardAccelerator → windows_reactor.element.VirtualKey
• windows_reactor.native.winui.bindings.IRowDefinition → windows_reactor.element.GridLength
• windows_reactor.native.winui.bindings.ITextBlock → windows_reactor.element.FontWeight
• windows_reactor.native.winui.bindings.ITextElement → windows_reactor.element.FontWeight

Direction

windows_reactor.native.winui.bindings uses windows_reactor.element. Changing windows_reactor.element can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→17 windows_reactor.native.winui.bindings depends on windows_result.hresult✕

Type pairs

16 distinct (type in windows_reactor.native.winui.bindings → type in windows_result.hresult) references.

Which types

• windows_reactor.native.winui.bindings.ApplicationInitializationCallbackBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.DependencyPropertyChangedCallbackBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.DispatcherQueueHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.DragEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.EventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.ExceptionRoutedEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.ISwapChainPanelNative → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.IWindowNative → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.KeyEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.PointerEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.RangeBaseValueChangedEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.RoutedEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.SelectionChangedEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.SizeChangedEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.TextChangedEventHandlerBox → windows_result.hresult.HRESULT
• windows_reactor.native.winui.bindings.TypedEventHandlerBox → windows_result.hresult.HRESULT

Direction

windows_reactor.native.winui.bindings uses windows_result.hresult. Changing windows_result.hresult can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→20 windows_reactor.native.winui.bindings depends on windows_core.runtime_type✕

Type pairs

668 distinct (type in windows_reactor.native.winui.bindings → type in windows_core.runtime_type) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_reactor.native.winui.bindings.AppBar → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AppBarButton → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AppBarSeparator → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AppWindow → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AppWindowPresenter → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AppWindowTitleBar → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.Application → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.ApplicationInitializationCallback → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.ApplicationInitializationCallbackParams → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AutoSuggestBox → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AutoSuggestBoxSuggestionChosenEventArgs → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AutoSuggestBoxTextChangedEventArgs → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AutomationHeadingLevel → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AutomationPeer → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.AutomationProperties → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.BitmapIcon → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.BitmapImage → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.BitmapSource → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.Block → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.BlockCollection → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.Border → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.BreadcrumbBar → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.BreadcrumbBarItemClickedEventArgs → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.Brush → windows_core.runtime_type.RuntimeType
• windows_reactor.native.winui.bindings.Button → windows_core.runtime_type.RuntimeType

Direction

windows_reactor.native.winui.bindings uses windows_core.runtime_type. Changing windows_core.runtime_type can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→21 windows_reactor.native.winui.bindings depends on windows_bindgen.types.interface✕

Type pairs

620 distinct (type in windows_reactor.native.winui.bindings → type in windows_bindgen.types.interface) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_reactor.native.winui.bindings.AppBar → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AppBarButton → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AppBarSeparator → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AppWindow → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AppWindowPresenter → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AppWindowTitleBar → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.Application → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.ApplicationInitializationCallback → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.ApplicationInitializationCallbackParams → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AutoSuggestBox → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AutoSuggestBoxSuggestionChosenEventArgs → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AutoSuggestBoxTextChangedEventArgs → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AutomationPeer → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.AutomationProperties → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.BitmapIcon → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.BitmapImage → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.BitmapSource → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.Block → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.BlockCollection → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.Border → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.BreadcrumbBar → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.BreadcrumbBarItemClickedEventArgs → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.Brush → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.Button → windows_bindgen.types.interface.Interface
• windows_reactor.native.winui.bindings.ButtonBase → windows_bindgen.types.interface.Interface

Direction

windows_reactor.native.winui.bindings uses windows_bindgen.types.interface. Changing windows_bindgen.types.interface can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→22 windows_reactor.native.winui.bindings depends on windows_numerics.bindings✕

Type pairs

1 distinct (type in windows_reactor.native.winui.bindings → type in windows_numerics.bindings) reference.

Which types

• windows_reactor.native.winui.bindings.IUIElement → windows_numerics.bindings.Vector3

Direction

windows_reactor.native.winui.bindings uses windows_numerics.bindings. Changing windows_numerics.bindings can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→23 windows_reactor.native.winui.bindings depends on windows_strings.hstring✕

Type pairs

4 distinct (type in windows_reactor.native.winui.bindings → type in windows_strings.hstring) references.

Which types

• windows_reactor.native.winui.bindings.ITextDocument → windows_strings.hstring.HSTRING
• windows_reactor.native.winui.bindings.IXamlMetadataProvider_Impl → windows_strings.hstring.HSTRING
• windows_reactor.native.winui.bindings.TypeName → windows_strings.hstring.HSTRING
• windows_reactor.native.winui.bindings.XmlnsDefinition → windows_strings.hstring.HSTRING

Direction

windows_reactor.native.winui.bindings uses windows_strings.hstring. Changing windows_strings.hstring can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→24 windows_reactor.native.winui.bindings depends on windows_time.bindings✕

Type pairs

6 distinct (type in windows_reactor.native.winui.bindings → type in windows_time.bindings) references.

Which types

• windows_reactor.native.winui.bindings.ICalendarDatePicker → windows_time.bindings.DateTime
• windows_reactor.native.winui.bindings.IDatePicker → windows_time.bindings.DateTime
• windows_reactor.native.winui.bindings.IDispatcherQueueTimer → windows_time.bindings.TimeSpan
• windows_reactor.native.winui.bindings.IScalarTransition → windows_time.bindings.TimeSpan
• windows_reactor.native.winui.bindings.ITimePicker → windows_time.bindings.TimeSpan
• windows_reactor.native.winui.bindings.IVector3Transition → windows_time.bindings.TimeSpan

Direction

windows_reactor.native.winui.bindings uses windows_time.bindings. Changing windows_time.bindings can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→29 windows_reactor.native.winui.bindings depends on windows_core.inspectable✕

Type pairs

390 distinct (type in windows_reactor.native.winui.bindings → type in windows_core.inspectable) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_reactor.native.winui.bindings.IAppBarButtonFactory_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppBarButtonStatics_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppBarButton_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppBarSeparatorFactory_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppBarSeparator_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppBar_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppWindow2_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppWindowPresenter_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppWindowTitleBar2_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppWindowTitleBar3_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppWindowTitleBar_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAppWindow_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IApplication3_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IApplicationFactory_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IApplicationInitializationCallbackParams_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IApplicationOverrides_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IApplicationStatics_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IApplication_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAutoSuggestBoxStatics_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAutoSuggestBoxSuggestionChosenEventArgs_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAutoSuggestBoxTextChangedEventArgs_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAutoSuggestBox_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAutomationPeer_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAutomationPropertiesStatics_Vtbl → windows_core.inspectable.IInspectable_Vtbl
• windows_reactor.native.winui.bindings.IAutomationProperties_Vtbl → windows_core.inspectable.IInspectable_Vtbl

Direction

windows_reactor.native.winui.bindings uses windows_core.inspectable. Changing windows_core.inspectable can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→31 windows_reactor.native.winui.bindings depends on windows_composition.bindings✕

Type pairs

2 distinct (type in windows_reactor.native.winui.bindings → type in windows_composition.bindings) references.

Which types

• windows_reactor.native.winui.bindings.IColorPicker → windows_composition.bindings.Color
• windows_reactor.native.winui.bindings.ISolidColorBrush → windows_composition.bindings.Color

Direction

windows_reactor.native.winui.bindings uses windows_composition.bindings. Changing windows_composition.bindings can break windows_reactor.native.winui.bindings, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

32→37 windows_reactor.native.winui.bindings depends on windows_core.unknown cycle✕

Type pairs

639 distinct (type in windows_reactor.native.winui.bindings → type in windows_core.unknown) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows_reactor.native.winui.bindings.AppBar → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AppBarButton → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AppBarSeparator → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AppWindow → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AppWindowPresenter → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AppWindowTitleBar → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.Application → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.ApplicationInitializationCallback → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.ApplicationInitializationCallbackParams → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.ApplicationInitializationCallback_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows_reactor.native.winui.bindings.AutoSuggestBox → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AutoSuggestBoxSuggestionChosenEventArgs → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AutoSuggestBoxTextChangedEventArgs → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AutomationPeer → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.AutomationProperties → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.BitmapIcon → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.BitmapImage → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.BitmapSource → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.Block → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.BlockCollection → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.Border → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.BreadcrumbBar → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.BreadcrumbBarItemClickedEventArgs → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.Brush → windows_core.unknown.IUnknown
• windows_reactor.native.winui.bindings.Button → windows_core.unknown.IUnknown

Direction

windows_reactor.native.winui.bindings uses windows_core.unknown. Changing windows_core.unknown can break windows_reactor.native.winui.bindings, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

33→1 windows.Windows.Win32.oaidl depends on windows_bindgen.guid✕

Type pairs

26 distinct (type in windows.Windows.Win32.oaidl → type in windows_bindgen.guid) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows.Windows.Win32.oaidl.CUSTDATAITEM → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ICreateErrorInfo_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ICreateTypeInfo2_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ICreateTypeInfo_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ICreateTypeLib2_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ICreateTypeLib_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.IDispatch_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.IEnumVARIANT_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.IErrorInfo_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.IErrorLog_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.IPropertyBag_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.IRecordInfo_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ISupportErrorInfo_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeChangeEvents_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeComp_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeFactory_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeInfo2_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeInfo_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeLib2_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeLibRegistrationReader_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeLibRegistration_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeLib_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.ITypeMarshal_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.SAFEARR_HAVEIID → windows_bindgen.guid.GUID
• windows.Windows.Win32.oaidl.TLIBATTR → windows_bindgen.guid.GUID

Direction

windows.Windows.Win32.oaidl uses windows_bindgen.guid. Changing windows_bindgen.guid can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→2 windows.Windows.Win32.oaidl depends on windows_core.imp.can_into✕

Type pairs

22 distinct (type in windows.Windows.Win32.oaidl → type in windows_core.imp.can_into) references.

Which types

• windows.Windows.Win32.oaidl.ICreateErrorInfo → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ICreateTypeInfo → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ICreateTypeInfo2 → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ICreateTypeLib → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ICreateTypeLib2 → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.IDispatch → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.IEnumVARIANT → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.IErrorInfo → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.IErrorLog → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.IPropertyBag → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.IRecordInfo → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ISupportErrorInfo → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeChangeEvents → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeComp → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeFactory → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeInfo → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeInfo2 → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeLib → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeLib2 → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeLibRegistration → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeLibRegistrationReader → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.oaidl.ITypeMarshal → windows_core.imp.can_into.CanInto

Direction

windows.Windows.Win32.oaidl uses windows_core.imp.can_into. Changing windows_core.imp.can_into can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→3 windows.Windows.Win32.oaidl depends on windows_core.out_ref✕

Type pairs

3 distinct (type in windows.Windows.Win32.oaidl → type in windows_core.out_ref) references.

Which types

• windows.Windows.Win32.oaidl.ITypeComp_Impl → windows_core.out_ref.OutRef
• windows.Windows.Win32.oaidl.ITypeInfo_Impl → windows_core.out_ref.OutRef
• windows.Windows.Win32.oaidl.ITypeLib_Impl → windows_core.out_ref.OutRef

Direction

windows.Windows.Win32.oaidl uses windows_core.out_ref. Changing windows_core.out_ref can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→4 windows.Windows.Win32.oaidl depends on windows_core.runtime_name✕

Type pairs

22 distinct (type in windows.Windows.Win32.oaidl → type in windows_core.runtime_name) references.

Which types

• windows.Windows.Win32.oaidl.ICreateErrorInfo → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ICreateTypeInfo → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ICreateTypeInfo2 → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ICreateTypeLib → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ICreateTypeLib2 → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.IDispatch → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.IEnumVARIANT → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.IErrorInfo → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.IErrorLog → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.IPropertyBag → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.IRecordInfo → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ISupportErrorInfo → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeChangeEvents → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeComp → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeFactory → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeInfo → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeInfo2 → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeLib → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeLib2 → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeLibRegistration → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeLibRegistrationReader → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.oaidl.ITypeMarshal → windows_core.runtime_name.RuntimeName

Direction

windows.Windows.Win32.oaidl uses windows_core.runtime_name. Changing windows_core.runtime_name can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→6 windows.Windows.Win32.oaidl depends on windows_result.bool✕

Type pairs

2 distinct (type in windows.Windows.Win32.oaidl → type in windows_result.bool) references.

Which types

• windows.Windows.Win32.oaidl.IRecordInfo → windows_result.bool.BOOL
• windows.Windows.Win32.oaidl.IRecordInfo_Impl → windows_result.bool.BOOL

Direction

windows.Windows.Win32.oaidl uses windows_result.bool. Changing windows_result.bool can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→11 windows.Windows.Win32.oaidl depends on windows_strings.bstr✕

Type pairs

2 distinct (type in windows.Windows.Win32.oaidl → type in windows_strings.bstr) references.

Which types

• windows.Windows.Win32.oaidl.ICreateTypeInfo → windows_strings.bstr.BSTR
• windows.Windows.Win32.oaidl.ICreateTypeInfo_Impl → windows_strings.bstr.BSTR

Direction

windows.Windows.Win32.oaidl uses windows_strings.bstr. Changing windows_strings.bstr can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→15 windows.Windows.Win32.oaidl depends on windows_sys.Windows.Win32.oaidl✕

Type pairs

7 distinct (type in windows.Windows.Win32.oaidl → type in windows_sys.Windows.Win32.oaidl) references.

Which types

• windows.Windows.Win32.oaidl.ARRAYDESC → windows_sys.Windows.Win32.oaidl.TYPEDESC
• windows.Windows.Win32.oaidl.ELEMDESC → windows_sys.Windows.Win32.oaidl.TYPEDESC
• windows.Windows.Win32.oaidl.FUNCDESC → windows_sys.Windows.Win32.oaidl.ELEMDESC
• windows.Windows.Win32.oaidl.TYPEATTR → windows_sys.Windows.Win32.oaidl.IDLDESC
• windows.Windows.Win32.oaidl.TYPEATTR → windows_sys.Windows.Win32.oaidl.TYPEDESC
• windows.Windows.Win32.oaidl.VARDESC → windows_sys.Windows.Win32.oaidl.ELEMDESC
• windows.Windows.Win32.oaidl._wireSAFEARRAY → windows_sys.Windows.Win32.oaidl.SAFEARRAYUNION

Direction

windows.Windows.Win32.oaidl uses windows_sys.Windows.Win32.oaidl. Changing windows_sys.Windows.Win32.oaidl can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→17 windows.Windows.Win32.oaidl depends on windows_result.hresult✕

Type pairs

18 distinct (type in windows.Windows.Win32.oaidl → type in windows_result.hresult) references.

Which types

• windows.Windows.Win32.oaidl.ICreateErrorInfo → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ICreateTypeInfo → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ICreateTypeInfo2 → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ICreateTypeLib → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ICreateTypeLib2 → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.IDispatch → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.IEnumVARIANT → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.IErrorLog → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.IPropertyBag → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.IRecordInfo → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ISupportErrorInfo → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ITypeChangeEvents → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ITypeComp → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ITypeInfo → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ITypeInfo2 → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ITypeLib → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ITypeLib2 → windows_result.hresult.HRESULT
• windows.Windows.Win32.oaidl.ITypeMarshal → windows_result.hresult.HRESULT

Direction

windows.Windows.Win32.oaidl uses windows_result.hresult. Changing windows_result.hresult can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→21 windows.Windows.Win32.oaidl depends on windows_bindgen.types.interface✕

Type pairs

22 distinct (type in windows.Windows.Win32.oaidl → type in windows_bindgen.types.interface) references.

Which types

• windows.Windows.Win32.oaidl.ICreateErrorInfo → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ICreateTypeInfo → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ICreateTypeInfo2 → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ICreateTypeLib → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ICreateTypeLib2 → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.IDispatch → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.IEnumVARIANT → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.IErrorInfo → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.IErrorLog → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.IPropertyBag → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.IRecordInfo → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ISupportErrorInfo → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeChangeEvents → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeComp → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeFactory → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeInfo → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeInfo2 → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeLib → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeLib2 → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeLibRegistration → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeLibRegistrationReader → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.oaidl.ITypeMarshal → windows_bindgen.types.interface.Interface

Direction

windows.Windows.Win32.oaidl uses windows_bindgen.types.interface. Changing windows_bindgen.types.interface can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→32 windows.Windows.Win32.oaidl depends on windows_reactor.native.winui.bindings✕

Type pairs

1 distinct (type in windows.Windows.Win32.oaidl → type in windows_reactor.native.winui.bindings) reference.

Which types

• windows.Windows.Win32.oaidl.IDispatch → windows_reactor.native.winui.bindings.ITextDocument

Direction

windows.Windows.Win32.oaidl uses windows_reactor.native.winui.bindings. Changing windows_reactor.native.winui.bindings can break windows.Windows.Win32.oaidl, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

33→37 windows.Windows.Win32.oaidl depends on windows_core.unknown cycle✕

Type pairs

58 distinct (type in windows.Windows.Win32.oaidl → type in windows_core.unknown) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows.Windows.Win32.oaidl.ICreateErrorInfo → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.ICreateErrorInfo_Impl → windows_core.unknown.IUnknownImpl
• windows.Windows.Win32.oaidl.ICreateErrorInfo_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows.Windows.Win32.oaidl.ICreateTypeInfo → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.ICreateTypeInfo2 → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.ICreateTypeInfo_Impl → windows_core.unknown.IUnknownImpl
• windows.Windows.Win32.oaidl.ICreateTypeInfo_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows.Windows.Win32.oaidl.ICreateTypeLib → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.ICreateTypeLib2 → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.ICreateTypeLib_Impl → windows_core.unknown.IUnknownImpl
• windows.Windows.Win32.oaidl.ICreateTypeLib_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows.Windows.Win32.oaidl.IDispatch → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.IDispatch_Impl → windows_core.unknown.IUnknownImpl
• windows.Windows.Win32.oaidl.IDispatch_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows.Windows.Win32.oaidl.IEnumVARIANT → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.IEnumVARIANT_Impl → windows_core.unknown.IUnknownImpl
• windows.Windows.Win32.oaidl.IEnumVARIANT_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows.Windows.Win32.oaidl.IErrorInfo → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.IErrorInfo_Impl → windows_core.unknown.IUnknownImpl
• windows.Windows.Win32.oaidl.IErrorInfo_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows.Windows.Win32.oaidl.IErrorLog → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.IErrorLog_Impl → windows_core.unknown.IUnknownImpl
• windows.Windows.Win32.oaidl.IErrorLog_Vtbl → windows_core.unknown.IUnknown_Vtbl
• windows.Windows.Win32.oaidl.IPropertyBag → windows_core.unknown.IUnknown
• windows.Windows.Win32.oaidl.IPropertyBag_Impl → windows_core.unknown.IUnknownImpl

Direction

windows.Windows.Win32.oaidl uses windows_core.unknown. Changing windows_core.unknown can break windows.Windows.Win32.oaidl, not the reverse.

Position

Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.

34→1 windows.Windows.Win32.shobjidl_core depends on windows_bindgen.guid✕

Type pairs

197 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_bindgen.guid) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows.Windows.Win32.shobjidl_core.EXTRASEARCH → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IActionProgressDialog_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IActionProgress_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IAppActivationUIInfo_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IAppVisibilityEvents_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IAppVisibility_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IApplicationActivationManager_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IApplicationAssociationRegistration_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings2_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IApplicationDestinations_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IApplicationDocumentLists_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IAssocHandlerInvoker_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IAssocHandler_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute2_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IBandSite_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IBannerNotificationHandler_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IBrowserFrameOptions_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.ICategorizer_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.ICategoryProvider_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IColumnManager_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser2_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser_Vtbl → windows_bindgen.guid.GUID
• windows.Windows.Win32.shobjidl_core.IContactManagerInterop_Vtbl → windows_bindgen.guid.GUID

Direction

windows.Windows.Win32.shobjidl_core uses windows_bindgen.guid. Changing windows_bindgen.guid can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

34→2 windows.Windows.Win32.shobjidl_core depends on windows_core.imp.can_into✕

Type pairs

195 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_core.imp.can_into) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows.Windows.Win32.shobjidl_core.IActionProgress → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IActionProgressDialog → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IAppActivationUIInfo → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IAppVisibility → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IAppVisibilityEvents → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IApplicationActivationManager → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IApplicationAssociationRegistration → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings2 → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IApplicationDestinations → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IApplicationDocumentLists → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IAssocHandler → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IAssocHandlerInvoker → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute2 → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IBandSite → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IBannerNotificationHandler → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IBrowserFrameOptions → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.ICategorizer → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.ICategoryProvider → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IColumnManager → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser2 → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IContactManagerInterop → windows_core.imp.can_into.CanInto
• windows.Windows.Win32.shobjidl_core.IContextMenu → windows_core.imp.can_into.CanInto

Direction

windows.Windows.Win32.shobjidl_core uses windows_core.imp.can_into. Changing windows_core.imp.can_into can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

34→3 windows.Windows.Win32.shobjidl_core depends on windows_core.out_ref✕

Type pairs

3 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_core.out_ref) references.

Which types

• windows.Windows.Win32.shobjidl_core.IBandSite_Impl → windows_core.out_ref.OutRef
• windows.Windows.Win32.shobjidl_core.IParentAndItem_Impl → windows_core.out_ref.OutRef
• windows.Windows.Win32.shobjidl_core.IShellMenu_Impl → windows_core.out_ref.OutRef

Direction

windows.Windows.Win32.shobjidl_core uses windows_core.out_ref. Changing windows_core.out_ref can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

34→4 windows.Windows.Win32.shobjidl_core depends on windows_core.runtime_name✕

Type pairs

195 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_core.runtime_name) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows.Windows.Win32.shobjidl_core.IActionProgress → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IActionProgressDialog → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IAppActivationUIInfo → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IAppVisibility → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IAppVisibilityEvents → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IApplicationActivationManager → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IApplicationAssociationRegistration → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings2 → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IApplicationDestinations → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IApplicationDocumentLists → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IAssocHandler → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IAssocHandlerInvoker → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute2 → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IBandSite → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IBannerNotificationHandler → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IBrowserFrameOptions → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.ICategorizer → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.ICategoryProvider → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IColumnManager → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser2 → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IContactManagerInterop → windows_core.runtime_name.RuntimeName
• windows.Windows.Win32.shobjidl_core.IContextMenu → windows_core.runtime_name.RuntimeName

Direction

windows.Windows.Win32.shobjidl_core uses windows_core.runtime_name. Changing windows_core.runtime_name can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

34→6 windows.Windows.Win32.shobjidl_core depends on windows_result.bool✕

Type pairs

24 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_result.bool) references.

Which types

• windows.Windows.Win32.shobjidl_core.IActionProgress_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IAppVisibilityEvents_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings2_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IDesktopWallpaper_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IDockingWindow_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IDropTargetHelper_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IExecuteCommand_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IExplorerCommandState_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IExplorerCommand_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IFileDialogCustomize_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IFileSaveDialog_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IFolderView2_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IFrameworkInputPaneHandler_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IInputObjectSite_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IInputObject_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IMenuPopup_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.INewWindowManager_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IRegTreeItem_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IRemoteComputer_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IRunnableTask_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IShellBrowser_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IShellTaskScheduler_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.IShellView_Impl → windows_result.bool.BOOL
• windows.Windows.Win32.shobjidl_core.ITaskbarList2_Impl → windows_result.bool.BOOL

Direction

windows.Windows.Win32.shobjidl_core uses windows_result.bool. Changing windows_result.bool can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

34→12 windows.Windows.Win32.shobjidl_core depends on windows_strings.pcstr✕

Type pairs

5 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_strings.pcstr) references.

Which types

• windows.Windows.Win32.shobjidl_core.CMINVOKECOMMANDINFO → windows_strings.pcstr.PCSTR
• windows.Windows.Win32.shobjidl_core.CMINVOKECOMMANDINFOEX → windows_strings.pcstr.PCSTR
• windows.Windows.Win32.shobjidl_core.CMINVOKECOMMANDINFOEX_REMOTE → windows_strings.pcstr.PCSTR
• windows.Windows.Win32.shobjidl_core.IFolderView2_Impl → windows_strings.pcstr.PCSTR
• windows.Windows.Win32.shobjidl_core.IShellLinkA_Impl → windows_strings.pcstr.PCSTR

Direction

windows.Windows.Win32.shobjidl_core uses windows_strings.pcstr. Changing windows_strings.pcstr can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

34→13 windows.Windows.Win32.shobjidl_core depends on windows_strings.pstr✕

Type pairs

2 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_strings.pstr) references.

Which types

• windows.Windows.Win32.shobjidl_core.IShellLinkA → windows_strings.pstr.PSTR
• windows.Windows.Win32.shobjidl_core.IShellLinkA_Impl → windows_strings.pstr.PSTR

Direction

windows.Windows.Win32.shobjidl_core uses windows_strings.pstr. Changing windows_strings.pstr can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

34→17 windows.Windows.Win32.shobjidl_core depends on windows_result.hresult✕

Type pairs

161 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_result.hresult) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows.Windows.Win32.shobjidl_core.IActionProgress → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IActionProgressDialog → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IAppVisibility → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IAppVisibilityEvents → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IApplicationAssociationRegistration → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings2 → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IApplicationDestinations → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IApplicationDocumentLists → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IAssocHandler → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IAssocHandlerInvoker → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute2 → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IBandSite → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IBannerNotificationHandler → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.ICategorizer → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.ICategoryProvider → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IColumnManager → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser2 → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IContactManagerInterop → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IContextMenu → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IContextMenu2 → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IContextMenu3 → windows_result.hresult.HRESULT
• windows.Windows.Win32.shobjidl_core.IContextMenuCB → windows_result.hresult.HRESULT

Direction

windows.Windows.Win32.shobjidl_core uses windows_result.hresult. Changing windows_result.hresult can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.

34→21 windows.Windows.Win32.shobjidl_core depends on windows_bindgen.types.interface✕

Type pairs

195 distinct (type in windows.Windows.Win32.shobjidl_core → type in windows_bindgen.types.interface) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.

Which types

• windows.Windows.Win32.shobjidl_core.IActionProgress → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IActionProgressDialog → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IAppActivationUIInfo → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IAppVisibility → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IAppVisibilityEvents → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IApplicationActivationManager → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IApplicationAssociationRegistration → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IApplicationDesignModeSettings2 → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IApplicationDestinations → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IApplicationDocumentLists → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IAssocHandler → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IAssocHandlerInvoker → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IAttachmentExecute2 → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IBandSite → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IBannerNotificationHandler → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IBrowserFrameOptions → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.ICategorizer → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.ICategoryProvider → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IColumnManager → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.ICommDlgBrowser2 → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IContactManagerInterop → windows_bindgen.types.interface.Interface
• windows.Windows.Win32.shobjidl_core.IContextMenu → windows_bindgen.types.interface.Interface

Direction

windows.Windows.Win32.shobjidl_core uses windows_bindgen.types.interface. Changing windows_bindgen.types.interface can break windows.Windows.Win32.shobjidl_core, not the reverse.

Position

Below the diagonal — points down the layering, which is what you want.