When your application uses Binary XAML (BAML) resources that are created by the XAML Resource Packager (XRPack), warnings and error messages are less informative than if BAML was not used. For example, with BAML on, the error message may be:

407416 PID:10b03f2 TID:1600066 PC=402938ce(xamlruntimecore.dll+0x000d38ce) RA=402de947(xamlruntimecore.dll+0x0011e947) SP=0002f80c, BVA=000db004

With BAML off, the error message is:

63262774 PID:1750532 TID:1760412 [XR] XRApplication::CheckParserError - PARSE ERROR: Code: 0x80470066  Line: 2    Character:4614   Message: Unknown element: Menu.

When you troubleshoot XAML issues in your application, we recommend that you do the following:

• Disable BAML. You can disable BAML by using the XRPack build parameter /BamlOff.
• Use line numbers in the XAML files so that you can more easily see where the problems occur. You can enable line numbers by using the XRPack build parameter /IndentFiltered. These line numbers appear in the XAML files in the output directory, not the files in the project.
• Do a clean build of the Silverlight application after changing these settings so that the new settings take effect. If you modify only the XAML files and then you build the Silverlight project without cleaning it first, the resource files will not get rebuilt. You can perform a clean build every time by using the XRPack build parameter /C.

Caution:
Because disabling BAML can reduce graphics performance, you typically disable it only when troubleshooting.

By using these recommended XRPack settings, you can troubleshoot problems more easily and generate the most useful warning and error information. To add these XRPack settings, use the procedure below. Note that the location of the file that you modify in Visual Studio depends on whether your application is a subproject of an OS design in Platform Builder or you are developing your application in Visual Studio without using Platform Builder. Choose the procedure that is appropriate for your project.