This article discusses the just released Compact13Tools Version 5.0 software architecture for Compact13Tools. This version has the full source for the Managed Code which it builds via a batch file.The software is structured as two layers. (Read on for more.) The next blog will introduce CEToolbox which directly builds to Managed Code tools as OS Source Subprojects; a topic covered in the previous three blogs. This article is essentially a slides presentation with some *comments.

News

Microsoft has announced a preview edition of ISS, Intelligent System Services. This is their Enterprise version of the "Internet of Things", aka Azure Internet of Things.
Not to be confused with Microsoft's "Internet of My Things" which is about BYOD, bring your own devices  (big and small) and connect to the enterprise and the cloud, seamlessly, whether at work, home or roaming.

ISS Links (Including some discussions):

• http://www.microsoft.com/windowsembedded/en-us/intelligent-systems-service.aspx
• http://download.microsoft.com/download/E/1/F/E1FFDADF-C0FF-4E72-A834-B173A079F393/Microsoft%20Azure%20Intelligent%20Systems%20Service_Datasheet.pdf
• https://connect.microsoft.com/site1132/
• http://www.zdnet.com/microsoft-delivers-preview-of-new-azure-cloud-service-for-internet-of-things-7000028469/?s_cid=e539&ttag=e539&ftag=TRE17cfd61
• http://mobile.eweek.com/cloud/microsoft-launches-azure-cloud-service-for-internet-of-things.html

Compact 7 Documentation

It has been noted that the Windows Compositor that was available in Compact 7 has been removed from Compact 2013. The current documentation does not indicate this and is to be updated. This is the alpha blending, as in Windows 7 that allowed for some measure of transparency when windows overlapped. Possibly removed because it does not fit with the Windows 8 UI philosophy. Thanks to Embedded MVP,  Vinoth for uncovering this.

• Compositor: http://msdn.microsoft.com/en-us/library/jj919252.aspx
• Vinoth's Blog: http://vinoth-vinothblog.blogspot.com.au/

Compact13Tools Update

Now available as Version 5.0 on Codeplex  (Click here)

A new release, Version 5.0, has been released on Codeplex. The native code for Compact13Tools has undergone some code review thanks to Embedded MVP, MIchel Verhagen from GuruCE in New Zealand. Registry entries have been streamlined and a conflict in the registry between Compact13ForeverShell and Compact13Minshell has been fixed. Michel's debugging infrastructure has been adopted in the native code in the tools. You add two files to a native code project and a rich debugging mechanism based upon Debug Zones is implemented. See the link below for details.

This version of the tools provides full source code for the Managed Code (C#) tool's projects. When their corresponding OS Subprojects are built as part of the OS build, a batch file is called by Prelink.bat to build them and place them in a common directory (\/bin). Postlink.bat then copies the .exe to the release directory for inclusion in the OS as flagged by its BIB file. The previous versions of the tools, provided the \bin directory with prebuilt .exes, except for the Prototypeapp which actually used this build mechanism.

Note that the next version of the tools will be renamed CEToolbox and will build the managed code directly as managed code sources OS Subproject as discussed in previous blogs.  See the next blog which is about CEToolbox (coming).

Links:

• Compact13Tools:
  • https://Compact13Tools.codeplex.com
• GuruCE:
  • http://guruce.com
• "A Template for Debug Messages"
  • http://guruce.com/blogpost/atemplatefordebugmessages

Note: Can click on slides to enlarge..

Compact13Tools Architecture

ie. How it all builds

Compact13Tools consists of two software layers:

• The OS Subprojects
• The SDK C# Managed Code projects

The OS Subprojects are built with the OS, which build the SDK projects in Prelink.bat.

Note, the SDK project can be loaded as a separate Visual Studio instance and developed/debugged over CoreCon.
There is an overall solution file for them.

There are four native code OS Subprojects.

The are also content OS Subprojects that deliver content only to the OS image.
These projects can be generated using CEComponentWiz. (Click here)

Each Managed Code tools has a corresponding OS Content Subproject.

The directory structure of Compact13Tools

The C# Build Mechanism for each Managed Code Tool:

• Is an OS Sources Subproject (Top layer)
• NoTarget Set
  • Content only to be included in OS
  • No sources to build
• Prelink.Bat
  • Calls a batch file that sets up the SDK/C# build environment
    and builds the Managed Code project (Bottom layer)
    • Output for project is set to \WINCE800\3rdParty\Compact13Tools\bin
• Postlink.bat
  • Copies the .exe from \bin (and any resources in the  <OS Subproject>\Resources folder)
    to the Release directory
• BIB file then includes these items in the image.

The binding force between the OS Content Subprojects and the C# ones is BuildVSProject.Bat
that is called by Prelink.bat.This batch file is located \Misc

• Note that need to set BUILDVSPROJECT to 1 in the OS Environment properties.
  • Can disable these rebuilds, when done once if you prefer.
• Also AppName is set in Prelink.bat.

Enjoy

A simpler mechanism would be to implement the C# projects as Managed Code Sources OS Subprojects.
This is covered in the next blog:

Next:

• Introducing CECompactTools, morphed from Compact13Tools.

Managed Code as part of the OS Build

Once a Managed Code app is debugged it should be possible to directly build it as part of the OS build, exactly like Native Code Subprojects. The following is a trilogy on this topic including a wizard for creating a C# OS Subproject that builds with the OS on embedded101.com:

Part 1     

• Managed Code Development as part of the OS.

Part 2     

• WECSharpWiz for generating Managed Code OS Subprojects

Part 3     

• Debugging  Managed Code as OS Subprojects