• DaveDev

    This package was deployed for development or authoring mode error in Windows App Cert Kit


    Via Davedev.net

    If you are getting this error message when running the Windows App Certification Kit don’t panic!

    This package was deployed for development or authoring mode. Uninstall the package and re-install it normally.

    WACK Error


    This means you have a Windows Store app written in JavaScript that you deployed locally through Visual Studio instead of as a package.  In order to properly test a JavaScript Windows Store app the  Byte code generation should be able to complete successfully.  In order to enable this the package must be installed normally as follows:

    In Visual Studio 2012 select the Project,  right click, open the Store Menu and choose Create App Packages.  If you are using the Express version of Visual Studio 2012 you will have a Store Menu on your Visual Studio Menu already.


    Create Store Package

    Select the option to not upload to the Windows Store.  This will create a local package you can use for testing on your own machine or give to other developers to test.

    Local Package


    Choose all of the defaults and then open the folder to the generated binaries with the link it provides.


    Install Package

    You will want to run the provided PowerShell script (.ps1 extension) and follow the prompts.  This will install the package locally into your Windows Store App location and apply the generated developer certificate.


    Successful Bytecode generation!

    Congrats!  You can now run the WACK Tool successfully as well as other developers who may want to test your app for you.

  • DaveDev

    Build a Hybrid App for Windows Phone 8 using appMobi


    Via Davedev.net


    appmobi_logo_highres HTML5

    If you’re a web developer focused on HTML5 like me then chances are you’ve looked into how to port your web apps to one of the App Marketplaces out there.  I recently sat down with appMobi’s Developer Evangelist, Andrew Smith, to chat about how Web Developers can create Hybrid Apps which run on iOS, Android and Windows.  Due to the popularity of that interview I’ve asked Andrew to guest post here on how you can get started!

    Via Andrew…

    Smartphones running mobile apps are spreading quickly, just like Websites did in the 90’s. However, in order to have your software in the mobile app stores developers need to create native apps written in the programming language of the particular operating system. Rather than writing the same application over and over so your app can run on all smartphones, wouldn’t it be great if your current Web developers could build your application once but allow you to deploy it to a variety of devices? Perhaps appMobi is the answer.

    What is a Hybrid Mobile App?

    The key to creating a mobile app that is written once but runs anywhere is the concept of the hybrid mobile app. These apps are called “hybrid” apps because they are native apps that are coded using the exact same technologies that power the World Wide Web.

    Native applications are written specifically for a particular operating system of the device it is meant to run on. That would be xCode/Objective C for iOS, Eclipse/Java for Android, and Visual C# or Visual Basic for Windows Phone 8. There is no native universal programming language for all device platforms.

    appmobi-xdkOn the other hand, mobile Web apps are server-side apps that run within a smartphone’s Web browser. They use Web technologies such as HTML5, JavaScript, and CSS3. However, these applications are not available from the smartphones’ app stores since they are downloaded from the Web.



    Hybrid apps are a marriage of these two technologies. Like a native app a hybrid app runs natively on the device and are distributed through the smartphones’ distinctive app stores. However, these apps are coded using Web technologies rendered locally on the device so it does not require an Internet connection. Furthermore a Web to native abstraction layer gives the hybrid app access to device capabilities that are not accessible to mobile Web applications such as the accelerometer, contacts database, and camera.

    Web Developers Can Use appMobi to Create Hybrid Apps

    Using appMobi, you can create apps using Web technologies that you are already familiar with. The appMobi XDK tool can be used as a simulator to test how your app will look on a variety of devices and interact with the device’s native features such as the camera and accelerometer using the appMobi JavaScript API.



    Then using the appMobi XDK you can see how your application would look on a variety of devices. Once you like the app on the emulator, load it on an actual smartphone using the appMobi “test anywhere” feature. Use this tool to create a project “bundle”, a folder including all the HTML, JavaScript, CSS, image, video, audio, and other supporting Web technology files that will be built into the native apps.

    Create Your Project Bundle

    Building a hybrid native app is just like building a mobile Web app, except that the code is built into a binary at the end for submission to the appropriate application stores. Using the appMobi appHub build system, your project bundle – all the files used to create the application including HTML, JavaScript, images, videos, CSS – is automatically compiled into a binary for you. No need to buy a Mac and learn XCode to create iOS apps. Don’t bother installing Eclipse and learning Java programming techniques to create an Android app. The appMobi appHub build system does all that for you.



    With the advent of Windows Phone 8, the appMobi appHub will soon include the capability of creating a native application for a Windows smartphone as well. Meanwhile, you can follow these easy steps to create your very own Windows Phone 8 application using the free tools Microsoft has provided.


    Decide what you want your app to do, and build it using the tools you are already familiar with. Consider using the appMobi XDK to test any calls to the appMobi JavaScript Bridge API, or see how your bundle will appear on a variety of devices.



    Build For Windows Phone 8

    Once you have an app project bundle finished, it is time to build it for Windows Phone 8. To build an appMobi application as a hybrid Windows Phone 8 app, you’ll need to install Visual Studio Express 2012 for Windows Phone on a Windows 8 PRO computer. The Windows 8 PRO operating system is key since The Windows Phone 8 emulator relies on Windows 8 Professional, so be sure you have the appropriate operating system before getting started.






    First create a Windows Phone 8 project in Visual Studio. Start Visual Studio for Windows Phone and select New and then Project. On the New Project setup screen, create a Windows Phone App using Visual C#. Supply a name for the project and select OK. This will create your new project.



    Select the Windows Phone 8 operating system. Click OK to continue.



    Once you have a project prepared, you will want to install one of appMobi’s Windows Phone 8 templates from NuGet to transform your empty new project into an appMobi application project. To install one of the appMobi templates visit:


    Consider trying one of the specialized templates another time, but just for the purposes of creating a Windows Phone 8 build you’ll want to stick with a simple template. Select the appMobi Windows Phone 8 Hello World template.

    HTML5 Hello World


    Click on the template and find the install command. Copy the Install-Package command to your clipboard. Do not include the PM> prompt portion.



    Return to Visual Studio and open the Package Manager window by selecting View > Other Windows > Package Manager Console. Paste the Install-Package command on your clipboard into the Package Manager Console and press the Enter key.

    PM Console


    After successfully installing the package, you will note that the Solution Explorer window updates to include an “html” folder and other specific “appMobiPage” files. You will also notice that a readme.txt file is displayed in the VS edit window. This file contains information about the contents of the template, and how to use it. Continue with those instructions, or follow the next few steps here.

    To bind the project to the appMobi template selected, you will need to modify the WMAppManifext.xml file loaded at project creation. This file can be found in the Properties directory. In the editor window for the WMAppManifest.xml file, you will need to update the Navigation Page field value.

    Nav Page


    Change the Navigation Page value to “AppMobiPage.xaml” and then save the file.


    appMobi Page


    Now you’ll want to import the appMobi project bundle into your newly created project. Copy all the files in the bundle with the exception of the files in the “_appMobi” directory. Paste all those files into the “html” directory of your Visual Studio project in the Solution Explorer.

    Once your project bundle is in position, you’ll need to identify which files you want included in the build. Make sure to reference all the files you use for your project bundle in AppMobiWebSource.xml.

    appmobi source


    At this point, you are now ready to start developing and debugging your application in the Windows Phone 8 environment. Use the WP8 emulator within Visual Studio to aid with device debugging.

    For More Information

    So you want to get started? Head to the Chrome Web Store to grab the XDK, and download Microsoft Visual Studio 2012 for Windows Phone 8.  

  • DaveDev

    Windows 8 Game Kit updated with Windows Store Share Contract


    Windows Store Share Contract

    I had some requests for an example of the Windows Store Contract in the Kit.  I created simple function that will allow the player to share out their score with other Windows apps at any time.  The purpose here is a quick and easy example you can add to your own games. 

    What code was updated?

    Inside default.js we add a new variable to handle the title of our message.

    //Share Text
    var SHARE_TITLE = "Check out my Space Cadet score!";

    Next, we create a reference to the DataTransferManager  and listen for its datarequested event.  MSDN describes the DataTransferManager as follows:

    The DataTransferManager class is a static class that you use to initiate sharing operations. To use the class, first call the GetForCurrentView method. This method returns the DataTransferManager object that is specific to the active window. Next, you need to add an event listener for the datarequested event to the object. This event is fired when a sharing operation starts—typically when the user taps the Share charm, although it is also fired if your app starts a share operation programmatically.

    The DataTransferManager class includes a ShowShareUI method, which you can use to programmatically start a share operation. In general, we recommend against using this method. Users expect to initiate share operations by using the Share charm—when you launch the operation programmatically, you can create an inconsistent user experience. We include the method because there are a few scenarios in which the user might not recognize opportunities to share. A good example is when the user achieves a high score in a game.

    We are going to follow the guidelines and only create a package for the DataTransferManager when the player using our game requests it.  The code to create an instance of the DataTransferManager and listen to the event looks like this:

    //Share Contract
    var dataTransferManager = Windows.ApplicationModel.DataTransfer.DataTransferManager.getForCurrentView();
    dataTransferManager.addEventListener("datarequested", shareScore);


    Finally, we will implement the shareScore function that will handle the datarequested event.  It is important to point out that since we don’t actually create the package until we handle the event we can share out different types of data from our game depending on what screen we are in.  For demonstration purposes I am using just the one listener but you should feel free to create different ones in your different game pages.

    We then fill out the properties of the request object to use text.  The text will be a combination of our player’s name, their current level and their current score.

    //Share Contract for High Score
    function shareScore(e) {
        var request = e.request;
        var playername = document.getElementById("txtPlayerName");
        request.data.properties.title = SHARE_TITLE;
        request.data.setText('"' + playername.innerHTML + '" has reached ' + txtLevel.innerHTML + ' with ' + txtScore.innerHTML + '!');


    Sharing out the score

    When we run the game we simply hit Windows-H (share) or go over to the Charms (Windows-C) and select Share.  At this point the DataTransferManager will send our game the event, we will fill out a request package with text and then the DataTransferManager will list all of the Windows Store apps that have registered to handle a Share for Text.

    If I select the Mail app on my own PC and you can see the title has been correctly filled out along with my player name, score and level.


    Share - Mail

    My PC also has a Windows Store Twitter app, MetroTwit, that has registered to handle Sharing of text.  I am able to easily tweet out my score here as well.

    Share - Twitter

    That’s it!  With just a few lines of code your game is now the source of a Share Contract allowing players to share our their scores with the world (and making your game a lot more appealing in the process).

    Where to download the code

    The main Codeplex release has been updated with the changes.  You can grab the latest release Win8GameKit-Jan2013 or simply browse the Source Code for the changes.



    The GitHub Win8GameKit repository has also been updated if you prefer to follow the project there.



  • DaveDev

    Announcing the Windows Phone Development JumpStart


    Windows Phone 8 Apps








    Cambridge, MA





    Tampa, FL





    Ft. Lauderdale, FL





    New York, NY





    Chevy Chase, MD





    Alpharetta, GA



    Seating is limited, so register today.









    These FREE events are targeted at jumpstarting your knowledge on a particular topic. At the end of a JumpStart you should have an idea of what you are going to try and accomplish and how you are going to get there. This JumpStart targets Windows Phone 8 SDK. The content is structured for all dev types, whether they are students just starting out or seasoned developers we are there to help. For the seasoned Android, Symbian, Web OS or iOS, we'll share tips and tricks and all-around Windows Phone development know-how.

    9:00am - Lap Around Windows Phone 8
    10:30am - Break
    10:45am - Designing For WP8
    12:00pm - Lunch
    12:45pm - More Than An App
    1:45pm - Sensors
    2:45pm - Break
    3:00pm - Sync and Auth
    4:00pm - What's next? Contest, local initiatives, and more as a wrap up….

    Download the latest Windows Phone SDK to ensure you have the most up to date developer tools. On the day of the event, bring your laptop computer and identification.
    In the meantime, don't forget to check out the Windows Phone Dev Center where you can register to submit your app into the Windows Phone Marketplace, learn about application features, understand common tasks for Apps and much more.                    

    NOTE: This event is brought to you by Microsoft and is free of charge. However, attendees are responsible for booking and paying for their own travel, parking and accommodation.

    For more information or to register, click here
    OR CALL 1-877-MSEVENT                  




Page 6 of 68 (272 items) «45678»