Interface '{0}' and '{1}' implemented on Type '{3}' are considered projected to Windows Runtime interface '{2}' and all methods on both interface '{0}' and '{1}' needs to be either all implicitly implemented or explicitly implemented. As a result, all methods on this interface '{2}' will be exported as public and you might encounter name collisions.
Insufficient memory to meet the expected demands of an operation, and this system is likely to never satisfy this request ...
Insufficient memory to meet the expected demands of an operation, and this system is likely to never satisfy this request. ...
Insufficient stack to continue executing the program safely. This can happen from having too many functions on the call stack ...
Interface '%ls' is marked as dual], but does not derive from IDispatch. It will be converted as an IUnknown-derived interface. ...
Interface '{0}' and '{1}' implemented on Type '{3}' are considered projected to Windows Runtime interface '{2}' and all methods ...
Interface '{0}' and '{1}' implemented on Type '{3}' are considered projected to Windows Runtime interface '{2}' and all methods ...
Interface '{0}' implemented on Type '{2}' is considered projected to Windows Runtime interface '{1}' and all methods on this ...
Interface '{0}' implemented on Type '{2}' is considered projected to Windows Runtime interface '{1}' and all methods on this ...
Interface '{0}' is not a valid MetadataView; MetadataViews do not support non-public interfaces, and interfaces that contain ...