MSDN Magazine - February 2009 - (Page 68)

in a moment—you can choose the “M” image packaging format with the /p:image command line switch to m.exe: C:\>m.exe /p:image wixbits.m Microsoft (R) "Codename M" Compiler version 1.0.0925.0 Copyright (C) Microsoft Corporation. All rights reserved. C:\>dir wixbits.mx 11/22/2008 04:44 PM 9,073 wixbits.mx The wixbits.mx file is an “M” image file, which contains the generated SQL as well as a manifest and other metadata. Since the file is in OPC (Open Packaging Conventions) format, you can stick a .zip file extension on it and open it just like any other .zip file. Figure 4 Compiling with Imported Types and Extents C:\>m.exe /p:image /t:Repository WixbitsTypes.m Microsoft (R) "Codename M" Compiler version 1.0.0925.0 Copyright (C) Microsoft Corporation. All rights reserved. C:\>dir WixbitsTypes.mx 11/22/2008 05:48 PM More importantly, however, you can use a .mx file for references and for deployment. When you build a .NET assembly, you can reference that assembly as part of your build process to pull public types and static instances into your .NET-based programs. If you’re using the C# or Visual Basic compilers from the command line, you can reference existing .NET assemblies with the /r (reference) switch. Likewise, if you’re compiling your “M” programs, you can employ the /r switch on the “M” compiler to pull in other types from “M” images. For that to work, you must first export your types or extents from the module you’re referencing: // WixbitsTypes.m module WixBits { export Product, Package; // export types export Products, Packages; // export extents type Product { }; type Package { }; Products : Product*; Packages : Package* where item.Product in Products; } 28,332 WixbitsTypes.mx You can then import types and extents that have been exported: // WixbitsValues.m module WixBits { import WixBits; // bring in exported types and extents } C:\>m.exe /p:image /t:Repository /r:WixbitsTypes.mx WixbitsValues.m Microsoft (R) "Codename M" Compiler version 1.0.0925.0 Copyright (C) Microsoft Corporation. All rights reserved. C:\>dir WixbitsValues.mx 11/22/2008 05:50 PM 5,606 WixbitsValues.mx Once you’ve built an “M” image file with exports, you can reference that when compiling “M” programs with imports (for more information, see Figure 4). In addition to packaging up types and extents for reference in other “M” programs, an “M” image file can be deployed to a SQL Server database instance using the “M” loader utility, mx.exe, in the following manner: C:\>mx.exe /db:Repository /i:WixbitsTypes.mx /i:WixbitsValues.mx Microsoft (R) "Codename M" Command-line Utility version 1.0.0925.0 Copyright (C) Microsoft Corporation. All rights reserved. Figure 5 The “M” Project Template in Visual Studio 2008 Here I am using the /db switch to specify which database to connect to, assuming the local host as the database server and installing the two image files. I load the tables into SQL and populate them with my values, which means I can use the data access technology of my choice to pull them back out again (or update them or delete them or insert new ones). In this case, I’m using the sqlcmd command-line tool: C:\>sqlcmd -d Repository 1> select Name from WixBitx.Products 2> go Name SuperNotepad (1 rows affected) While Intellipad supports “M” language services out of the box, including generating SQL, there is no supported mechanism for building the image or referencing other images. However, Visual Studio supports these features. Visual Studio Integration Figure 6 An “M” Project with Source Code and .mx File Reference 68 msdn magazine The “Oslo” SDK ships with built-in support for Visual Studio 2008 SP1. After you install the SDK, you will have the “M” Project template installed, as shown in Figure 5. By default, you’ll get a Model1.m file added to your project. This “Oslo” Basics

Table of Contents Feed for the Digital Edition of MSDN Magazine - February 2009

MSDN Magazine - February 2009 Contents Toolbox CLR Inside Out Data Points Cutting Edge Patterns In Practice Best Practices .Net Interop "Oslo" Basics Patterns Silverlight Under The Table Foundations Windows With C++ .NET Matters Going Places { End Bracket }

MSDN Magazine - February 2009

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.