Detecting Windows Store App Configuration Mode (Debug vs Release) in JavaScript

Windows Library for JavaScript (WinJS) is an amazing library. This along with the projected winmd libraries, developers have almost everything they would ever need to develop an average Windows Store App. One thing that is missing that I recently came across is the ability to detect which configuration mode the App is currently running in (Debug or Release).

I needed to enhance a few debugging capabilities if the App is in Debug mode. To detect the current mode in JavaScript I used the beauty of language projection. The following sections will examine this in more detail.

C#

First, I used a C# Windows Runtime Component to enable the capability of using the implementations in JavaScript. I then created what I called a ConfigurationManager. Below is the code:

namespace AppName.Utilities
{
    public sealed class ConfigurationManager
    {
        public static bool IsDebug {
            get {
#if DEBUG
                return true;
#else
                return false;
#endif
            }
        }
    }
}

The simplicity of this class cannot be overstated. It has a single static property called “IsDebug”. The key part of the implementation is the use of compiler directives #if and #else.

#if the DEBUG constant is defined, then the App is in Debug mode. #else (Otherwise), the App is in Release mode.

JS

After adding a reference to this component and rebuilding, I can now detect the current configuration mode in the JavaScript App:

var isDebug = AppName.Utilities.ConfigurationManager.IsDebug;
if(isDebug) {
    //debug-specific code.
} else {
    //release-specific code.
}

Please note that this depends on the compiler. There is one potential issue with this: the perceived configuration mode of the App is solely dependent on the configuration mode of the projected component.

Appendix A

There is a “Debug” object in JavaScript. This object does not contain abilities to determine the configuration mode but merely whether a debugger is attached (and various other debugger type mechanisms). This object also exists in both Debug and Release modes. The solution provided in this article shows one of the easiest ways of accomplishing the feat of determining whether the configuration mode is Debug or Release.

Rudimentary Way to Make a WinRT Component Object Bindable in WinJS

When projecting a WinRT Component object to WinJS, I kept running into an exception saying that the WinRT object could not be extended. This post will briefly describe how I got around this issue.

There are a few things known that helped come to this solution:

  • I didn’t need to worry about differences between one-way/two-way binding. All I had to do was present the object onto the screen.
  • Average JavaScript objects are bindable with WinJS
  • JavaScript objects are essentially associative arrays
  • If a member does not exist when referenced in an assignment operation, it is first created, then assigned.
  • I can essentially “clone” objects by iteratively copying members using array syntax.

This last item is exactly what I did! Let me elaborate:

It is simple. At this point, we can’t bind to WinRT Objects therefore we need to make them bindable ourselves. The code snippet below shows this.

function _makeBindable( obj ) {
    var o = new Object();
    for ( m in obj ) {
        o[m] = obj[m];
    }
    return o;
}

var winrtObj = Projection.getWinRTObject();

//cannot bind winrtObj

var bindableWinRTObj = _makeBindable( winrtObj );

//use bindableWinRTObj for data-binding scenarios

Lets look at _makeBindable in a little more detail.

First, the function takes an object as a parameter. This object is the WinRT object that is causing issues. Then, a local variable is created assigned to a new Object.

The next part is very important – iterating over the members of the WinRT object. Using a for-in loop, cloning an object is quite easy. In this case, “m” represents the current member name as a string. Since JavaScript objects are essentially associative arrays, “m” can be used to access the current WinRT object’s member using array syntax. The member name is also used to assign to the local variable that was previously created. This effectively copied the current member from the WinRT object to the local variable.

Once all of the members are copied, the local variable is returned for use in data-binding scenarios.

Dynamic Objects Using WinJS & XML

Welcome to the latest Creationism article. The Creationism series focuses on various constructs using common Microsoft technologies. This entry will show how to create a JavaScript object based on an xml file. The article will assume basic JavaScript, WinJS and XML experience. This post originated from my blog on Code Project: “Creationism: Dynamic Objects Using WinJS & XML“.

The Problem

I am writing an app for Windows 8 and need a maintainable set of values I can use in JavaScript. My first attempt included creating a Constants object that contained the values I needed. This soon became unmanageable as the number of constants increased. To fix this, something like an ASP.Net web.config file would be great. The problem is I do not want the restriction of accessing it through a sort of “AppSettings” property as with ASP.Net websites. My preference would be a JavaScript object that contains the properties I need but from a configuration file. How would I do this?

The Solution

What would solve my problem is a JavaScript object created at runtime that includes properties and values based on an XML file. A few things known about JavaScript make this solution viable:

  1. JavaScript is a highly dynamic language. Considering this fact, creating an object during runtime should be like Eddie Van Halen playing a guitar.
  2. Object properties can be accessed and manipulated using normal array syntax.
  3. Server data is accessible from JavaScript. AJAX is the acronym.
  4. Since an XML file is obtained, it can be parsed no differently than an average HTML document.

Combining the implementation of these four facts will enable me to create an object at runtime using the data of an XML file. The next section will explain how this is done.

The Implementation

There are three basic steps to implementing this. The mechanisms accessible from WinJS will help tremendously. First, the XML file needs to be obtained. This can be done using the WinJS.xhr function. More information on this function can be found on MSDN: “WinJS.xhr function (Windows)”. The next step is to parse the XML file and then to create the Constants object based on the data retrieved from the file. These steps will be explained in more detail in the following sections.

The Configuration File

To consume the file, the file will need to be created. Below is the sample content in the file:

<?xml version="1.0" encoding="utf-8" ?>
<Configuration>
  <Constant1>
    <add name="String" value="Value 1" />
    <add name="Integer" value="1" />
  </Constant1>
  <Constant2>
    <Boolean>
      <add name="IsTrue" value="true" />
      <add name="IsFalse" value="false" />
    </Boolean>
  </Constant2>
  <Constant3>
    <add name="SubConstant" value="SubValue" />
    <NextSubConstant>
      <add name="NextSub" value="NextSubValue" />
    </NextSubConstant>
  </Constant3>
</Configuration>

As can be seen, this is nothing more than an average XML file. There are various nested nodes and attributes to show some of the possible node structures supported by this solution. For this article, the name of the file is “config.xml” and the root node is “Configuration”.

The Data

The WinJS.xhr function is used to get the XML file. This function takes an object used to configure the request and returns a Promise. This is shown below:

WinJS.xhr({
    url: "config.xml",
    headers: {
        "If-Modified-Since": "Wed, 2 Feb 2000 11:11:11 GMT"
    },
    responseType: "document"
}).done(function(result) {
    if (result.status === 200) {
        var data = result.responseXML;
        var root = data.querySelector("Configuration");

        WinJS.Namespace.define("ST.Constants");
        iterate(root, ST.Constants);
    } else {
        /* ... Handle missing document ... */
    }
});

Overview

Above shows what could be thought of as jQuery AJAX on steroids. The xhr function is called taking an object used to configure the XMLHttpRequest. “url” is the only required property. Other optional properties can be used to further configure the XMLHttpRequest. This is much like jQuery’s ajax method but, in this case, a Promise object is returned. The “done” method of the returned Promise is used to process the returned XML document.

Configuring the XMLHttpRequest

WinJS.xhr({
    url: "config.xml",
    headers: {
        "If-Modified-Since": "Wed, 2 Feb 2000 11:11:11 GMT"
    },
    responseType: "document"
})

The parameter passed to the xhr function is an object. This object is used to configure the XMLHttpRequest as mentioned previously. Here the “url” is set to the path to the XML file. Then, the “headers” property is used which includes the “If-Modified-Since” date. This ensures the XML file is obtained. The last property is “responseType” which is used to make sure the result of this call is a document able to be parsed by JavaScript.

Processing the XML File

.done(function(result) {
    if (result.status === 200) {
        var data = result.responseXML;
        var root = data.querySelector("Configuration");

        WinJS.Namespace.define("ST.Constants");
        iterate(root, ST.Constants);
    } else {
        /* ... Handle missing document ... */
    }
});

The next step is to process the returned XML file. The xhr function returns a Promise object. This object contains a “done” method that can be used for processing the results of the xhr function call. As with average use of XMLHttpRequests, the first step is to make sure it succeeded. Using the result passed into the done handler, the status of the request can be determined. This result object is the XMLHttpRequest. It contains useful properties among these being “status” and “responseXML”. A successful status is 200. If the status is 200, the function proceeds with processing the results by first getting the responeXML from the result object. Since the responseType was set to “document”, the content of responseXML is the XML document that can be parsed by JavaScript. The iteration of this document will be described in more detail below but there are two more steps to do first. The iteration method takes two parameters. The first parameter is the node to process. To begin, the root node needs to be processed so this is what is retrieved. The second parameter is the object to process with the node. The object is meant to be static so the WinJS.Namespace.define method is used to create this. The two parameters are passed to the iterate method. The next section provides more detail.

The Iteration

There is hair, teeth, flesh and bones but the iteration method is the meat. Within this method is the traversal of the XML file along with the additions to the Constants object. Below is the implementation:

function iterate(node, ns) {
   if (node && node.childNodes) {
      if (node.childNodes.length > 0) {
         var nodes = node.childNodes;
         var len = nodes.length;
         for (var i = 0; i < len; i++) {
            var sub = nodes[i];
            if (sub.nodeType === sub.ELEMENT_NODE) {
               var name = sub.nodeName;
               if (sub.childNodes.length > 0) {
                  ns[name] = {};
                  iterate(sub, ns[name]);
               } else {
                  var attName = sub.getAttribute("name");
                  var attValue = sub.getAttribute("value");
                  //Key/Value Attribute
                  if (attName && attValue) {
                     ns[attName] = attValue;
                  //Node Name/Value
                  } else if (attValue && node.nodeName && !attName) {
                     ns[name] = attValue;
                  } else {
                     /* ... Handle Data Not Available ... */
                  }
               }
            }
         }
      } else if (node) {
         var name = node.nodeName;
         var attName = node.getAttribute("name");
         var attValue = node.getAttribute("value");
         //Key/Value Attribute
         if (attName && attValue) {
            ns[attName] = attValue;
            //Node Name/Value
         } else if (attValue && node.nodeName && !attName) {
            ns[name] = attValue;
            //Log Warning
         } else {
            /* ... Handle Data Not Available ... */
         }
      }
   }
}

Above is the implementation of the iteration method. This method has various validation checks for the current node, child nodes, and attributes. There is also room for handling missing data.

Handling No Children

The method begins by checking whether the given node and its children exist. If any children exist, it continues processing the child nodes. If there are no children, the method checks to make sure there is a node and upon success attempts to get the name and value attributes. This is shown below:

else if (node) {
   var name = node.nodeName;
   var attName = node.getAttribute("name");
   var attValue = node.getAttribute("value");

   //Key/Value Attribute
   if (attName && attValue) {
      ns[attName] = attValue;

      //Node Name/Value
   } else if (attValue && node.nodeName && !attName) {
      ns[name] = attValue;

      //Log Warning
   } else {
      /* ... Handle Data Not Available ... */
   }
}

There are three possible paths than can be taken here:

  1. If both the name and value attributes exist, the Constants object is updated. A new property is added to the object. This part takes advantage of the fact JavaScript object properties can be accessed and manipulated by using normal array syntax. The new property is created with the value of the “name” attribute and is assigned the value of the “value” attribute.
  2. If the value attribute and node name exist but not the name attribute, the Constants object is updated using the node name. The name of the new property is the name of the node. The value of this new property is the value of the value attribute.
  3. If neither of the above two cases exist, there is no data available as this solution is currently implemented. This is a good place to handle such a case by either logging the occurrence, adding default data, or any other way that is necessary.

Handling with Children

If the given node exists with children, the iterate method proceeds by processing the child nodes. The snippet below shows this:

if (node.childNodes.length > 0) {
   var nodes = node.childNodes;
   var len = nodes.length;
   for (var i = 0; i  0) {

            ns[name] = {};
            iterate(sub, ns[name]);
         } else {

            var attName = sub.getAttribute("name");
            var attValue = sub.getAttribute("value");

            //Key/Value Attribute
            if (attName && attValue) {
               ns[attName] = attValue;

               //Node Name/Value
            } else if (attValue && node.nodeName && !attName) {
               ns[name] = attValue;

            } else {
               /* ... Handle Data Not Available ... */
            }
         }
      }
   }
}

The node is checked to make sure it has child nodes. If it does, each child node is processed in a simple for loop. The current child node is stored and then a check is done to be sure it is an element node. If so, the method checks this node’s children. If they exist, the name of the sub node is used to create a new property of the given Constants object. Then the iterate method is called again this time passing in the current child node and the new property of the Constants object. This provides the support needed to add nested nodes in the XML file.

If the current child node does not have any children, it is processed in the same way as what was described in the previous section “Handling No Children”.

The Outcome

As you are probably aware by now, this solution creates an object at runtime. Using the Watch window while debugging the structure of the object can be seen:

This shows that the structure of the Constants object mirrors the structure of the XML file.

Originally Perceived Enhancements

Using this solution offers numerous benefits. It is flexible, scalable, and performs well. It provides practically infinite levels of nesting in the xml file (barring any call stack limitations when the prototype chain is created). There is also no performance hit from going across a network since the configuration file is local to the app. Among these strengths, there are still improvements that can be made.

Attribute Values

So far, the values of the constants are set as the attribute values in the XML file. Node values could be used as well.

Data Types

Not every value is appropriate as a string. Additional logic could be added to the iteration to have values of appropriate data types (e.g. If the value is meant to be an Integer, make it an Integer; if the value is meant to be a Date, make it a Date).

Caching

This creates an object at runtime. Don’t create the same object every time the app is started. When the object is first created, store it. Then, retrieve it from storage when the app loads again. Only create this object when a change has been made.

Conclusion

This article presented a way to create objects that are easily configurable by updating values in an XML file. As with most things, there are pros and cons to this solution but it does the job, and does the job well. Needless to say, the band is happy and the object has been brought to life.

Thank you for reading and please see my other Creationism articles.