Vista - Is an app written in XAML a managed app?

Hi,

If I write my application in XAML then is it a managed application?

Also, does WinFX (.NET 3.0) directly understand XAML or does it convert it
to something (say IL or something else) and then run this code at runtime?

Thanks,
- Manoj Agarwal

XAML is a design script, like HTML. It is not an application. XAML is just
XML. You will still need to either write code-behind (yes, making it a
managed app) or, when the added technology has been made available in a XAML
revision, write JScript or C#-script (making it a scripted app like an .hta
application).

The XAML parser and much of the renderer is managed; some of the rendering
is native, such as the 3D stuff.

Jon

"Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
news:41BC7217-201F-4A59-A4E4-93A3AAB84EE2@microsoft.com...
> Hi,
>
> If I write my application in XAML then is it a managed application?
>
> Also, does WinFX (.NET 3.0) directly understand XAML or does it convert it
> to something (say IL or something else) and then run this code at runtime?
>
> Thanks,
> - Manoj Agarwal

Hi Jon,

Thanks for your reply.

Another thing which I wanted to ask (you have made a mention of it in your
reply) is that I have read that WPF doesn't use the old User32\GDI+ graphic
sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.

If this is so then does it mean that WPF does not use the .NET 2.0 framework
for display purpose but uses native code?

If that is so then a WPF app is making calls to unmanaged code (i.e. the
native code). I believe that to make calls to unmanaged code from managed
code the app requires full-trust security. So do we require full-thrust to
run a simple WPF app?

Can you please help!

Thanks,
- Manoj


"Jon Davis" wrote:

> XAML is a design script, like HTML. It is not an application. XAML is just
> XML. You will still need to either write code-behind (yes, making it a
> managed app) or, when the added technology has been made available in a XAML
> revision, write JScript or C#-script (making it a scripted app like an .hta
> application).
>
> The XAML parser and much of the renderer is managed; some of the rendering
> is native, such as the 3D stuff.
>
> Jon
>
> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
> news:41BC7217-201F-4A59-A4E4-93A3AAB84EE2@microsoft.com...
> > Hi,
> >
> > If I write my application in XAML then is it a managed application?
> >
> > Also, does WinFX (.NET 3.0) directly understand XAML or does it convert it
> > to something (say IL or something else) and then run this code at runtime?
> >
> > Thanks,
> > - Manoj Agarwal
>
>
>

> Another thing which I wanted to ask (you have made a mention of it in your
> reply) is that I have read that WPF doesn't use the old User32\GDI+
> graphic
> sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.
>
> If this is so then does it mean that WPF does not use the .NET 2.0
> framework
> for display purpose but uses native code?

Most of WPF is managed code. You will be doing all of your work in managed
code. Direct3D is indeed utilized when a 3D card is available. D3D is
native. But that happens several layers below anything you touch.

> If that is so then a WPF app is making calls to unmanaged code (i.e. the
> native code). I believe that to make calls to unmanaged code from managed
> code the app requires full-trust security. So do we require full-thrust to
> run a simple WPF app?

Just as with WinForms, which at the underlying layers must make Win32 calls
behind the scenes, WPF hides the developer from those details as well. What
exactly do you mean by "full trust security"? The application should execute
from a trusted path as with WinForms, but you don't need to be
Administrator, for instance, to execute WPF applications.

--
Jon Davis

"Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
news:6FEAF906-A373-40D6-AEE0-399EAE8ED528@microsoft.com...
> Hi Jon,
>
> Thanks for your reply.
>
> Another thing which I wanted to ask (you have made a mention of it in your
> reply) is that I have read that WPF doesn't use the old User32\GDI+
> graphic
> sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.
>
> If this is so then does it mean that WPF does not use the .NET 2.0
> framework
> for display purpose but uses native code?
>
> If that is so then a WPF app is making calls to unmanaged code (i.e. the
> native code). I believe that to make calls to unmanaged code from managed
> code the app requires full-trust security. So do we require full-thrust to
> run a simple WPF app?
>
> Can you please help!
>
> Thanks,
> - Manoj
>
>
> "Jon Davis" wrote:
>
>> XAML is a design script, like HTML. It is not an application. XAML is
>> just
>> XML. You will still need to either write code-behind (yes, making it a
>> managed app) or, when the added technology has been made available in a
>> XAML
>> revision, write JScript or C#-script (making it a scripted app like an
>> .hta
>> application).
>>
>> The XAML parser and much of the renderer is managed; some of the
>> rendering
>> is native, such as the 3D stuff.
>>
>> Jon
>>
>> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
>> news:41BC7217-201F-4A59-A4E4-93A3AAB84EE2@microsoft.com...
>> > Hi,
>> >
>> > If I write my application in XAML then is it a managed application?
>> >
>> > Also, does WinFX (.NET 3.0) directly understand XAML or does it convert
>> > it
>> > to something (say IL or something else) and then run this code at
>> > runtime?
>> >
>> > Thanks,
>> > - Manoj Agarwal
>>
>>
>>

The basic confusion in my mind is that how can WPF (which is a layer over
..NET Framework 2.0) not use the grpahic sub-system used by .NET 2.0 but use
some other sub-system?

If a WPF app uses some other sub-system then will the app code be MSIL code
and can I view it in ILDASM?

Thanks for your patience with me


"Jon Davis" wrote:

> > Another thing which I wanted to ask (you have made a mention of it in your
> > reply) is that I have read that WPF doesn't use the old User32\GDI+
> > graphic
> > sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.
> >
> > If this is so then does it mean that WPF does not use the .NET 2.0
> > framework
> > for display purpose but uses native code?
>
> Most of WPF is managed code. You will be doing all of your work in managed
> code. Direct3D is indeed utilized when a 3D card is available. D3D is
> native. But that happens several layers below anything you touch.
>
> > If that is so then a WPF app is making calls to unmanaged code (i.e. the
> > native code). I believe that to make calls to unmanaged code from managed
> > code the app requires full-trust security. So do we require full-thrust to
> > run a simple WPF app?
>
> Just as with WinForms, which at the underlying layers must make Win32 calls
> behind the scenes, WPF hides the developer from those details as well. What
> exactly do you mean by "full trust security"? The application should execute
> from a trusted path as with WinForms, but you don't need to be
> Administrator, for instance, to execute WPF applications.
>
> --
> Jon Davis
>
> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
> news:6FEAF906-A373-40D6-AEE0-399EAE8ED528@microsoft.com...
> > Hi Jon,
> >
> > Thanks for your reply.
> >
> > Another thing which I wanted to ask (you have made a mention of it in your
> > reply) is that I have read that WPF doesn't use the old User32\GDI+
> > graphic
> > sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.
> >
> > If this is so then does it mean that WPF does not use the .NET 2.0
> > framework
> > for display purpose but uses native code?
> >
> > If that is so then a WPF app is making calls to unmanaged code (i.e. the
> > native code). I believe that to make calls to unmanaged code from managed
> > code the app requires full-trust security. So do we require full-thrust to
> > run a simple WPF app?
> >
> > Can you please help!
> >
> > Thanks,
> > - Manoj
> >
> >
> > "Jon Davis" wrote:
> >
> >> XAML is a design script, like HTML. It is not an application. XAML is
> >> just
> >> XML. You will still need to either write code-behind (yes, making it a
> >> managed app) or, when the added technology has been made available in a
> >> XAML
> >> revision, write JScript or C#-script (making it a scripted app like an
> >> .hta
> >> application).
> >>
> >> The XAML parser and much of the renderer is managed; some of the
> >> rendering
> >> is native, such as the 3D stuff.
> >>
> >> Jon
> >>
> >> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
> >> news:41BC7217-201F-4A59-A4E4-93A3AAB84EE2@microsoft.com...
> >> > Hi,
> >> >
> >> > If I write my application in XAML then is it a managed application?
> >> >
> >> > Also, does WinFX (.NET 3.0) directly understand XAML or does it convert
> >> > it
> >> > to something (say IL or something else) and then run this code at
> >> > runtime?
> >> >
> >> > Thanks,
> >> > - Manoj Agarwal
> >>
> >>
> >>
>
>
>

The underlying composition and rendering code for both WPF and the Vista
Destop Window Manager (DWM) lives in unmanaged code. Calls are made to this
code from WPF managed DLLs, which contain, well, the rest of WPF (all of the
APIs, layout, property system, app model, controls, etc, etc). While it's
true that WPF apps cannot themselves make calls to unmanaged code in partial
trust environments, WPF itself may do so (this is the same as it was with
..net 2.0), so no worries there.

A WPF app will be a managed app, and thus you can view it via ILDASM, etc.

-Adam Smith [MS]

"Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
news:8E5F7C4F-1C99-44C5-A7D0-72981636EE75@microsoft.com...
> The basic confusion in my mind is that how can WPF (which is a layer over
> .NET Framework 2.0) not use the grpahic sub-system used by .NET 2.0 but
> use
> some other sub-system?
>
> If a WPF app uses some other sub-system then will the app code be MSIL
> code
> and can I view it in ILDASM?
>
> Thanks for your patience with me
>
>
> "Jon Davis" wrote:
>
>> > Another thing which I wanted to ask (you have made a mention of it in
>> > your
>> > reply) is that I have read that WPF doesn't use the old User32\GDI+
>> > graphic
>> > sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.
>> >
>> > If this is so then does it mean that WPF does not use the .NET 2.0
>> > framework
>> > for display purpose but uses native code?
>>
>> Most of WPF is managed code. You will be doing all of your work in
>> managed
>> code. Direct3D is indeed utilized when a 3D card is available. D3D is
>> native. But that happens several layers below anything you touch.
>>
>> > If that is so then a WPF app is making calls to unmanaged code (i.e.
>> > the
>> > native code). I believe that to make calls to unmanaged code from
>> > managed
>> > code the app requires full-trust security. So do we require full-thrust
>> > to
>> > run a simple WPF app?
>>
>> Just as with WinForms, which at the underlying layers must make Win32
>> calls
>> behind the scenes, WPF hides the developer from those details as well.
>> What
>> exactly do you mean by "full trust security"? The application should
>> execute
>> from a trusted path as with WinForms, but you don't need to be
>> Administrator, for instance, to execute WPF applications.
>>
>> --
>> Jon Davis
>>
>> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
>> news:6FEAF906-A373-40D6-AEE0-399EAE8ED528@microsoft.com...
>> > Hi Jon,
>> >
>> > Thanks for your reply.
>> >
>> > Another thing which I wanted to ask (you have made a mention of it in
>> > your
>> > reply) is that I have read that WPF doesn't use the old User32\GDI+
>> > graphic
>> > sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.
>> >
>> > If this is so then does it mean that WPF does not use the .NET 2.0
>> > framework
>> > for display purpose but uses native code?
>> >
>> > If that is so then a WPF app is making calls to unmanaged code (i.e.
>> > the
>> > native code). I believe that to make calls to unmanaged code from
>> > managed
>> > code the app requires full-trust security. So do we require full-thrust
>> > to
>> > run a simple WPF app?
>> >
>> > Can you please help!
>> >
>> > Thanks,
>> > - Manoj
>> >
>> >
>> > "Jon Davis" wrote:
>> >
>> >> XAML is a design script, like HTML. It is not an application. XAML is
>> >> just
>> >> XML. You will still need to either write code-behind (yes, making it a
>> >> managed app) or, when the added technology has been made available in
>> >> a
>> >> XAML
>> >> revision, write JScript or C#-script (making it a scripted app like an
>> >> .hta
>> >> application).
>> >>
>> >> The XAML parser and much of the renderer is managed; some of the
>> >> rendering
>> >> is native, such as the 3D stuff.
>> >>
>> >> Jon
>> >>
>> >> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in
>> >> message
>> >> news:41BC7217-201F-4A59-A4E4-93A3AAB84EE2@microsoft.com...
>> >> > Hi,
>> >> >
>> >> > If I write my application in XAML then is it a managed application?
>> >> >
>> >> > Also, does WinFX (.NET 3.0) directly understand XAML or does it
>> >> > convert
>> >> > it
>> >> > to something (say IL or something else) and then run this code at
>> >> > runtime?
>> >> >
>> >> > Thanks,
>> >> > - Manoj Agarwal
>> >>
>> >>
>> >>
>>
>>
>>

Thanks for the informative reply Adam. The picture is much clearer to me,
thanks to you and Jon.

So probably the WPF managed DLLs will be making calls to the underlying
composition and rendering code (unmanaged code) using the .NET
Interoperability feature (COM and Dll Interoperability). Is that right?

Also, I tried to open the various dlls\exes installed by .NET Framework 3.0
and found that for WPF these are the only managed ones- PresentationUI.dll,
PresentationFontCache.exe, PresentationCFFRasterizer.dll. All others are
unmanaged (i.e. do not open in ILDasm). By any chance, do you have any idea
about what each one does?

Thanks,
- Manoj


"Adam Smith [MS]" wrote:

> The underlying composition and rendering code for both WPF and the Vista
> Destop Window Manager (DWM) lives in unmanaged code. Calls are made to this
> code from WPF managed DLLs, which contain, well, the rest of WPF (all of the
> APIs, layout, property system, app model, controls, etc, etc). While it's
> true that WPF apps cannot themselves make calls to unmanaged code in partial
> trust environments, WPF itself may do so (this is the same as it was with
> ..net 2.0), so no worries there.
>
> A WPF app will be a managed app, and thus you can view it via ILDASM, etc.
>
> -Adam Smith [MS]
>
> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
> news:8E5F7C4F-1C99-44C5-A7D0-72981636EE75@microsoft.com...
> > The basic confusion in my mind is that how can WPF (which is a layer over
> > .NET Framework 2.0) not use the grpahic sub-system used by .NET 2.0 but
> > use
> > some other sub-system?
> >
> > If a WPF app uses some other sub-system then will the app code be MSIL
> > code
> > and can I view it in ILDASM?
> >
> > Thanks for your patience with me
> >
> >
> > "Jon Davis" wrote:
> >
> >> > Another thing which I wanted to ask (you have made a mention of it in
> >> > your
> >> > reply) is that I have read that WPF doesn't use the old User32\GDI+
> >> > graphic
> >> > sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.
> >> >
> >> > If this is so then does it mean that WPF does not use the .NET 2.0
> >> > framework
> >> > for display purpose but uses native code?
> >>
> >> Most of WPF is managed code. You will be doing all of your work in
> >> managed
> >> code. Direct3D is indeed utilized when a 3D card is available. D3D is
> >> native. But that happens several layers below anything you touch.
> >>
> >> > If that is so then a WPF app is making calls to unmanaged code (i.e.
> >> > the
> >> > native code). I believe that to make calls to unmanaged code from
> >> > managed
> >> > code the app requires full-trust security. So do we require full-thrust
> >> > to
> >> > run a simple WPF app?
> >>
> >> Just as with WinForms, which at the underlying layers must make Win32
> >> calls
> >> behind the scenes, WPF hides the developer from those details as well.
> >> What
> >> exactly do you mean by "full trust security"? The application should
> >> execute
> >> from a trusted path as with WinForms, but you don't need to be
> >> Administrator, for instance, to execute WPF applications.
> >>
> >> --
> >> Jon Davis
> >>
> >> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
> >> news:6FEAF906-A373-40D6-AEE0-399EAE8ED528@microsoft.com...
> >> > Hi Jon,
> >> >
> >> > Thanks for your reply.
> >> >
> >> > Another thing which I wanted to ask (you have made a mention of it in
> >> > your
> >> > reply) is that I have read that WPF doesn't use the old User32\GDI+
> >> > graphic
> >> > sub-system which .NET 2.0 Winforms apps use. I think WPF use Direct3D.
> >> >
> >> > If this is so then does it mean that WPF does not use the .NET 2.0
> >> > framework
> >> > for display purpose but uses native code?
> >> >
> >> > If that is so then a WPF app is making calls to unmanaged code (i.e.
> >> > the
> >> > native code). I believe that to make calls to unmanaged code from
> >> > managed
> >> > code the app requires full-trust security. So do we require full-thrust
> >> > to
> >> > run a simple WPF app?
> >> >
> >> > Can you please help!
> >> >
> >> > Thanks,
> >> > - Manoj
> >> >
> >> >
> >> > "Jon Davis" wrote:
> >> >
> >> >> XAML is a design script, like HTML. It is not an application. XAML is
> >> >> just
> >> >> XML. You will still need to either write code-behind (yes, making it a
> >> >> managed app) or, when the added technology has been made available in
> >> >> a
> >> >> XAML
> >> >> revision, write JScript or C#-script (making it a scripted app like an
> >> >> .hta
> >> >> application).
> >> >>
> >> >> The XAML parser and much of the renderer is managed; some of the
> >> >> rendering
> >> >> is native, such as the 3D stuff.
> >> >>
> >> >> Jon
> >> >>
> >> >> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:41BC7217-201F-4A59-A4E4-93A3AAB84EE2@microsoft.com...
> >> >> > Hi,
> >> >> >
> >> >> > If I write my application in XAML then is it a managed application?
> >> >> >
> >> >> > Also, does WinFX (.NET 3.0) directly understand XAML or does it
> >> >> > convert
> >> >> > it
> >> >> > to something (say IL or something else) and then run this code at
> >> >> > runtime?
> >> >> >
> >> >> > Thanks,
> >> >> > - Manoj Agarwal
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

> Also, I tried to open the various dlls\exes installed by .NET Framework
> 3.0
> and found that for WPF these are the only managed ones-
> PresentationUI.dll,
> PresentationFontCache.exe, PresentationCFFRasterizer.dll. All others are
> unmanaged (i.e. do not open in ILDasm). By any chance, do you have any
> idea
> about what each one does?

Actually, if you're looking at .NET 3.0 July CTP, the path to all the
framework assemblies (including WPF) is here:

C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0

The key WPF files are:

PresentationCore.dll
PresentationFramework.dll
ReachFramework.dll (this is for XPS / printing, etc)
WindowsBase.dll

Jon


"Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
news:54FC3D57-9E27-4334-B08C-3E7737A45BDD@microsoft.com...
> Thanks for the informative reply Adam. The picture is much clearer to me,
> thanks to you and Jon.
>
> So probably the WPF managed DLLs will be making calls to the underlying
> composition and rendering code (unmanaged code) using the .NET
> Interoperability feature (COM and Dll Interoperability). Is that right?
>
> Also, I tried to open the various dlls\exes installed by .NET Framework
> 3.0
> and found that for WPF these are the only managed ones-
> PresentationUI.dll,
> PresentationFontCache.exe, PresentationCFFRasterizer.dll. All others are
> unmanaged (i.e. do not open in ILDasm). By any chance, do you have any
> idea
> about what each one does?
>
> Thanks,
> - Manoj
>
>
> "Adam Smith [MS]" wrote:
>
>> The underlying composition and rendering code for both WPF and the Vista
>> Destop Window Manager (DWM) lives in unmanaged code. Calls are made to
>> this
>> code from WPF managed DLLs, which contain, well, the rest of WPF (all of
>> the
>> APIs, layout, property system, app model, controls, etc, etc). While
>> it's
>> true that WPF apps cannot themselves make calls to unmanaged code in
>> partial
>> trust environments, WPF itself may do so (this is the same as it was with
>> ..net 2.0), so no worries there.
>>
>> A WPF app will be a managed app, and thus you can view it via ILDASM,
>> etc.
>>
>> -Adam Smith [MS]
>>
>> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in message
>> news:8E5F7C4F-1C99-44C5-A7D0-72981636EE75@microsoft.com...
>> > The basic confusion in my mind is that how can WPF (which is a layer
>> > over
>> > .NET Framework 2.0) not use the grpahic sub-system used by .NET 2.0 but
>> > use
>> > some other sub-system?
>> >
>> > If a WPF app uses some other sub-system then will the app code be MSIL
>> > code
>> > and can I view it in ILDASM?
>> >
>> > Thanks for your patience with me
>> >
>> >
>> > "Jon Davis" wrote:
>> >
>> >> > Another thing which I wanted to ask (you have made a mention of it
>> >> > in
>> >> > your
>> >> > reply) is that I have read that WPF doesn't use the old User32\GDI+
>> >> > graphic
>> >> > sub-system which .NET 2.0 Winforms apps use. I think WPF use
>> >> > Direct3D.
>> >> >
>> >> > If this is so then does it mean that WPF does not use the .NET 2.0
>> >> > framework
>> >> > for display purpose but uses native code?
>> >>
>> >> Most of WPF is managed code. You will be doing all of your work in
>> >> managed
>> >> code. Direct3D is indeed utilized when a 3D card is available. D3D is
>> >> native. But that happens several layers below anything you touch.
>> >>
>> >> > If that is so then a WPF app is making calls to unmanaged code (i.e.
>> >> > the
>> >> > native code). I believe that to make calls to unmanaged code from
>> >> > managed
>> >> > code the app requires full-trust security. So do we require
>> >> > full-thrust
>> >> > to
>> >> > run a simple WPF app?
>> >>
>> >> Just as with WinForms, which at the underlying layers must make Win32
>> >> calls
>> >> behind the scenes, WPF hides the developer from those details as well.
>> >> What
>> >> exactly do you mean by "full trust security"? The application should
>> >> execute
>> >> from a trusted path as with WinForms, but you don't need to be
>> >> Administrator, for instance, to execute WPF applications.
>> >>
>> >> --
>> >> Jon Davis
>> >>
>> >> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in
>> >> message
>> >> news:6FEAF906-A373-40D6-AEE0-399EAE8ED528@microsoft.com...
>> >> > Hi Jon,
>> >> >
>> >> > Thanks for your reply.
>> >> >
>> >> > Another thing which I wanted to ask (you have made a mention of it
>> >> > in
>> >> > your
>> >> > reply) is that I have read that WPF doesn't use the old User32\GDI+
>> >> > graphic
>> >> > sub-system which .NET 2.0 Winforms apps use. I think WPF use
>> >> > Direct3D.
>> >> >
>> >> > If this is so then does it mean that WPF does not use the .NET 2.0
>> >> > framework
>> >> > for display purpose but uses native code?
>> >> >
>> >> > If that is so then a WPF app is making calls to unmanaged code (i.e.
>> >> > the
>> >> > native code). I believe that to make calls to unmanaged code from
>> >> > managed
>> >> > code the app requires full-trust security. So do we require
>> >> > full-thrust
>> >> > to
>> >> > run a simple WPF app?
>> >> >
>> >> > Can you please help!
>> >> >
>> >> > Thanks,
>> >> > - Manoj
>> >> >
>> >> >
>> >> > "Jon Davis" wrote:
>> >> >
>> >> >> XAML is a design script, like HTML. It is not an application. XAML
>> >> >> is
>> >> >> just
>> >> >> XML. You will still need to either write code-behind (yes, making
>> >> >> it a
>> >> >> managed app) or, when the added technology has been made available
>> >> >> in
>> >> >> a
>> >> >> XAML
>> >> >> revision, write JScript or C#-script (making it a scripted app like
>> >> >> an
>> >> >> .hta
>> >> >> application).
>> >> >>
>> >> >> The XAML parser and much of the renderer is managed; some of the
>> >> >> rendering
>> >> >> is native, such as the 3D stuff.
>> >> >>
>> >> >> Jon
>> >> >>
>> >> >> "Manoj Agarwal" <ManojAgarwal@discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:41BC7217-201F-4A59-A4E4-93A3AAB84EE2@microsoft.com...
>> >> >> > Hi,
>> >> >> >
>> >> >> > If I write my application in XAML then is it a managed
>> >> >> > application?
>> >> >> >
>> >> >> > Also, does WinFX (.NET 3.0) directly understand XAML or does it
>> >> >> > convert
>> >> >> > it
>> >> >> > to something (say IL or something else) and then run this code at
>> >> >> > runtime?
>> >> >> >
>> >> >> > Thanks,
>> >> >> > - Manoj Agarwal
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>