locked
Metro app execution cycle? Is it different for XAML metro app & Javascript metro app?

    Question

  • I have multiple question :)

    1.What is metro app execution cycle?

    2.Is the cycle different for XAML metro app & Javascript Metro app?

    3.What is role of WWAHost.exe in executing metro app (i know its superset of IE).

    4. Does the same exe host xaml-metro app also?

    Thanks a lot in advance..

    Wednesday, July 18, 2012 6:50 AM

Answers

  • Hi Manish,

    1. Application lifecycle (Metro style apps) 

    2. No

    3.  WWAHost.exe is the host process for HTML/JavaScript apps

    4. XAML apps do not run in WWAHost.exe

    -Jeff


    Jeff Sanders (MSFT)

    Wednesday, July 18, 2012 2:16 PM
    Moderator
  • Hi

    a)It because the WWAHost.exe provides an Internet Explorer-based rendering platform, direct ports are easily accomplished if your app uses HTML, CSS, and JavaScript technologies exclusively. It's not for xmal apps.

    b)They have same cycle , Javascript  is first-class citizen in the WinRT ecosystem, they have same winRT API, You can see the architecture below.

    • Marked as answer by Dino He Thursday, July 26, 2012 8:26 AM
    Thursday, July 19, 2012 4:50 PM

All replies

  • Hi Manish,

    1. Application lifecycle (Metro style apps) 

    2. No

    3.  WWAHost.exe is the host process for HTML/JavaScript apps

    4. XAML apps do not run in WWAHost.exe

    -Jeff


    Jeff Sanders (MSFT)

    Wednesday, July 18, 2012 2:16 PM
    Moderator
  • Thanks a lot for reply.

    Based on answers it raised my doubt further :)

    a) Everywhere i read, Metro apps can be developed using XAML/C# & Html5/js, then why WWAHost.exe only used for html/js metro apps, not for xaml metro apps ??? What is so diff between two approaches?

    b) I was not clear in asking the "Execution Cycle" question (trying now):

    i)C#+XAML => Converted to single class => compiled to IL => Code executed by OS +CLR (pls correct me if i am wrong here)

    ii)HTML5+Javascript => ? => ? => ...... (I have no idea what happens here)

    Curiously waiting for replies :)


    Manishabb2011


    Thursday, July 19, 2012 5:51 AM
  • Hi

    a)It because the WWAHost.exe provides an Internet Explorer-based rendering platform, direct ports are easily accomplished if your app uses HTML, CSS, and JavaScript technologies exclusively. It's not for xmal apps.

    b)They have same cycle , Javascript  is first-class citizen in the WinRT ecosystem, they have same winRT API, You can see the architecture below.

    • Marked as answer by Dino He Thursday, July 26, 2012 8:26 AM
    Thursday, July 19, 2012 4:50 PM