The underlying low-level api to create WinRT objects is RoCreateInstance(), same animal as the COM CoCreateInstance() function.
There are no C++/CX objects here, they are an implementation detail of the COM server. And various other tidbits, like having to use DateTimeOffset instead of DateTime, a side-effect of the language projection only mapping DateTimeOffset. It is not entirely invisible, you must for example declare your C# class sealed, a restriction brought on by COM only supporting interface inheritance, not implementation inheritance. Which in turn takes advantage of the existing COM interop built into the CLR. Taking advantage of the language projection built into the CLR. Much less visibly, your C# component is exposing the managed type as an unmanaged WinRT type. #Cx programmer dock cross reference window code#
Something similar happens in your C# code as well. The syntax resembles the managed C++/CLI language a lot, mostly because they were designed to solve the same problem, making interop with unmanaged types easy. Which are actually COM types under the hood. C++/CX is a pure unmanaged language extension, designed to make interop with WinRT types easy.
Where does dict reside? Who will release it?. When I pass cb to the Runtime component, does cb belongs to managed. Heard that cb and com point to some C++/CX objects (which reside IDictionary dict = com.CreateDictionary() WindowsPhoneRuntimeComponent com = new WindowsPhoneRuntimeComponent() Then I do CallbackImp cb = new CallbackImp () Public ref class WindowsPhoneRuntimeComponent sealedĬallbackImp, which implements ICallback. In C++ Runtime Component, I have public interface class ICallback I have a WP C++ Runtime Component that is to be consumed by a C# WP application.
0 kommentar(er)
