Not sure if this is an issue but I have been working through your new course Windows Runtime Internals on Pluralsight and I grabbed a copy of the implements class template from here to use.

When I compile the standard c++ project in the 'Core Apps in Standard C++' module with the class template I get the following compiler error:

error C2440: 'static_cast': cannot convert from 'const Modern::Implements<ABI::Windows::ApplicationModel::Core::IFrameworkView,ABI::Windows::ApplicationModel::Core::IFrameworkViewSource> *const ' to 'ABI::Windows::ApplicationModel::Core::IFrameworkViewSource *'

When I double click the error it drops me in this function from the class template:

template <typename First, typename ... Rest>
void * FindInterface(GUID const & id) const noexcept
{
    if (id == __uuidof(First))
    {
        return static_cast<First *>(this);
    }
    return FindInterface<Rest ...>(id);
}

If I remove the const from the method the project builds without error.

Currently there is no way of authoring things modularly and/or consuming non-in-box APIs.
This is a bit of a blocker for me, and I otherwise love the idea.

I noticed that you plan to make the compiler consume winmd instead of IDL, but that doesnt seem critical (for most use cases) as it can be worked around using winmdidl.exe. Right?

The Windows 8.1 does'nt compiler either under MSVC 2013 or 2013 with toolset set to V120. Errors on c++ features like 'noexcept'. How do set templates for both Win81 and Win10 development.

Seriously, everybody on earth and maybe up to the international space station uses the terms "Modern C++" for C++11 / C++14.

e.g. Effective Modern C++, etc... http://shop.oreilly.com/product/0636920033707.do

There is also "Modern C++ and Windows Store" that already has a foot hold in the Windows-specific world : http://www.amazon.fr/Modern-C-Windows-Store-Apps/dp/0989020800/ref=sr_1_5?s=english-books&ie=UTF8&qid=1438185205&sr=1-5&keywords=modern+c%2B%2B

I watched the video and read some articles on the site, but I'm confused how moderncpp can be related/compared to WRL when it comes to implementing my own classes. Is moderncpp supposed to be a replacement or extention to WRL? Can / should someone use them together? Could you please explain?

Searching online gives the closest matching result at https://social.msdn.microsoft.com/Forums/en-US/f16482b7-5873-48e1-9c77-0d3f7fea716c/visual-studio-2015-uwp-the-name-mapcontrol-does-not-exist-in-the-namespace?forum=vssetup

I'm sure this is something simple, but every project is unavailable and unloads.

I'm using VS2015 enterprise release with C++ installed, and the latest W10 SDK.

What am I missing?

Not really an issue, more like a feature request? The tool I am working on is a traditional systray app that currently uses the traditional core win32 function calls and some rather ugly code to read ini files. I'd like to start fresh with this, is there a way to create and register system tray windows with right click menus and such? I looked around but I didn't see any specific documentation dealing with this. Thanks!

I tried create a chain based on your example:

Windows::Foundation::IAsyncOperation<StorageFile> a = picker.PickSingleFileAsync().Completed([](auto const & sender, AsyncStatus)
            {
                if (StorageFile file = sender.GetResults())
                {
                    MODERN_TRACE(L"%ls\n", file.Name().Buffer());
                }
                else
                {
                    MODERN_TRACE(L"Canceled\n");
                }
            });

there an error with casting variable 'a':Error C2440 'initializing': cannot convert from 'void' to 'Modern::Windows::Foundation::IAsyncOperationModern::Windows::Storage::StorageFile' App app.cpp 58

Also I tried await functions like advised on StackOverflow:

auto dicop = Windows::Devices::Enumeration::DeviceInformation::FindAllAsync();

            dicop.Completed([](auto dicopint, AsyncStatus) 
            {
                auto f = dicopint.GetResults();
                auto name = f.First().Current().Name();
                MessageDialog dialog(name, L"Hello World!");
                dialog.ShowAsync();
            });
            while (dicop.Status() == AsyncStatus::Started)
            {
                try
                {
                    auto mcw = Windows::UI::Core::CoreWindow::GetForCurrentThread();
                    mcw.Dispatcher().ProcessEvents(CoreProcessEventsOption::ProcessAllIfPresent);
                }
                catch (Exception& ex)
                {
                    auto a = ex.Result;
                }
            }

(placed like previous code in KeyUp function)
the code under "try" throws E_UNEXPECTED.
CoreWindow returned by "Windows::UI::Core::CoreWindow::GetForCurrentThread();" same as the "window.KeyUp([](CoreWindow const &cw, KeyEventArgs const & args)" (from KeyUp calling).

Am I wrong using this?

Also where exceptions from namespace Platform (like, AccessDeniedException, COMException etc)? Is there for now only one of them - base (Modern::Exception)?

When trying to register a call back for a property change on a Text/Modern::String, I'm unable to get the value of the string. when I ran it to see the runtime class I got "Windows::Foundation::IReference'1"

        text.RegisterPropertyChangedCallback(text.TextProperty(), [](const DependencyObject& d, const DependencyProperty& p) 
        {
            const auto text_prop = d.GetValue(p);
            //text_prop.GetRuntimeClassName() = Windows::Foundation::IReference'1<String>
            const auto text_ref = text_prop.As<Windows::Foundation::IReference<String>>();
        });

The line with text_ref is giving me the compile error.
'Modern::ABI::Windows::Foundation::IReferenceModern::String': no GUID has been associated with this object

void Modern::Windows::Foundation::Collections::impl_IVectorModern::Windows::Foundation::Collections::IVectorModern::Windows::UI::Xaml::UIElement,T::Append(const T &) const': cannot convert argument 1 from 'Modern::Windows::UI::Xaml::Controls::Button' to 'const Modern::Windows::UI::Xaml::UIElement &'

I can't bind it to a context as well.

I've noticed (at least, in part of the code) that there's very little SAL in modern.... what's up with that?

Especially in COM-related code, I never cease to be amazed by how powerful SAL is, and I believe that it's indescribably valuable for any library code!

Side note: Does modern support VS2013? I haven't yet got my hands on 2015, and'd happily add the SAL myself.

I get interface not found for "ICompositor". The "Compositor" constructor fails in SetWindow

void SetWindow(CoreWindow const & window)
{
Compositor compositor;
ContainerVisual root = compositor.CreateContainerVisual();
....

Any way you can modify the generator tool to use forward slashes in the include statements? MSVC handles them fine, and then it increases the likelihood that other compilers and compilers hosted on other platforms can actually build the code.

Now I`m working on app that read files and parse it. I try port my code into your CoreApp sample.
First of all, app.cpp: code after line "CoreApplication::Run(make());" unreachable. I set after it "auto a=0" and set breakpoint - app never reaches this point.
Second - I try to use "Windows::Storage::Pickers::FileOpenPicker". Usually it needs to set "ViewMode" prop. So following code:
auto picker = Windows::Storage::Pickers::FileOpenPicker();
picker.FileTypeFilter.ViewMode = Windows::Storage::Pickers::PickerViewMode::List;
generates error c2228 (which is currently missing on msdn). It said "left of ViewMode must be a class, struct...". Also I unable set FileTypeFilter prop - member of it "Append" is missing. Assume that this prop
is Foundation::Vector<String^>