Manually Compile your XAML into BAML

re: Manually Compile your XAML into BAML

w0lfshad3 — Tue, 30 Oct 2007 04:40:16 GMT

The first step is to compile the XAML files into BAML using the xamlc.exe compiler.For example, if your project includes a file name Window1.xaml, the compiler will create a

temporary file named Window1.baml and place it in the obj\Debug subfolder (in your project

folder). At the same time, a partial class is created for your window, using the language of

your choice. For example, if you’re using C#, the xamlc.exe compiler will create a file named

Window1.g.cs in the obj\Debug folder. The g stands for generated.

The partial class includes three things:

• Fields for all the controls in your window.

• Code that loads the BAML from the assembly, thereby creating the tree of objects. This

happens when the constructor calls InitializeComponent().

• Code that assigns the appropriate control object to each field and connects all the

event handlers. This happens in a method named Connect(), which the BAML parser

calls every time it finds a named object.

The partial class does not include code to instantiate and initialize your controls because

that task is performed by the WPF engine when the BAML is processed by the

Application.LoadComponent() method.

■Note As part of the XAML compilation process, the XAML compiler needs to create a partial class. This is

only possible if the language you’re using supports the .NET Code DOM model. C# and VB support Code

DOM, but if you’re using a third-party language you’ll need to make sure this support exists before you can

create compiled XAML applications.

...so read the filename.g.cs, it's how BAML is loaded.

re: Manually Compile your XAML into BAML

Stanimir Stoyanov — Thu, 01 Jul 2004 14:06:00 GMT

Can someone tell me a good way to read BAML files? I tried the System.Windows.Serialization.BamlReader class, but it seemed not to work correctly - it gives some UIContext exception.

Thank you in advance,
Stan

re: Manually Compile your XAML into BAML

Henry Erich III — Fri, 09 Apr 2004 15:02:00 GMT

Ok, last night I put on the SDK (finally) and compiled a simple XAML with xamlc.exe. Awesome! I cant wait to do more!

Today you can't compile xaml on the fly.

TrackBack — Thu, 08 Apr 2004 23:37:00 GMT

re: Manually Compile your XAML into BAML

Rob Relyea [msft] — Thu, 08 Apr 2004 23:36:00 GMT

We want to get to a model that will allow building in LH without the sdk having to be installed.

Here is what works now:
1) Msbuild.exe is shipping with LH, becuase the .net redist is part of LH.

Here are problems now:
1) set lapi=c:\windows\microsoft.net\windows\v6.0.4030
2) resgen.exe and al.exe need to be installed currently...i forget the path we are looking for it (perhaps %sdktoolpath% ????)

re: Manually Compile your XAML into BAML

Jason — Thu, 08 Apr 2004 13:20:00 GMT

To use precompiled XAML, yes, however there is a runtime environment built into Longhorn that runs non-compiled XAML.

re: Manually Compile your XAML into BAML

Henry Erich III — Thu, 08 Apr 2004 03:42:00 GMT

So, the only way to properly compile is to use xamlc and not ac. Which also would mean I have to get the SDK and couldnt complile with just a LH install?

re: Manually Compile your XAML into BAML

Rob Relyea [MSFT] — Tue, 18 Nov 2003 10:05:00 GMT

Don't use AC.exe! That is obsolete.
As Chris has written, we did a major rearchitecture, AC.exe is part of the old architecture.

What you should use is XamlC.exe (which is currently installed with the LHSDK). When you run the Longhorn SDK Command Prompt - it will be in the path.