Now Windows can call the App class's implementations of the methods of IFrameworkView. So the App class serves as both view-provider factory and view-provider. It's that same App object that we created in wWinMain. And we've now supplied Windows with that view-provider. The IFrameworkView interfaceĪn object that implements IFrameworkView is a view-provider object. And you can see that it does in the listing above. Since IFrameworkViewSource::CreateView has a return value type of IFrameworkView, it follows that the App class needs to implement that interface, too. In other words, the App object returns itself. As you can see above, the App::CreateView implementation of that method returns *this.
Windows calls that function on the object that you pass to CoreApplication.Run. IFrameworkViewSource has the single method IFrameworkViewSource::CreateView. That object's job is to manufacture and return a view-provider object. struct App : winrt::implementsĪn object that implements IFrameworkViewSource is a view-provider factory object. The App class does indeed implement IFrameworkViewSource, as you can see in the listing below. Windows uses that view-provider to connect your app with the Windows shell so that you can handle application lifecycle events. Those interfaces (as well as CoreApplication.Run) represent a way for your app to supply Windows with a view-provider. The next two sections in this topic describe the IFrameworkViewSource and IFrameworkView interfaces. So the App class needs to implement that interface. Note that CoreApplication.Run expects an IFrameworkViewSource interface.
We make an instance of the App class (this is the one, and only, instance of App that's created), and we pass that to the static CoreApplication.Run method. int _stdcall wWinMain(HINSTANCE, HINSTANCE, PWSTR, int) Here's what wWinMain looks like (from App.cpp). The wWinMain function is the entry point for the app. But we'll refer to it as an app in order to talk more generally about how a Universal Windows Platform (UWP) app initializes. In this case, of course, we know that the app is a game. In there is the implementation of the App class, which represents the app and its lifecycle.
Sg project for windows code#
In your Core App project, open the source code file App.cpp. Review the App class to understand IFrameworkViewSource and IFrameworkView Target the latest generally-available (that is, not preview) version of the Windows SDK. Then, in Visual Studio, create a new project based on the Core App (C++/WinRT) project template.
Sg project for windows install#
For info about setting up Visual Studio for C++/WinRT development-including installing and using the C++/WinRT Visual Studio Extension (VSIX) and the NuGet package (which together provide project template and build support)-see Visual Studio support for C++/WinRT.įirst install (or update to) the latest version of the C++/WinRT Visual Studio Extension (VSIX) see the note above.
0 kommentar(er)
