MICROSOFT_PRESS_EBOOK_PROGRAMMING_WINDOWS_8_APPS_WITH_HTML_CSS_AND_JAVASCRIPT_PDF

public sealed class Tests
{
public static string TestMethod(Boolean throwAnException)
{
if (throwAnException)
{
throw new System.Exception("Tests.TestMethod was asked to throw an exception.");
}
}
return "Tests.TestMethod succeeded";
}
public int TestProperty { get; set; }
If you build the solution at this point (Build > Build Solution), you’ll see that the result of the
PixelCruncherCS project is a file called PixelCruncher.winmd. The .winmd extension stands for Windows
Metadata: a WinRT Component written in C# is a .NET assembly that includes extra metadata referred
to as the component’s Application Binary Interface or ABI. This is what tells Windows about everything
the component makes available to other languages (those public classes), and it’s also what provides
IntelliSense for that component in Visual Studio and Blend.
In the app you must add a reference to the component so that it becomes available in the JavaScript
namespace, just like the WinRT APIs. To do this, right-click References within the JavaScript app project
and select Add Reference. In the dialog that appears, select Solution on the side and then check the box
for the WinRT component project as shown in Figure 16-2.
FIGURE 16-2 Adding a reference to a WinRT component within the same solution as the app.
When writing code that refers to the component, you always start with the namespace,
PixelCruncherCS in our case. As soon as you enter that name and a dot, IntelliSense will appear for
available classes in that namespace:
722