John R. Spinella Blog

Using PowerShell to implement a Farm-wide Global Navigation solution from the Managed Metadata Term Store in SharePoint 2013

John R. Spinella — Thu, 04 May 2017 00:44:11 GMT

Co-Written by John R. Spinella & Daniel Setlock We had a requirement at a customer to provide unified Global Navigation across their SharePoint 2013 farm, ideally that was fed through the Term Store they had already developed within the Managed Metadata Service. It was a struggle to find a solution that was easy enough to maintain, and provided the experience that users desired, and we thought others might like to take advantage of it. The purpose of this post is to demonstrate how to export the Managed Metadata Term Store via PowerShell to a SiteMap, and import that SiteMap into a multi-tiered dropdown into the Structured Navigation within SharePoint through a code-less method. It is possible to use the Term Store to push Global Navigation across Site Collections within SharePoint, however anyone who has attempted it has likely run into issues. The most common being that it is possible to pin a term set to a Site Collection, but only a single Site Collection. You can pin the same Term Set, however that provides a read-only copy, and the link in the navigation is not updated when the link is updated within the Term Store. It is possible to have multiple Term Sets, each for a different part of the organization, however it is less friendly to use a single Term Set across all of the Site It is a few clicks to provide the Human Resources Site Collection with its own navigation, same with Legal, and so forth. However once on the Human Resources Site Collection, via the traditional method, you would lose the links to Legal, IT, and Finance. The goal is to provide a single navigation across all Site Collections, at the top level (Term Set) to provide access to Terms, and child terms, without the need to copy Terms around, or pin read-only terms. There are solutions involving managed code and master page modifications to introduce Global Navigation, however most often this involve injecting the navigation into the SuiteLinks bar and presents its own challenges, and is not what users have come to expect in SharePoint. To start, a Term Set needs to be created as if it was going to be used in a single location, much like the example above. A link to the proper location needs to be included (Navigation Tab > Simple Link or Header) for each of the terms. Once a Term Set has been created, it is time to export it as an xml document via PowerShell. Exporting the Term Set The script below is modified from a posting by Alan Parsons found here. Add-PSSnapin “Microsoft.SharePoint.Powershell” –ErrorAction SilentlyContinue #Variables start $siteUrl = 'https://SharePoint2013' #Update your site URL $termSetStoreDesc = 'Managed Metadata Service Application' #Ensure you type your MMS correctly $groupDesc = 'GlobalNavigation' #Replace with your Group Name $termSetName = 'Global Navigation' #Replace with your Term Set name $saveLoc = 'C:\temp\navigation\Nav.xml' #Update your directory here $session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession($siteUrl) $LocalProperty = '_Sys_Nav_SimpleLinkUrl' $XML = '' #Variables end #Functions start function buildNode ($myTerm) { #Write-Output $myTerm.LocalCustomProperties['_Sys_Nav_ExcludedProviders'] $myXML += ' + $myTerm.Name + '" IsVisible="' If ($myTerm.LocalCustomProperties.ContainsKey('_Sys_Nav_ExcludedProviders')) { $myXML += (-not($myTerm.LocalCustomProperties._Sys_Nav_ExcludedProviders.Contains('GlobalNavigationTaxonomyProvider'))) } Else { $myXML += $true } $myXML += '"> ' + $myTerm.LocalCustomProperties['_Sys_Nav_SimpleLinkUrl'] + ' ' + $myTerm.CreatedDate + ' true Heading ' + $myTerm.LastModifiedDate + ' ' If ($myTerm.TermsCount –gt 0) { Foreach ($term in $myTerm.Terms) { $myXML += buildNode ($term) } } $myXML += ' ' return $myXML } #Functions end $termStore = $session.TermStores[$termSetStoreDesc] $group = $termStore.Groups[$groupDesc] # | Where-Object {$_.Name -like "Global Navigation"} $termSet = $group.TermSets[$termSetName] $terms = $termSet.GetTerms(200) #Update your Site and Server Relative URLs - This print at the top of the XML Document $XML = ' ' Foreach ($term in $terms) { $XML += (buildNode $term) } $XML += ' ' $XML | out-File –FilePath $saveLoc The key to the script above is that it creates the Navigation NodeType as a ‘Heading’, rather than a link. The ‘Heading’ NodeType allows for additional nested navigational objects, whereas ‘Links’ do not. However, when viewing the Structured Navigation (Via the GUI) under Navigation in Site Settings, it is not possible to nest Headings, you must do this programmatically. As a result, you cannot add additional items under the navigation once it is in place, and you would have to remove the navigation and run the scripts again. With that you should have an exported SiteMap file that looks something like the below image: Please note that the URLs in this example are all set to the same via the Managed Metadata Service Application, yours will be different and unique. Importing the SiteMap Once you have the XML file available, the next step is to import it. We did this through using the ‘Import-SPNavigation’ cmdlet. This is a custom cmdlet available via Aptillion that we already had installed, and is available at Github here. The script to iterate through the SharePoint farm and enforce the global navigation is as follows. It consumes the XML SiteMap generated in the previous script, and is targeted to a Web Application. Add-PSSnapin Microsoft.SharePoint.Powershell –ErrorAction SilentlyContinue $path="C:\temp\nav.xml" #$path2="C:\temp\nav.xml" $sites = Get-SPSite -limit all -WebApplication https://sharepoint2013 | ? {$_.Url -notlike "*/personal/*"} |Get-SPWeb -Limit All ForEach ($sites in $Sites) { # The URL to the Site $spWeb = $sites.url #Relative url $relativeUrl = $sites.ServerRelativeUrl #Get Global Nav XML and write new file based on current site [xml]$XmlDocument = Get-Content -path $path $XmlDocument.Site $XmlDocument.site.url = $spweb $xmldocument.site.Web.serverRelativeUrl =$relativeUrl $XmlDocument.Save($path) #Import new Global Nav Get-SPWeb $sites.url | Import-SPNavigation -InputFile $path -ErrorAction SilentlyContinue $sites.Dispose()} After that has been completed, you should see Structured Navigation within the Webs that looks like the following: Note that all objects are folders, which indicate a heading, rather than a link. If you have a navigation that extends past two tiers, you cannot see them on this screen, however they will be represented on the Global Navigation across the sites, as shown below.

Updating the drop-down levels

If you need to extend the drop-down list past the first fly-out, you would need to modify the masterpage. In general, the ‘MaximumDynamicDisplayLevels is set to ‘2’, which would display as shown above. If you needed a ‘Finance Sub Sub Sub Office 1’ you would need to update the value to 3, or do 4 for good measure.

Additional Styling

Depending on the length of the first-tier terms, it may cause child terms to wrap on the navigation as shown below. If this becomes an issue, adding the following styles to the masterpage /stylesheet would provide the appropriate width for navigation as seen previously in the post. ul.dynamic { width: auto !important; white-space: nowrap; } Or ul.dynamic { width: 300px !important; white-space: nowrap; }

Delete Structured Navigation

It is possible to put the scripts on a PowerShell scheduled task to enforce Global Navigation, and it would be possible to delete the current navigation within the population script. If it is necessary to delete the navigation across the SharePoint farm, the script below can be utilized. #It may be necessary to run this multiple times to completely clean out navigation Add-PSSnapin “Microsoft.SharePoint.Powershell” –ErrorAction SilentlyContinue #Update the identity with your own Web Application $Sites = Get-SPWebApplication -Identity https://SharePoint2013 | Get-SPSite -Limit All | Get-SPWeb -Limit all #Iterate through sites ForEach ($site in $Sites) { #Iterate through webs ForEach ($web in $site) { #Delete existing navigation Foreach($node in ($web.Navigation.TopNavigationBar)) { write-host $web.Title "--" "Node title : "$node.Title $node.Delete() } } $sites.Dispose() }

Conclusion

And that is how you can create a SiteMap through the Term Store, and use that to generate a Farm-wide Global Navigation solution to provide a uniform experience, code-free. Depending on the tools and knowledge available to you, there are many ways to accomplish the same thing. It is possible to leverage a custom SiteMap provider, programmatically display the Term Store across multiple Site Collections, create a solution that reads from a list or database, or utilize hardcoded navigation in the masterpage. This solved a need for a customer, and based on our experience we thought others could leverage this information to provide similar results. Happy Coding!

Release Explorer for Visual Studio Beta: Update

John R. Spinella — Fri, 29 May 2015 08:07:44 GMT

Hello,

To give everyone a update, I am currently finishing up the integration of VSO/RMO. With the next release of Release Explorer, you will be able to do both on prem and VSO. I am hoping to have this done by the mid to end of June. There are a lot of changes happening with the new version of RM, so I am trying to keep up with that. Check out some screen shot of the updated Release Explorer.

VSO version for seeing releases. It is very similar to the on prem version.

New Release Dialog

I am working very hard on this to make this a viable option in the Development/DevOps cycle.

Thanks for all your support!

John

Release Explorer for Visual Studio Beta

John R. Spinella — Fri, 06 Mar 2015 12:36:00 GMT

For some time now, I have been working on a update to my Deployment Explorer that was built for the project formally known as DevOps. I always get requests from my customers and emails from people who are using the Deployment Explorer to update the explorer to work with Release Mgt. So, I said what the heck and I’ll give it a try. This request was more on the side of the developer who does Dev/Test stuff and would like one client to work out of. My intent is not to replace Release Management Client but to enhance the experience.

** THIS IS A BETA PRODUCT, SOME FEATURES MAY NOT WORK CORRECTLY. USE AT YOUR OWN RISK***

Below is how to download it from the Visual Studio Gallery and start using it.

Installation:

First, you will need to go to https://visualstudiogallery.msdn.microsoft.com/81cdcbeb-7c10-4b3c-8ca6-b23a44777266 to download the extension.

Using the Explorer:

The following screenshot shows the Team Explorer window when Release Explorer is installed.

In order for the explorer to work correctly, you will need to add in the Release Management Server details. Go to Options -> Release Explorer -> Settings. You should see this.

Now added in your server details. After that is complete, you can start using the explorer.

To use Release Explorer, simply click Releases. You will see your recent releases. The following screenshot shows an example.

From Release Explorer, you can select a particular deployment to see release steps and to see the deployment logs. You also can Restart, Abandon or Retry existing releases in the explorer. If you need to return to the Release Management Client, perhaps to fix some errors or to improve the orchestration, click Launch Release Management, under Releases. Check out below for more screenshots.

View release steps, log or restart a release.

Release Steps

I also added a Notifications window that allows you to keep track of what is happening with your releases. You can find it at View -> Other Windows -> Release Notifications

New Release Window: This window will allow you to create new vNext release based on you release template, build and current stage.

Select New Build Window. This window allows you to select from a range of builds to include into the release.

Let me know how the explorer is working. I hope this explorer helps you manage your dev/test release better.

Happy Coding!

John

Dev/Test with Microsoft Azure & Visual Studio 2013

John R. Spinella — Fri, 21 Nov 2014 09:30:00 GMT

So, I have been working a lot with customers on DevOps and one of the quick and easy way to achieve a Dev/Test environment is using Microsoft Azure and Visual Studio. This scenario applies broadly to every type of organization. Whether you’re a single developer or a one-person startup getting your mobile app out the door , or a multi-national enterprise with 100,000 + employees, you need a sandbox to build, test, and deploy. You also need a safe, isolated zone in which to do it with. You can count on Microsoft Windows Azure to quickly setup development labs for testing your apps, validating application behaviors, or using the environment for training, and teaching. Provisioning Virtual Machines can take minutes and gives you access to a isolated sandbox that your developers can use right away. Most dev, test, and lab environments are project-based and don’t need to be up and running 24/7. When you’re done, simply turn your virtual machines off. You pay for what you use and no more. How great is that!

Check out below how to setup you instance of Azure in Visual Studio.

1. Open Internet Explorer and navigate your Windows Azure portal developer site https://manage.windowsazure.com/
2. In the toolbar at the bottom, click on New | Compute | Virtual Machine | From Gallery Ok, for a change, let’s leave the server explorer aside for a moment, and take a look at the portal.
3. So, I’m going to create a new Virtual machine from our template gallery.

Note:

One of the cool features of Windows Azure is that it allows for a lot of scenarios related to development and test environments.
and the most flexible option for these scenarios are Virtual machines.

Windows Azure’s new IaaS and Virtual Networking capabilities make it really easy to enable enterprise development teams to use the cloud to do this. Using the cloud for dev/test enables development teams to work in a flexible, agile, way without ever being bottlenecked waiting for resources from their IT department. Development teams can instead use Windows Azure in a self-service way to spin up or down resources in minutes. And then when they are ready to deploy their apps, they can choose to do so either in the cloud or using their existing on-premises servers. This later option makes it really easy to start leveraging the cloud even without having to fully bet on it right away for production scenarios.

4. Click on SharePoint Server 2013 Trial
5. Click on next

Note:

We need to enter a unique site name, and choose the location, and database server that we want to use. In these case I’m going to create a new database.

The ASP.NET MVC application that I will deploy in the next few steps uses a database that I will deploy later.

6. Set the virtual server name
7. Set the user name and password
8. Click on Next

Note:

In step two of the wizard, I get to supply a name for my new Virtual Machine, select its size and complete a username and password to login to the machine.

Remember, the size of virtual machine here is crucial as it both selects the hardware that my virtual machine will run on, but also has a knock on impact to the amount deducted per minute from my Azure subscription.

9. Set the Cloud Service Name
10. Set the region and the storage account
11. Click on Next Step three has a few more fields to be completed. Firstly, in the cloud service field, I will create a new cloud service for my virtual machine. This option is available so that virtual machines can be grouped logically for purposes such as load balancing.

Note:

If you already have a storage account in the same data center, choose that, if not you can choose to “Use an automatically generated storage account”.

12. Click on Next

Note:

The final step allows us to specify the endpoint where we can communicate with our virtual machine. In my instance, the default settings used by Remote Desktop and PowerShell are suitable, so I can use either of these mechanisms to work with my VM.

With this all filled in automatically, we are all done with the wizard, so I can select the check mark at the bottom right of the screen to complete the wizard.

13. Wait until the virtual machine is created. This could take while.
14. When completed, Open Visual Studio

Note:

Virtual machine provisioning will take a few minutes, but once completed you will have an entry in your Virtual Machines section of the portal that you can select and connect to initiate a remote desktop session to your new virtual machine.

15. Open the Server Explorer in Visual Studio
16. Click on Virtual Machine node
(If the virtual machine does not appear click refresh)
17. Click on the new server (Virtual Machines now have context menu actions that allow you start, shutdown, restart, and delete a Virtual Machine directly within the Visual Studio Server Explorer.)

Note:

The shutdown action enables you to shut down the virtual machine and suspend billing when the VM is not in use, and easily restart it when you need it. When you stop a VM we no longer charge you any computing time for it – yet we still preserve the deployment state and configuration. This makes it incredibly easy to stop VMs when you aren’t actively using them to avoid billing charges, and then restart them when you want to use them again.

My next post will show you how to upload a website to the provisioned server and start testing it.

Happy Coding!

John

Modern DevOps Tools

John R. Spinella — Wed, 28 May 2014 14:34:00 GMT

Hey everyone,

Been awhile since I posted anything, been really busy. I just wanted to update everyone on a CodePlex project I have created with some of my co workers - Modern DevOps Tools. The site is based around building tools that uses recommended practices that will work inside of your continuous delivery cycle. Right now, I have up the DevOps Build Template that has all the goodies!

Assembly Versioning
Branch Specification
Code Analysis
- Cat.Net
- FxCop
- StyleCop
- Code Metrics
- SharePoint Dispose Check
Build Reports for Continuous Delivery
Email
Code Signing
Auto Deployments using DSC (Desired State Configuration) - Coming soon
Auto Deployments using RM (Release Management) - Coming soon - 2013 version
Quick Use Guide

TFS 2013 build template is coming soon! Please go check it out and provide feedback on the tools we have and any other tools you would like to see.

Thanks,

John

Channel 9 video - Introducing DevOps Workbench Express Edition for Visual Studio 2012

John R. Spinella — Thu, 03 Oct 2013 05:52:35 GMT

You can watch the full video here:

https://channel9.msdn.com/Blogs/VisualStudio/Introducing-Deployment-Workbench-Express-Edition

Interview:

Brian Keller interviews Casey O'Mara about another great Visual Studio Rangers project - DevOps Workbench Express Edition. This free tool available on Visual Studio Gallery, and Codeplex is designed to help small to medium teams manage their releases and push them from Team Foundation Server (or Team Foundation Service) directly into a dev/test/staging/production environment.

Download Guidance: https://aka.ms/vsardevops

Download DevOps Workbench Express Edition Tool: DevOps Workbench Express Edition

View YouTube videos: TFS2012 - DevOps Deployment Workbench Express Edition

Team Members

(in alphabetical order):
Anna Galaeva, Bijan Javidi, Bob Hardister, Casey O’Mara, David Pitcher, Ed Blankenship, Jahangeer Mohammed, John Bergman, John Spinella, Joseph Abukhader, Larry Guger, Ryan Frasier, Tony Feissle, Willy-Peter Schaub

DevOps Workbench Express Edition Release for Visual Studio 2012

John R. Spinella — Thu, 03 Oct 2013 05:48:00 GMT

The ALM Rangers currently released the DevOps Workbench Express Edition guidance to Codeplex (here) and the download to Visual Studio Gallery.

DevOps Deployment is based around build once, and deploy to multiple environments. DevOps Workbench Express Edition specifically targets the small organization with multiple personas. This will work inside of your continuous delivery cycle to provide business value, and agility.

The latest binary release can be found on Visual Studio Gallery, the guidance, and all code samples in the Codeplex Downloads section as well as a introduction video here.

Currently in scope:

DevOps Workbench Express Edition
DevOps Deployment Explorer
DevOps Workbench Hands-on-Labs
Guidance for Continuous Delivery
Quick Use Guide
DevOps Workbench Express Edition Poster

Templates included:

Azure Deployment
Website Deployment
SharePoint
Visual Studio SQL 2010 Database Projects
Visual Studio SQL 2012 Database Projects

...plus many other compositional deployment activities.

Visual Studio ALM Rangers

Big thanks to the team that delivered this:

Anna Galaeva, Bijan Javidi, Bob Hardister, Casey O’Mara, David Pitcher, Ed Blankenship, Jahangeer Mohammed, John Bergman, John Spinella, Joseph Abukhader, Larry Guger, Ryan Frasier, Tony Feissle, Willy-Peter Schaub

This guidance is created by the Visual Studio ALM Rangers, who have the mission to provide out of band solutions for missing features and/or guidance. This content was created with support from Microsoft Product Group, members of Microsoft Services, Microsoft Most Valued Professionals (MVPs) and technical specialists from technology communities around the globe, giving you a real-world view from the field, where the technology has been tested and used.

Targeted for Visual Studio 2012 – DevOps Deployment Workbench Express Edition

John R. Spinella — Thu, 03 Oct 2013 05:44:34 GMT

New Video posted today by my good friend and team mate on YouTube about the DevOps Workbench Express Edition and how to do your very own custom deployment. Casey and I will be doing several more, and interviewing people from the team on how to use the Workbench for everyday deployments, and even going into more detail around build and continuous delivery all the way to continuous testing!!

Stay tuned for more great videos. I’d also love to see your suggestions, comments, and other feedback!

You can get the solution and guidance here: https://vsarDevOps.codeplex.com or at the Visual Studio Gallery.

[View:https://www.youtube.com/watch?v=_sc8BbEpSq4&feature=youtube_gdata_player]

Happy Coding,

John

BRDLite V2.0 is Released to the Public!

John R. Spinella — Thu, 21 Feb 2013 05:36:00 GMT

After a few weeks of silent ship, which did not reveal any showstoppers, we would like to announce the
general availability of BRDLite on Codeplex. Kudos to John Jacob and Myself, the co-leads of the project, and the team, for this achievement which is especially important for our future ambitions in this area. It is a stepping stone to our DevOps future.

Please help us spread the news by blogging. Use this email as a starting point or refer to the Rangers blog.

Project Description

The Build Release and Deploy (BRD) Lite is a set of build process reference templates that allows you to quickly setup a real-world build process in your environment. It leverages extensions from Community TFS Build Extensions, which provide capabilities for your Team Foundation builds such as automatic compile, build version number customization, build packaging, code signing, basic deployment functionality, and environment configuration file management into your Team Foundation builds.

The “Lite” comes from a build template that you or your Build administrators can use “out of the box” for most scenarios. Of course, you can always customize and extend as needed.

Epics

As Abu, the build master, I would like a number of BRDLite reference templates, which implement scenario based custom activities
As Abu, the build master, I need guidance on extending the BRDLite reference template with new custom activities
As Abu, the build master, I would like to understand the changes and impact of Visual Studio 2012 on BRDLite

Team

Bijan Javidi, Brandon Hawbaker, Jim Lamb, John Jacob, John Spinella, Mike Fourie, Richard Fennell, William Bartholomew, Willy-Peter Schaub

Future plans

BRDLite is our 1^st investment in DevOps domain which is one of our focus areas in future. Actually, with the announcement of Rangers FY13 triage #3 a couple of weeks ago, the future has already started. DevOps is the new Ranger project which extends BRDLite to the next level. As usual, it is the Rangers way of converting hype and buzz into pragmatic hands-on solutions.

Stay tuned!

Happy Coding!

John

Using ReverseGeocodeQuery for Windows Phone 8

John R. Spinella — Fri, 02 Nov 2012 08:39:00 GMT

So, I started writing some of my apps I had for Android and WP7 for Windows Phone 8 and to my surprise Nokia Maps are looking to be a really good thing. With the New Nokia Maps, there are Maps services that come with the Windows Phone 8 SDK. One in particular is ReverseGeocodeQuery. This is great as I can use my internal map to get geocoding without having to reference any of the Bing Services. Now, if you want more of the Bing services like Search, Live API, ect. then BIng Services API is the way to go. For my example I will show you how to use the ReverseGeocodeQuery and fill in a textblock with a address of where I am.

Building the Sample Phone Project in Visual Studio 2012

First thing you want to do is open Visual Studio 2012 and create a new windows phone project. We are going to name it "ReverseGeocodeQueryPhoneApp" and you will want to pick Windows Phone 8.0 SDK.

Next, you should see Visual Studio creating your project and you should see below.

Now, with the MainPage.xaml open, add in the code below to the main content grid.

Open the code behind and Add in the reference code below.

public partial class MainPage : PhoneApplicationPage
{
 // Progress indicator shown in system tray
 private ProgressIndicator ProgressIndicator = null;
 
 // My current location
 private GeoCoordinate MyCoordinate = null;
 
 // Reverse geocode query
 private ReverseGeocodeQuery MyReverseGeocodeQuery = null;
 
 /// 
 /// Accuracy of my current location in meters;
 /// 

 private double _accuracy = 0.0;
 
 // Constructor
 public MainPage()
 {
 InitializeComponent();
 GetCurrentCoordinate();
 } 
 
 /// 
 /// Method to get current coordinate asynchronously so that the UI thread is not blocked. Updates MyCoordinate.
 /// Using Location API requires ID_CAP_LOCATION capability to be included in the Application manifest file.
 /// 

 private async void GetCurrentCoordinate()
 {
 Geolocator geolocator = new Geolocator();
 geolocator.DesiredAccuracy = PositionAccuracy.High;
 
 try
 {
 Geoposition currentPosition = await geolocator.GetGeopositionAsync(TimeSpan.FromMinutes(1), TimeSpan.FromSeconds(10));
 _accuracy = currentPosition.Coordinate.Accuracy;
 
 MyCoordinate = new GeoCoordinate(currentPosition.Coordinate.Latitude, currentPosition.Coordinate.Longitude);
 
 if (MyReverseGeocodeQuery == null || !MyReverseGeocodeQuery.IsBusy)
 {
 MyReverseGeocodeQuery = new ReverseGeocodeQuery();
 MyReverseGeocodeQuery.GeoCoordinate = new GeoCoordinate(MyCoordinate.Latitude, MyCoordinate.Longitude);
 MyReverseGeocodeQuery.QueryCompleted += ReverseGeocodeQuery_QueryCompleted;
 MyReverseGeocodeQuery.QueryAsync();
 }
 
 }
 catch (Exception ex)
 {
 ...
 }
 
 }
 
 /// 
 /// Event handler for reverse geocode query.
 /// 

 /// Results of the reverse geocode query - list of locations
 private void ReverseGeocodeQuery_QueryCompleted(object sender, QueryCompletedEventArgs> e)
 {
 if (e.Error == null)
 {
 if (e.Result.Count > 0)
 {
 MapAddress address = e.Result[0].Information.Address;
 CurrentLocTextBlock.Text = "Current Location: " + address.City + ", " + address.State;
 } 
 }
 } 
 }

Remember to check ID_CAP_Location and ID_CAP_Map in the Capabilities section of the Windows Manifest. if you don't you will get a Access Denied Error.

Now you are set to debug your work, below is what should be displaying in the emulator.

I hope you found the post useful. As I come across more great things in Windows Phone 8 development (I am sure I will). I will pass it along to you all.

Happy Coding!!

Thanks,

John