Jaime Rodriguez
On Windows Store apps, Windows Phone, HTML and XAML

  • Jaime Rodriguez

    ISO image for the Windows Phone developer tools..


    For those of us who have multiple machines or re-install often and don’t like to download every time using the web installer,  there is an ISO image for the Windows Phone Developer tools

    Download using this link.. http://go.microsoft.com/fwlink/?LinkId=201927.

    This is the RTM version ( so what we released around 9/15).   Don’t forget to install the October update for the tools after you have installed the tools from this iso.

    Also, if you are a VB developer, you will have to get the VB tools support  that RTMed yesterday  

    Happy Windows Phone coding!

  • Jaime Rodriguez

    Working with GIF images in Windows Phone


    As you know, Silverlight does not have native support for decoding gif images. That is downer, but not a showstopper since several 3rd party, opensource libraries for decoding Gifs. GifCompare

    The Twitter for Windows Phone team used the ImageTools project from Codeplex to decode gifs.   It worked well, but when we implemented there were two things that bothered me a little:

    1. The decoder was not perfect.  In our experience, it does ~90% of the images we tested  [and that was thousands of images, so representative test]
    2. There was one infinite loop that bothered me.  Has to do with nextflag during decoding. The Decoder checks for flags to be != 0, and for some odd reason we have seen gifs with nextFlag = –1; this can send your app into an infinite loop.

    I knew there were other libraries and partners were using these (for example,  the GifDecoder library shared a long while ago by Joe Stegman).
    Today, I finally compared these two libs side-by-side.  I used ~400 images.  25% came from a list of Gifs that had known issues. The other 75% was a random selection by looking at a Twitter user, and downloading his followers and filtering for the ones that used gifs.

    The results:  
    Decoding wise, these two libraries are pretty much the same code.  I should have started by comparing that before I wrote my test.  Instead, I found it by accident as I dived in to fix the infinite loop above.
    The results are pretty inline with our original ~90% assessment.  My tests are a bit lower but again it is because I spiked the test.

    The codeplex library is getting updated a lot more, and is growing and getting fixes, so that is what I am sticking with for my projects.
    They have done a lot of work on their AnimatedImage control (which supports animated gifs, looks pretty neat (though I have to say animated gifs feels like going back in time).

    If you need to decode Gifs, I do recommend you use this library. It is better than nothing.   Please do make sure you:

    1. Download the latest from codeplex. It is getting updated often.
    2. Test it for infinite loops.  You can download the source for my comparison app. I am attaching it to this post.  Or you can just check the source for the library.  The current issue is at ImageTools.IO.Gif.GifDecoder.Decode ()  their loop checks for  while nextFlag != 0 ….   and I simply tweaked it to  while nextFlag > 0 …    I have no idea what my changed does to GIF decoding since I know nothing about the format, but I know that I can get  ~90% of my Gifs to decode and I don’t have the infinite loop, so it works for me..

    I am sure the library will improve over time,  I pinged the folks with my tests and my results in case it helps improve. 
    Source for my little test, and source for the libraries I used (with small changes) are in skydrive

    Happy Windows Phone coding!

  • Jaime Rodriguez

    Windows phones hardware reviews


    Kevan Hutson (or some one in his team) created this great ‘aggregation’ of reviews of different Windows Phone models.
    It is a bit US-centric, because it aimed at helping the MS-based US Employees order their phones now that Windows Phone is launched in the US.
    Still think it might be useful to many of the people reading this blog.. and if not, it can influence others to share better links, or even their own reviews..
    So, with Kevan’s permission, sharing his internal list.  

    Take it with three grains of salt; I did not read all the reviews, this is very unofficial, and I am sure not comprehensive.. Still, it did help me, so I thought was worth sharing..

    Samsung Focus | AT&T

     Brilliant 4” Super AMOLED Screen  
    Thinnest, lightest Windows Phone
    Audience Noise Reduction

    Consumer Reports: Samsung Focus is sharp, with a few dull spots
    The Samsung Focus looks like a winning smart phone, thanks to its gorgeous display and the efficient and attractive operating system behind it.

    Gizmodo: The first Windows phone that matters
    [Samsung Focus is] the thinnest and lightest Windows Phone, and its Super AMOLED display is the best screen too. If you're going to get a Windows Phone, this is the one to stare at the hardest.

    The Samsung Focus plays up Windows Phone 7's strengths and plays down its weaknesses for a great Windows Phone experience.

    The Focus is kind of the everyman of the Windows Phone 7 line. It doesn't really have any fancy features and isn't especially stylish... but it gets the job done.

    MobileBurn: Windows Phone 7 and great hardware
    The build quality on the Focus is amazing. It is a very solid and rich-feeling device. That it is good looking and features the best looking display on the market, in my opinion, certainly doesn't hurt.



    LG Quantum | AT&T

    Full QWERTY Keyboard
    16 GB Internal Memory
    Play To (DLNA) Support

    Engadget: LG Quantum first hands-on!
    We're very torn on the LG Quantum. From the outside you've got a design that can only be named as "frumpy," with wasteful curves and rubberized edges, along with the smallest screen of the AT&T bunch. Still, slide this puppy open and you're treated with one of the best QWERTY keyboards in the business.

    The Quantum takes a stand as it is the only Windows Phone 7-based device with a slide-out full QWERTY keyboard.

    The LG Quantum could be a quantum of trouble. The first Windows Phone 7 device with a full keyboard that will be sold through U.S. carrier stores, it has a balky sliding mechanism and a really bizarre keyboard layout that could kill its appeal.


    HTC Surround | AT&T

    Slide-out speakers w/ kickstand
    SRS Dolby Mobile Surround Sound
    16 GB internal memory

    It's business as usual for HTC: attractive and understated finishes that avoid looking plasticky, a solid feel in the hand and considerable heft thanks to the slider design.

    The HTC Surround promises a big entertainment experience with its kickstand and huge slide-out speaker, but Windows Phone 7 just isn't up to the task.

    The Surround needed to bring a lot to the table in order to justify being bigger and heavier than the Samsung Focus while lacking the QWERTY keyboard of the LG Quantum, and we just don't think a pair of average speakers and a kickstand provides that justification

    Gear Live
    The HTC Surround is a good phone, and its the one we'd recommend if watching movies and listening to music is your jam.


    HTC HD7 | T-Mobile

    Largest 4.3” Screen
    T-Mobile TV built-in

    The hardware could use a bit of updating, but the HTC HD7 for T-Mobile combines the power of Windows Phone 7 with a large touch screen and delivers satisfying performance.

    The T-Mobile HD7 is a good-looking phone that's a fine canvas for Windows Phone's services, but it's not at the top of its class.

    Overall, the HD7 is not a bad phone, and it's a perfect serviceable vehicle for Windows Phone 7. It's just not a great phone.

    Boy Genius Report
    The Windows Phone 7 OS on HTC’s HD7 is absolutely fantastic in many respects, and yet in other areas, it is an OS filled with almosts.

    The reason we like the HD7 is that it seems to be just about the perfect size for us. It trades little in the way of added bulk for an awful lot in added real estate and general usability.

    The HD7′s large display, responsive interface and our generally positive feelings about Windows Phone 7 all stand in its favor, but there are still niggling flaws and frustrations that mar the overall experience.


    Dell Venue Pro | T-Mobile

    Vertical QWERTY Keyboard
    Scratch & Shatter Resistant Screen
    Available on T-Mobile, sold through Dell

    Engadget: Dell Venue Pro (aka Lightning) first hands-on!
    No matter what you call Dell's Windows Phone 7 portrait slider, it's downright awesome.

    The smartphone feels very solid in the hand. In addition to the slide-out QWERTY keyboard, the Venue Pro also offers a 4.1-inch WVGA AMOLED touch screen, which was both sharp and responsive in our brief hands-on time with the device.

    The Venue Pro has a bit more heft than some of the other WP7 devices launching today, but it's not overly bulky. It just feels solid, durable.

    PCMag.com:  Windows Phone 7's dark horse? Hands on
    I want to love the Dell Venue Pro. This is the Windows Phone 7 with a keyboard that might actually work. But it's from Dell, and even T-Mobile doesn't seem to have complete faith in the phone.

    Additional reviews worth reading:
    CNET - First impressions: HTC HD7, Dell Venue Pro
    Engadget - Windows Phone 7 in review: the good, the bad, and the Surround
    InformationWeek - Review: AT&T's Windows Phone 7 handsets tested
    Maximum PC - Windows Phone 7 impressions: The first 24 hours
    PhysOrg - Review: Microsoft hits refresh on smartphones
    ZDNet - Hands-on with the HTC Surround and Samsung Focus WP7 smartphones

    Additional Model Reviews - EU and APAC
    LG Optimus 7 E900 review (Stuff Magazine)
    Samsung Omni Review (Telegraph)
    Trophy (TechRadar)
    Mozart (Pocketlint)

  • Jaime Rodriguez

    The Windows Phone platform and Windows Phone devs are both doing great


    Yesterday, I saw a few posts, tweets and personal emails from smart, professional developers  who are building great windows phone apps and did not appreciate getting caught in the recent slew of press and marketing exchange around Windows Phone perf.   I am going to share my personal experiences to try to clarify the likely misinterpretation..

    The problem/story:
    Press goes to marketing (not engineering folks) and tells them “when are you going to fix the perf problems in the platform, we are seeing a few apps lag?” … 
    Windows Phone marketing answers it the way they see it “there is no problem with the platform, we are working on education for developers to improve their apps”..
    Some developers then get upset and respond with a “what are you talking about? We know our stuff, our apps are good, some are even great, we just need you to improve <insert a feature or a hardware component here> so it is faster..” ..

    At first glance, the stories are in partial conflict.. and the developers get caught in the middle (since they are not in the conversation that is getting reported), so I have to share my personal experience as a developer collaborating with partners and developers  to build build good and great Windows phone apps(disclaimer, I still work for Microsoft so I am biased, and all that, but I also like to tell it like it is so read on and decide).

    Answer or state of the union:
    Every platform always needs performance improvement. Users will always demand more.  Engineers will always aim to provide more. I know our Windows Phone engineering team has improvements and fixes coming into the platform to make things better/faster…

    At the same time, the journalist question around “fixing the performance in the platform” is a loaded question and implies “it is broken”. 
    Every platform has small bugs and short-falls so the question is whether this is a systemic problem or a big hole that really qualifies ours as “broken”.  I can’t speak for every developer but my experience has been that there is a very reasonable (low) number of bugs as expected, and the platform works and performs well with-in user expectations, so I can understand why MS marketing folks are  responding with the “it is not broken, we just need to advise developers to get the most out of their apps”.

    So, why do they say that?  I won't speak for all developers, but I can share that  100% of the apps I have been involved with, can use performance improvements that developers can make today but simply need more time to implement or did not understand a month ago; these are new apps, new usage patterns, etc.. There is also changes that will (eventually) come for free to the platform as improvements (you can call them bug fixes if you want but I would call them optimizations) that will make existing apps better (with out neding changes).

    On my partner’s projects, we had to balance between features, optimizations, and polish within the constraints we had to get us to launch – biggest constraint being time,  beta of the platform was shipped ~3 months from RTM, most apps were built in this time-frame.   As developers and engineers, we discover new characteristics or niche scenarios in the platform every day. We are are thriving with all these great new lessons or lessons that others are sharing, and we are improving the apps, lots of these apps are already released their first or second update, and I am sure every one of these is better than their previous release.   

    That is why Microsoft is emphasizing education and broad sharing. It is not blame, it is just a natural partnership for any brand new platform ..

    To the developers:

    When you hear MS marketing folks say “we are working to train and educate developers to improver performance on their apps” please don’t misinterpret as an insult or blame . What Microsoft folks are trying to say is “we have a great platform, but the hardware has been available only for a short time, the new amazing experiences we are seeing every day have never been built before on any platform.  We know we have a strong foundation, but we learn new stuff every day,  and we want to share it as guidance and education so you (developers) can leverage the tips can make your apps even better. 

    In my opinion, there is a lot to be proud of..   There is some amazing apps, and some great reviews.  The fact that reviewers like Gizmodo are comparing the Windows Phone apps to apps that have been in other platforms for 18 months to 3 years, and we are comparing neutrally or favorably is pretty amazing.   It has been ~8 months since developers even heard of our platform.  It has been only four months since beta and only a few weeks of marketplace being open.  What do we have to show for?  Thousands of apps in the marketplace, tens of thousands of developers registered,  over half a million downloads of the tools..   All-up, this is a great story…  The read I get from peers at Microsoft is that we are very proud of the platform and the tools,  and we are very impressed (often amazed) with some of the the apps that are getting in the marketplace.  We are heavily invested in providing the best tools and the best guidance.  When we say  we are working on education, all that means is we are ready to partner with you  (our developers).  Your success is the pillar to our own platform’s success. Long-term, we will optimize the platform even further , and half of the issues that are annoying us today will be gone,  but interim, we will have to work together to create great apps.   We know the platform can do it since plenty of you devs already proved it.. 

    Let’s keep rocking and don’t over analyze sensationalist titles to news stories..
    That is my personal 2c.  Back to my writing some good tips on my upcoming Windows Phone book Winking smile ..

  • Jaime Rodriguez

    GeoCoordinateWatcher tips part1


    A few tips for those using GeoCoordinateWatcher in Windows Phone 7.

    The data:

    • GeoCoordinateWatcher events fire in the UI thread.  Yes, StatusChanged and PositionChanged fire in the UI thread. 
      This is not due to thread affinity or any thing similar. Even if I start the GeoCoordinateWatcher in a background thread, it still fires events in the UI thread. They wanted to make it easy for developers.
    • GeoCoordinateWatcher PositionChanged will fire as often every second if you do not give it a MovementThreshold. Yes, you can not move at all and it is firing (on your UI thread).  Note, that is what I see on my phone, I do know the phone is optimized for battery life, so maybe it throttles with battery .. but when fully charged I see a ~1 Hz rate.
    • Getting a GPS fix out of GeoCoordinateWatcher can some times take a second or two. GPS is never a trivial operation (if you have ever turned it on in your car, I am sure you would know).  This can be a pain if you have an app that needs a fix in milliseconds, for example, if you are in search, and you want to do a local search, you want it to have location immediately, you don’t want to wait a second …

    The Tips:

    • Avoid doing a lot of work on the GeoCoordinate events.  They are in the UI thread. Avoid as much work as you can (send to background thread if needed).
    • Absolutely set a MovementThreshold on the GeoCoordinateWatcher   20 meters is probably lowest you should you.  I most often use 250m. Most of the services I use ( twitter, facebook, search, etc.  are doing searches in a > mile radius, 250m is great threshold for these services)…
      • if you do set MovementThreshold you should know that GeoCoordinateWatcher fires event in a weird order and the order can get you when you use MovementThreshold.
      • GeoCoordinateWatcher has a StatusChanged,  which you would expect fires when the GCW is ready…   my experience is that when subscribing to GCW I see this sequence
        • StatusChanged to Initializin
        • PositionChanged   -- with a valid location
        • StatusChanged to ready
        • If you have a high threshold, PositionChanged might not fire again…  so if you were a cautious developer and checked that Status is ready before accepting the location, you might not get a PositionChanged.   
      • The answer (from the devs) is that it is fair to assume that if PositionChanged fires, the status is ready.  It is OK to not check status in this event.
    • If  you read above, when there is no threshold it fires every second…  I am told the threshold does affect sampling rate (we are preserving battery as much as we can) but I am also thinking they are doing work sampling more often than most of my apps need.. I am not writing some thing that requires a position every few seconds..  so what I do for most of my apps is Start () and Stop () the GCW every 2 minutes (or longer pending on the app)…   Start and Stop is not an expensive operation…    Just have your GCW be wrapped by a singleton, and start it and stop it often..  Avoid calling Dispose () on GCW..   I have very seldomly (when stress testing) seen a race condition on Dispose () that could crash my app…   again, happens seldomly but I still don’t like the chances, since it is a singleton, and you can start and stop.. I don’t see a need to Dispose ()..

    That should be all you need to really optimize your location-aware apps… Don’t forget to prompt the user before you use their location ..  
    Feel free to beat me to the next part… you should know what that is..

    Happy Windows Phone coding !!

  • Jaime Rodriguez

    Slides and demos from TechEd sessions..



    I have uploaded my slides and demos from my teched sessions.  alt
    Thanks for attending and staying awake Smile 


    Happy Windows Phone coding!

  • Jaime Rodriguez

    XAPAthons at Teched Europe 2010


    On my way to TechEd Europe today, and just found out there is a room available to host a Windows Phone XAPathon..
    There was also room for T-shirts for first 12 XAPathon RSVPs.   If you are at the event. Below is the likely places you will find me..


    What is a XAPathon?
    A casual short ( less than an hour unless schedule allows for more) meeting with a so-named Windows Phone expert (in this case me and/or Oren Nachman, a perf expert).
    You can do anything you want with the time:

    • We will have phones, some tools, and eagerness to help you with your app.
    • You can join us for an hour and ask questions, chat, or just borrow a phone and see how your app performs on it.
    • If you are an expert and have already coded an app, you can still join and shoot a brief 15 minute video about your app and your experiences hacking on WIndows phone.  I can then put it as part of my “Windows

    How do I sign-up for a XAPathon ?
    Email me via the link on this blog post.. or contact me via twitter @jaimerodriguez  or Just stop by at the Passau 4 room  (yes, you have to be a registered attendee, sorry).

    Break out sessions

    09:00 Windows Phone Pre-Conference
      ( a ~5 hour dive into building WIndows Phone apps..
    Taught by yours truly.  
    Still working on the timings for the session but slides and decks are done. It will flow like this:

    1. Intro to phone (goals, design, hardware audience)   - Intro
    2. Phone UX – pragmatic
    1. Metro – intro
    2. Interactions – pragmatic
    3. Includes deepdive into phone controls – pragmatic
    • Integrating w/ hardware – pragmatic
    1. Accelerometer, location, mic,  etc.
    2. Keyboard,
    3. Touch
    4. Choosers and launchers
    • Navigation – deepdive
    • tomb stoning – deepdive
    • Push notification – deepdive
    • Lessons learned from a few apps – deepdive
    1. Data
    2. Perf
    3. Other ..

    [intro == 15 mins or less, and it is 200 level] ,
    [pragmatic == 200 to 300 level intro+good practices]
    [deep dive == all you will ever have to know about it]


    10:30 WPH101 - Changing our Game : Windows Phone 7 and the Windows Phone 7 Application Platform
    12:00 WPH202 - User Experience Best Practices for Building Applications on Windows Phone 7
    16:30 WPH305 - Understanding the Windows Phone 7 Development Tools


    9:00 WPH306 - Silverlight for Windows Phone 7
    12:00 WPH307 - Building Windows Phone Games with Microsoft XNA and Visual Studio 2010
    16:00 WPH309 - Developing Windows Phone 7 Web Applications with WebMatrix


    09:00 WPH310 - Giving your Windows Phone XNA Games Plenty of Whizz and Bang
    12:00 -WPH311 - Microsoft Silverlight Performance on Windows Phone
    16:30 -WPH214 - Understanding Marketplace and Making Money with Windows Phone 7 Applications
    18:00 WPH315 - Developing for Windows Phone 7 - End to End


    09:00 WPH316 - Building Offline Experiences for Windows Phones and Other Devices using Sync Framework
    10:30 WPH117-IS - Come and Meet the Windows Phone 7 Team
    12:30 WPH318 - Developing Code for Windows Mobile and Windows Phone 7

    Silverlight Focus groups

    At TechEd Europe, the Microsoft Silverlight team will be conducting several focus groups (60-90 min) on-site November 11th, and the purpose is to solicit opinions about Rich Internet Applications (RIA) platforms. The team would love to learn more about your thought process when evaluating these technologies and about your experiences building applications with various solutions!

    All focus group participants will be given a gratuity (Microsoft software) for their contribution.

    To participate, please enter the URL below into your Web browser and fill out a brief form with your name, contact information, and your level familiarity with various RIA platforms, http://www.surveymonkey.com/s/GKG3RN6

    Note: We will only use this information to schedule some time to talk with you while you are at the show, and will not add you to a mailing list or share your information with third parties.

    Hope to c u there.. 
    Happy WIndows Phone coding..

  • Jaime Rodriguez

    Guessing if the SIP is visible in a Windows Phone application


    For Silverlight applications, Windows Phone does a good job at abstracting the keyboard from the platform. 
    As a developer, you drop a TextBox any where in your app and whenever the textbox gets focus:

    • The platform will launch the SIP if the hardware keyboard is not available.  When the SIP comes up,  the platform also applies a TranslateTransform to the RootFrame of the application, so that the SIP takes its space, but the textbox is still visible. 
    • The platform does nothing if the hardware keyboard is available. SIP does not come up, does not get on the way, etc.

    Again, all of the above comes for free, and is pretty convenient most of the time.   Unfortunately, every now and then, you do run into a scene that maybe has a button underneath the textbox ( for example, a login window or a  sign-up window with a button near the bottom).   If you are in one of these situations,  the news are not so great. There are no platform events or classes to tell you if a SIP is available and/or when it is shown or hidden.    There is a “hack” that works most of the time:

    When SIP is visible, and the screen has been translated,  the transform is applied at the App.RootFrame (which is a PhoneApplicationFrame).   The easiest way to get notified when this Transform changes (to avoid polling) is to data bind to it; using a DependencyProperty, you get free notifications when the property changes (which of course would happen if the SIP is visible. 
    Here is a sample snippet, that sets an IsChecked property in a checkbox whenever we think the SIP is visible.

       1: public partial class MainPage : PhoneApplicationPage
       2:    {
       3:        // Constructor
       4:        public MainPage()
       5:        {
       6:            InitializeComponent();
       7:            BeginListenForSIPChanged(); 
       9:        }
      11:        private void BeginListenForSIPChanged()
      12:        {
      13:            PhoneApplicationFrame frame = (App.Current as App).RootFrame;
      14:            Binding b = new Binding("Y");
      15:            b.Source = (frame.RenderTransform as TransformGroup).Children[0] as TranslateTransform;
      16:            SetBinding(RootFrameTransformProperty, b);
      17:        }
      20:        public static readonly DependencyProperty RootFrameTransformProperty = DependencyProperty.Register(
      21:          "RootFrameTransform",
      22:          typeof(double),
      23:          typeof(MainPage),
      24:          new PropertyMetadata(OnRootFrameTransformChanged));
      26:        static void OnRootFrameTransformChanged(DependencyObject source, DependencyPropertyChangedEventArgs e)
      27:        {
      28:            double newvalue = (double) e.NewValue;
      29:            MainPage page = source as MainPage;  
      30:            if ( newvalue < 0.0 )
      31:            {
      32:                page.IsSipVisibleGuess.IsChecked = true; 
      33:            }
      34:            else if ( newvalue == 0.0 )
      35:            {
      36:                page.IsSipVisibleGuess.IsChecked = false ; 
      37:            } 
      39: #if DEBUG 
      40:            else 
      41:                System.Diagnostics.Debug.Assert ( false, "I assumed this would never happen, let me know if it does"); 
      42: #endif 
      44:        }
      46:    }

    Full disclaimer, this post begins with guessing. it is not 100% fail-safe.
    The scenario where it fails is when you set focus on a textbox and SIP comes up, and then you open the hardware keyboard on the phone. The platform does not always apply the transform immediately.  The snippet is still right, since the transform has not been removed, but it is annoying that hardware keyboard is readily working and transform is still there.

    The snippet also does not tell you if the SIP is visible when the TextBox is so high enough on the scene that the rootframe does not get translated at all.

    I would recommend you avoid using the trick when you can,  the easiest way to avoid it is not to put buttons that can be covered by the SIP (so no buttons underneath the textbox). . Put the buttons either above the textbox, or on the ApplicationBar. The latter being my preferred approach.

    If you want to try it, the source is here.

    Happy Windows Phone coding.

  • Jaime Rodriguez

    Tips for debugging WP7 media apps with WPConnect


    Monday’s blog post on  running under screen lock generated a couple of questions around media not playing when medialibrary is locked ( and Zune locking Media Library).
    So, today, I remind you about a recently announced tool that shipped with the Windows Phone Developer Tools October Update.

    The tool is called Windows Phone Connect Tool ( internally we know it as either WPDTConnect, or WPConnect, the latter is the final name of the exe as it made it out externally).
    Full instructions on running and troubleshooting WPConnect are here.   My personalized version is below.


    • Of course, this requires you have the WIndows Phone Developer Tools installed (dah!) . Get the tools from here
    • This also requires you have a version of Zune capable of connecting to Windows Phone. That is version 4.7.1404.  Get it from here
      You will not be running Zune during the debugging, but WPConnect is still using some of that infrastructure that Zune installs.
    • At last, you need to install the WPDT October Update.  Get it from here.

    To run WPConnect:
    You simply need to run the WPConnect.exe. 
    By default it will be installed at  %ProgramFiles%\Microsoft SDKs\Windows Phone\v7.0\Tools\ or at %ProgramFiles(x86)%\Microsoft SDKs\Windows Phone\v7.0\Tools\WPConnect.
    The instructions on MSDN talk about opening a command prompt and navigating to that directory; that is Microsoft internal instructions. For the rest of the world that does not use DOS and command prompt as much as we do inside , you can do any of these and it will work equally well.

      • Run WPConnect from a short-cut on your desktop. 
      • Copy the WPConnect executable some where in your path or your desktop or what ever and run it.

    The really important stuff is to:

    1. Do connect once with Zune before running WPConnect. As I mentioned, the infrastructure is shared.
    2. Make sure you stop Zune before you run WPConnect.
    3. Run WPConnect [any way you want, command prompt not required]

    The results:
    What you  will get is ability to debug applications that play Media on the phone without media library getting locked. You can also debug applications that interact with MediaLibrary.

    A couple of FAQs and or known issues:

    • The update to the tools is an MSP. It is pretty silent. Run it and as long as you do not get an error you will be fine. If you need to test if it succeeded, check for WPConnect.
    • There is no significant advantage or disadvantage between debugging using WPConnect and/or Zune. One is not faster than the other or any thing like that. It is same communication services underneath.
    • WPConnect runs for a few seconds and then exits.  This is expected, don’t be looking for it in taskmgr. If you launch it and it says it connected, you will be able to debug for hours without having to relaunch it. It is like a silent ninja, you don’t see it but it is there ready to strike.
    • Launching Zune any time after WPConnect is running will disconnect WPConnect. This most often happens if you disconnect your phone and connect it again.  The workaround is to close Zune and WPConnect again. 

    That should be all you need.  Read the full instructions for more troubleshooting tips. Hope that helps.

    Happy Windows Phone coding!

  • Jaime Rodriguez

    Hail to the swiss army knife of Silverlight Windows Phone Apps LongListSelector


    Today,  David Anson announced the second release of the Silverlight for Windows Phone  toolkit.   

    This release doubles the number of controls in the kit, includes page transitions, ListPicker, and the new Swiss Army style control for Windows Phone: LongListSelector..
    I am still getting deep into LongListSelector and trying to fit into some apps, but the potential for it is so great, I am doing a preview post on it..

    LongListSelector started as a list that would address the requirements for lists similar to the people hub list.. 
    Headers and Footers that scrolls with the items in the list (see how the “new releases” header scrolls with the list items, this is great for panoramas )

    , WP7_1 (62)                      WP7_1 (63)WP7_1 (65)

    It then morphed into grouping ( similar to Quick Jump Grid control )  

    WP7_1 (67)

    WP7_1 (66)









    And finally but still equally important as a very performant listbox where you have a lot of control on how items are virtualized, how fast the list scrolls, how big your bounces are, etc.
    LongListSelector  uses a different scrolling mechanism ( animation on render thread ) and different virtualization strategy ( not a VirtualizingStackPanel) that results in better, smoother scrolling in most ListBoxes…


    What are you waiting for???  Go download the toolkit from codeplex

    Happy Windows Phone Coding!

    PS --- Test thoroughly.. With this high degree of customization and so many features into a single control, it is not too hard to make a mistake..  Make sure as you replace your standard listboxes with LongListSelector, you tune the knobs so it works just right for your app..

  • Jaime Rodriguez

    Running a Windows Phone Application under the lock screen


    Last week, Microsoft published new Application content policies for Windows Phone 7 Apps.  One of the changes that got attention was the ability to run applications under a locked screen.  Refer to section 6.3 of the application certification requirements.

    In reality, the change is pretty minor, the capability to run under lock screen has been there since RTM.  Microsoft simply published some new ‘guidance’ on the expectations for applications that run under a locked screen.  That said, the change was interpreted as Microsoft relaxing the guidelines, since now it is clear that running under locked screen is not going to be frowned upon as long as you meet the requirements.  

    Why run under a locked screen? What are the benefits?
    Many applications are expected to run under a locked screen:  music players, run-tracking applications,  map applications, etc.  These applications will likely not change, as the certification guidelines had already approved these scenarios.  

    The changes to the certification requirements are aimed at apps that want to avoid tombstoning. For applications that are slow to recover from tombstoning ( maybe they make network calls and download a lot of data at start-up), they now can avoid the overhead of recovering from tombstoning when the application goes under locked screen.  You simply let the screen lock come on, and stay running quietly without consuming a lot of battery, and when the lock screen goes away, then you restore doing your business, but the gain to the end-user was they did not wait for a second or more while your app re-hydrated from a tombstone.   Since your app was never killed, response time is immediate. 

    Before we go much further on this topic, I do want to emphasize that running under lock is not an excuse so developers do not implement a super-fast, comprehensive tombstoning strategy. There are plenty of valid reasons why an app tombstones ( Choosers, App switching, etc.) that can’t be avoided, so you should still work hard to get the absolutely best tombstoning you can implement.

    Still, running under locked screen is a very nice to have for some apps, so I did a bit of digging and below are my tips, lessons learned, and even sample code, you can reuse to get your app to run under lock.

    Running Under Locked Screen
    In short, to let your application run under locked screen,  you must:

    1. Set PhoneApplicationService.Current.ApplicationIdleDetectionMode = IdleDetectionMode.Disabled;
    2. Handle the  Application’s RootFrame  Obscured and Unobscured events.  So you know when the lockscreen comes on.
      Obscured will be called when your app is getting locked.  Here, you should do as much as you can to minimize CPU or battery consumption. Stop all animations, stop making network calls, stop listening to accelerometer, or location changes, etc.. 
      Unobscured of course gets called when screens us getting unlocked. This is when the user comes back, and you pick where they left-off before phone went under the lock.
    3. [Optional] To have a great user experience with user in control,  you should prompt the user so they opt-in into running under lock.
    4. [Optional] You should expose as part of your application configuration settings an option for the user to change their mind or simply want to disable it and conserve power.
    5. There was only one gotcha that I noticed. If your application sets ApplicationDetectionMode to IdleDetectionMode.Disabled,  it can not change that back to IdleDetecionMode.Enabled until application is either launched again (so a full restart) or deactivated and then reactivated.

    Getting all this to run was trivial, but required a few more lines of code than the four items above (to save settings, fire events, etc.) .   I wrote this helper class called ApplicationIdleHelper.

    The class is a Singleton.  That is why the static Current property, so it can be shared throughout the app. The class supports change notification so you can bind to it. image

    • The class tracks three settings/properties:
      • RunsUnderLock is true if the user has elected to run under lock.  This setting is persisted across activations and launches of the app so we remember the user’s preference.  The property also supports change notification.
    • HasUserAgreedToRunUnderLock is true if the user was prompted using UI with a disclaimer that running under lock can consume battery.  This setting is serialized to ApplicationSetings, so that you don’t have to prompt the user every time.
    • IsRestartRequired is a transient property that does not get persisted. It simply flags whether the user has changed from IdleDetectionMode.Disabled to IdleDetectionMode.Enabled.  If we try set this transition, we will get an exception that tells us once Disabled is selected you can’t go back to Enabled.  Reality is that you can do it next time application is activated, so you just have to prompt the user to restart the app if they want the change to take place.
    • IsRunningUnderLock is a transient read-only property that supports change notification. This property tells you if the app is currently under a locked screen.  Good flag to make sure you are not doing work you are not supposed to, remember you are stealth under the lock screen (to preserve battery).
    • The application also supports three events:
      Locked  is fired when the Locked screen comes on. It is an abstraction so you don’t have to listen to RootFrame.Obscured event.
    • UnLocked fires when the application transitions from being in Locked state to it being in unlocked state and visible to the user. Again, equivalent to Unobscured event. 
       RestartRequired so that your classes are notified if the user has made a setting change that requires a restart (mainly going from IdleDetecionMode.Disabled to IdleDetecionMode.Enabled).

    That is all there is to it.  Plus, a bit of glue and a sample app for you to see it in action.

    About the sample app.

    WP7_1 (60)

    It is a very simple pivot app that plays music using MediaElement.
    You can toggle your preference to run under lock (or not to do that) by clicking the “Toggle current preference” button.
    You can play/stop music by pressing the Play/Stop button.
    The app will manage the settings for you. The UI under “Current settings” is data bounds to the ApplicationIdeleModeHelper so you can see it working.
    The events are fired properly too.

    Here are the behaviors you should see:

    If you are in the greedy pivot, and have chosen to  Run under Lock,  the music will continue playing under lock.
    If you are in the greedy pivot, but have not chosen to run under lock, the app will tombstone when the phone locks and there for the music will stop.
    If you are in the mellow pivot,  even if you have chosen to Run Under Lock,  the music will stop.  The application is not tombstoned, but it stoppped doing the work. It listens to the Locked event and stops doing work then, and then listens to Unlocked event and resumes there.  Again, without tombstoning. I just wanted to show you how you can “decrease” the work you do under lock, to avoid consuming battery.

    NOTE: To exercise the app you will need a device, as I don’t think the emulator runs under lock or simulates lock.  Also, when running this, make sure your device is not attached to Zune, as that will lock media library and prevent the app from playing music (and this sample does not throw error for that).

    The source for the app is on my Sky drive.  Let me know if you find issues or have questions.

    As my uncle used to say, “with great power comes great responsibility” ..  Running under lock is pretty neat, but advanced feature, do not abuse it.   Only use it for the kinds of apps that end-users would want to keep open even while locked.

    Happy Windows Phone coding!

Page 1 of 1 (11 items)