WPF-Blogger.com [Language: en]

12 Absolutely and Insanely Essential Utilities For Programmers

Jesse Liberty [MS] — 2010-07-30T06:45:01

In every era in recent times there has been one profession that for a short while you could enter without formal training. Autodidacts in the 19th century could read the law without recourse to formal education (see Abe Lincoln). In the early 20th century it was aviation. For a short while in the 1980s and [...]

Announcing 2nd CTP of XAML Toolkit

Lester Lobo — 2010-07-30T04:13:00

We are happy to announce the release of the second CTP of the XAMLToolkit. Where do i get it: LINK The toolkit comprises of: A XAML DOM Fxcop rule authoring support for XAML SilverlightSchemaContext that enables System.Xaml to parse SL XAML. We greatly...(read more)

One From The Vault: Ranting About Editors

Jesse Liberty [MS] — 2010-07-26T03:37:38

This week’s One From The Vault is a rant on arbitrary and incorrect “rules” of English insisted upon by some teachers, editors and pedants: There is no excuse for thinking that you can’t start a sentence with “There is.” And I should add that I think it is fine to start a sentence with “and.” [...]

Portland Silverlight User Group 10 Aug 2010

Karl Shifflett [MS] — 2010-07-25T21:38:37

On 10 Aug 2010, Adam Kinney and I will be presenting at the Portland Silverlight User Group. As you know I work on the WPF & Silverlight Designer in Visual Studio as part of the Expression Team. This session will provide guidance for writing applications that are toolable. Many folks use the term, Blendable. Do [...]

Data Validation And Templating in Silverlight 4

Jesse Liberty [MS] — 2010-07-25T21:26:52

This is the fifth in a series on Templates and DataValidation. [ First In Series Previous In Series ] In this and the next posting I will create an application that will demonstrate how to modify the Visual State for invalid data. Along the way we will review: Binding form elements to data The binding [...]

Video recordings for first Windows Phone 7 Jumpstart event

Jaime Rodriguez [MS] — 2010-07-23T21:17:00

This week, MS learning did the first delivery of our Windows Phone 7 Jumpstart training.

The JumpStart is a four part deep-dive into Windows Phone. The four sessions included:

An Introduction to the Windows Phone Platform
Game Building on the Windows Phone Platform
Advanced Windows Phone Development
Selling Your Windows Phone Solutions & Wrap Up

The reviews for the event were awesome. Thousands of people attended. Everybody liked the presenters and the content.

You can download all the content for the JumpStart from this MS Learning Website.

Below you can find links to the video recordings.
The recordings a little raw, they are captures of the sessions without edits, but the videos are great for learning Windows phone, they go through fast, and are a must-see companion to the demos and ppts..

If you missed out, on these great sessions check the MS Learning blog next month. I hear the events will be repeated often.

Session one: Intro to the series and intro to Windows Phone platform:

Session Two: Game building on Windows phone

Session Three: Advanced Windows Phone development ( life cycle, state management, push, etc.. )

Session four: Selling your Windows Phone solution ( marketplace, A

Happy Windows Phone coding..

Events and Delegates Under The Hood – Q&A

Jesse Liberty [MS] — 2010-07-19T22:55:35

In the comments from this morning’s post, Andrew raised two questions important enough that I wanted to answer them in a post, rather than in comments…. [In the original version of the posting] you had some code showing that you could use “=” with delegates but that you’d get a compile time error with the [...]

Events and Delegates Under The Hood – Reposted

Jesse Liberty [MS] — 2010-07-19T19:13:16

Many programmers come to Silverlight with little prior experience with C#, and thus conceptualize events as a response to an action that is “hooked up” using somewhat arbitrary syntax. All of that is fine, until it isn’t, and so this post will dive a bit deeper into Delegates and Events as core aspects of .Net [...]

Events and Delegates Under The Hood

Jesse Liberty [MS] — 2010-07-19T06:12:55

Teaching An Old Control New Tricks With Templates

Jesse Liberty [MS] — 2010-07-18T06:31:39

This is the fourth in a short series on Templates and DataValidation. [ First In Series Previous In Series ] You will remember that in the previous post in this small series, we created a new button template with a new appearance and new behavior for the “standard” view states. This button will be used [...]

The Great Much More Signal, Much Less Noise Challenge of 2010

Jesse Liberty [MS] — 2010-07-17T19:59:37

Starting today and running through the end of the year, I am challenging myself to post at least one useful, interesting or worthwhile entry every single day – (Yikes!) You are the judges. I will measure my success/failure on visits, pageviews and subscribers I’ve also added per-post ratings so that you can indicate what you [...]

Portland .NET User Group 3 Aug 2010 + Mole 2010

Karl Shifflett [MS] — 2010-07-17T04:29:28

I’m very excited to announce that I’ll be speaking at the Portland .NET User Group on 3 Aug 2010. This will be my first time visiting Portland and I’m looking forward to it! This wide open night will close out with the first time unveiling of Mole 2010. Line of Business for WPF Departing from [...]

The Disasters of Visual Design Tools

Charles Petzold — 2010-07-16T12:26:00

Many years ago — about the time that visual design tools were being introduced into our programming environments — I promised that I would never believe myself to be teaching programming if I were writing sentences like "Now drag the Button from the toolbox to the window." I am proud to say I have kept to that promise.

... more ...

Templates, Visual State and Fun With Controls

Jesse Liberty [MS] — 2010-07-15T20:41:59

This is the third (if you count Sunday’s update!) in my short series on Templates and Data Validation. [ First In Series. Previous In Series ] Today we’re going to create a templated Button that changes the appearance and visual state behavior of the button. Changing the visual state behavior in this case means responding [...]

Manipulation Events Update for the WP7 Beta

Charles Petzold — 2010-07-14T20:07:57

Always start with the good news: The good news is that the Manipulation events in the July beta of the Windows Phone 7 development tools no longer have the orientation problem I discussed in my blog entry Basic Manipulation Event Handling in Windows Phone 7 (at least with translation). You can flip the phone emulator sideways and translation coordinates don't need to be finagled. More good news: I am now able to get the emulator to recognize two fingers on my two touch screens, so I've been able to experiment with scaling as well as translation.

... more ...

Windows Phone 7 Development Tools Now in Beta

Charles Petzold — 2010-07-13T22:41:11

As of yesterday, Windows Phone 7 is in beta, which means there are updated development tools to be downloaded and installed.

... more ...

Tips for uninstalling the Windows Phone Developer Tools CTPs and moving to beta

Jaime Rodriguez [MS] — 2010-07-13T21:19:19

To install the Windows Phone Developer Tools beta, you will first need to uninstall the older CTP (if you had it installed).

The process is straight forward if you get the order right and don’t have other pre-release bits installed. All this means is

You should uninstall the item named Microsoft Windows Phone Developer Tools CTP – ENU. That will chain the uninstall of other components.

If you do run into issues (or you are reading this and already uninstalled in wrong order), the following blog posts have workarounds to the most common errors you will run into:

You are trying to uninstall, but the software first wants to install something that is or was already installed.
Check this post
You are getting an error installing the beta, need tips to check for incompatible components. Check this post
Your install failed in the middle, or you have uninstalled components out of order and you need some brute force uninstaller. Try this post

I hope that does it; if not please try the Windows Phone forums. You can also email me, but responses are much more delayed than at the forums; we have a great team monitoring the forums.

Happy Windows Phone coding.

Awarded Silverlight Cream’s Best Blog Post of 2010

Jesse Liberty [MS] — 2010-07-13T16:58:12

I’m incredibly proud that Silverlight Cream (required reading for anyone interested in Silverlight) rated one of my blog posts #1 for 2010. The pride results only from the fact that Dave does such an incredible job every day culling the very best posts in the Silverlight eco-system.

New Video: Introduction to Xaml

Jesse Liberty [MS] — 2010-07-13T16:32:36

In my new video An Introduction To Xaml, I recreate the form used in Adding Controls To An Application, but this time using Xaml rather than drag and drop. Part of the ongoing video series: Getting Started With Silverlight. [30]

Getting Request.Form Data Out of XDomainRequest In ASP.NET

Karsten Januszewski [MS] — 2010-07-13T03:34:00

I am using the XDomainRequest object in IE8 and IE9 to do cross domain posting. However, I hit an issue where I couldn't seem to get at the data I was posting: the Request.Form collection contained nothing yet I was clearly sending it. I then found this post:

http://blogs.msdn.com/b/ieinternals/archive/2010/05/13/xdomainrequest-restrictions-limitations-and-workarounds.aspx

which states: "we restricted the content type to text/plain but didn’t allow the caller to specify that the data was in application/x-www-urlencoded form. This is problematic because server-side frameworks (e.g. ASP, ASPNET, etc) will only automatically parse a request’s fields into name-value pairs if the x-www-urlencoded content type is specified.

To workaround this issue, server code that currently processes HTML Forms must be rewritten to manually parse the request body into name-value pairs when receiving requests from XDomainRequest objects. This makes adding support for the XDomainRequest object more difficult than it would be otherwise."

Okay, so how does one do that? Well, turned to be pretty simple. I just had to access the Request.InputStream directly, as follows:

//set the header to support XDomainRequest

Response.Headers.Add("Access-Control-Allow-Origin", "*");

//now extract the data out of the stream

System.IO.Stream str;

String jsonContents;

Int32 counter, strLen, strRead;

// Create a Stream object.

str = Request.InputStream;

// Find number of bytes in stream.

strLen = Convert.ToInt32(str.Length);

// Create a byte array.

byte[] byteArray = new byte[strLen];

// Read stream into byte array.

strRead = str.Read(byteArray, 0, strLen);

// Convert byte array to a text string.

jsonContents = Encoding.UTF8.GetString(byteArray);

Eulogy

Jesse Liberty [MS] — 2010-07-11T20:56:34

The following is from the eulogy I gave for my mother in law. Posted here in the hope you might find some of it valuable. Speak no ill of the dead. It used to make me crazy to sit at a memorial service and listen to the Rabbi who had never met my father… or [...]

Styles (followup)

Jesse Liberty [MS] — 2010-07-11T07:22:16

Yesterday’s post did not include source, and left fleshing out the styles as an exercise… this quick follow-up will provide a link to the full code and a quick walkthrough of the styles I ended up creating. The tricky part is that there is not a single base class for the various controls we’re using [...]

Visual State Manager A-Z

Jesse Liberty [MS] — 2010-07-10T04:03:13

This is the first of a multipart series on the Visual State Manager which will cover Styles Resources Templates Custom Controls Customizing data validation Let’s start with the form that is used in my Getting Started With Silverlight video: Adding Controls To An Application. That video uses the design surface in Visual Studio 2010, and [...]

Serializing Request.ServerVariables to JSON: JavaScriptSerializer vs. DataContractJsonSerializer

Karsten Januszewski [MS] — 2010-07-07T21:06:00

I needed to serialize Request.ServerVariables to JSON. I tried both JavaScriptSerializer nor DataContractJsonSerializer without any luck. But I thought both would work, as Request.ServerVariables is of type NameValueCollection and the docs on MSDN state that both serialization engines support dictionaries. The solution? Convert (manually) the NameValueCollection into a dictionary.

Here's the code:

            Dictionary<string,string> d = new Dictionary<string,string>();
            foreach (string s in Request.ServerVariables.AllKeys)
            {
                d.Add(s, Request.ServerVariables[s]);
            }
            //DataContractJsonSerializer
            DataContractJsonSerializer serverVariablesSerializer = new DataContractJsonSerializer(typeof(Dictionary<string,string>));
            MemoryStream ms = new MemoryStream();
            serverVariablesSerializer.WriteObject(ms, d);
            string json = Encoding.Default.GetString(ms.ToArray());
            Debug.WriteLine(json);
            //JavaScriptSerializer
            JavaScriptSerializer serverVariablesSerializer2 = new JavaScriptSerializer();
            string json2 = serverVariablesSerializer2.Serialize(d);
            Debug.WriteLine(json2);

What's interesting is that the output is different between the two serialization engines. JavaScriptSerializer is smart enough to turn the key into the key in JSON, whereas DataContractJsonSerializer creates a key called "key" with the value of the key and then a key called "value" with the value of the value. Kind of annoying. The winner? JavaScriptSerializer

Here's the output BTW:

DataContractJsonSerializer: [{"Key":"ALL_HTTP","Value":"HTTP_CONNECTION:Keep-Alive\u000d\u000aHTTP_ACCEPT:*\/*\u000d\u000aHTTP_ACCEPT_ENCODING:gzip, deflate\u000d\u000aHTTP_ACCEPT_LANGUAGE:en-us\u000d\u000aHTTP_COOKIE:comment=name=b&email=b@b.com&url=&country=us; WT_FPC=id=71.231.143.146-177222816.30061129:lv=1277910617997:ss=1277910147666\u000d\u000aHTTP_HOST:localhost:4135\u000d\u000aHTTP_USER_AGENT:Mozilla\/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident\/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; MS-RTC LM 8; .NET4.0C; .NET4.0E)\u000d\u000a"},{"Key":"ALL_RAW","Value":"Connection: Keep-Alive\u000d\u000aAccept: *\/*\u000d\u000aAccept-Encoding: gzip, deflate\u000d\u000aAccept-Language: en-us\u000d\u000aCookie: comment=name=b&email=b@b.com&url=&country=us; WT_FPC=id=71.231.143.146-177222816.30061129:lv=1277910617997:ss=1277910147666\u000d\u000aHost: localhost:4135\u000d\u000aUser-Agent: Mozilla\/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident\/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; MS-RTC LM 8; .NET4.0C; .NET4.0E)\u000d\u000a"},{"Key":"APPL_MD_PATH","Value":""},{"Key":"APPL_PHYSICAL_PATH","Value":"C:\\stuff\\WebApplication1\\WebApplication1\\"},{"Key":"AUTH_TYPE","Value":"NTLM"},{"Key":"AUTH_USER","Value":"REDMOND\\karstenj"},{"Key":"AUTH_PASSWORD","Value":""},{"Key":"LOGON_USER","Value":"REDMOND\\karstenj"},{"Key":"REMOTE_USER","Value":"REDMOND\\karstenj"},{"Key":"CERT_COOKIE","Value":""},{"Key":"CERT_FLAGS","Value":""},{"Key":"CERT_ISSUER","Value":""},{"Key":"CERT_KEYSIZE","Value":""},{"Key":"CERT_SECRETKEYSIZE","Value":""},{"Key":"CERT_SERIALNUMBER","Value":""},{"Key":"CERT_SERVER_ISSUER","Value":""},{"Key":"CERT_SERVER_SUBJECT","Value":""},{"Key":"CERT_SUBJECT","Value":""},{"Key":"CONTENT_LENGTH","Value":"0"},{"Key":"CONTENT_TYPE","Value":""},{"Key":"GATEWAY_INTERFACE","Value":""},{"Key":"HTTPS","Value":""},{"Key":"HTTPS_KEYSIZE","Value":""},{"Key":"HTTPS_SECRETKEYSIZE","Value":""},{"Key":"HTTPS_SERVER_ISSUER","Value":""},{"Key":"HTTPS_SERVER_SUBJECT","Value":""},{"Key":"INSTANCE_ID","Value":""},{"Key":"INSTANCE_META_PATH","Value":""},{"Key":"LOCAL_ADDR","Value":"127.0.0.1"},{"Key":"PATH_INFO","Value":"\/Default.aspx"},{"Key":"PATH_TRANSLATED","Value":"C:\\stuff\\WebApplication1\\WebApplication1\\Default.aspx"},{"Key":"QUERY_STRING","Value":""},{"Key":"REMOTE_ADDR","Value":"127.0.0.1"},{"Key":"REMOTE_HOST","Value":"127.0.0.1"},{"Key":"REMOTE_PORT","Value":""},{"Key":"REQUEST_METHOD","Value":"GET"},{"Key":"SCRIPT_NAME","Value":"\/Default.aspx"},{"Key":"SERVER_NAME","Value":"localhost"},{"Key":"SERVER_PORT","Value":"4135"},{"Key":"SERVER_PORT_SECURE","Value":"0"},{"Key":"SERVER_PROTOCOL","Value":"HTTP\/1.1"},{"Key":"SERVER_SOFTWARE","Value":""},{"Key":"URL","Value":"\/Default.aspx"},{"Key":"HTTP_CONNECTION","Value":"Keep-Alive"},{"Key":"HTTP_ACCEPT","Value":"*\/*"},{"Key":"HTTP_ACCEPT_ENCODING","Value":"gzip, deflate"},{"Key":"HTTP_ACCEPT_LANGUAGE","Value":"en-us"},{"Key":"HTTP_COOKIE","Value":"comment=name=b&email=b@b.com&url=&country=us; WT_FPC=id=71.231.143.146-177222816.30061129:lv=1277910617997:ss=1277910147666"},{"Key":"HTTP_HOST","Value":"localhost:4135"},{"Key":"HTTP_USER_AGENT","Value":"Mozilla\/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident\/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; MS-RTC LM 8; .NET4.0C; .NET4.0E)"}]

JavaScriptSerializer: {"ALL_HTTP":"HTTP_CONNECTION:Keep-Alive\r\nHTTP_ACCEPT:*/*\r\nHTTP_ACCEPT_ENCODING:gzip, deflate\r\nHTTP_ACCEPT_LANGUAGE:en-us\r\nHTTP_COOKIE:comment=name=b&email=b@b.com&url=&country=us; WT_FPC=id=71.231.143.146-177222816.30061129:lv=1277910617997:ss=1277910147666\r\nHTTP_HOST:localhost:4135\r\nHTTP_USER_AGENT:Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; MS-RTC LM 8; .NET4.0C; .NET4.0E)\r\n","ALL_RAW":"Connection: Keep-Alive\r\nAccept: */*\r\nAccept-Encoding: gzip, deflate\r\nAccept-Language: en-us\r\nCookie: comment=name=b&email=b@b.com&url=&country=us; WT_FPC=id=71.231.143.146-177222816.30061129:lv=1277910617997:ss=1277910147666\r\nHost: localhost:4135\r\nUser-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; MS-RTC LM 8; .NET4.0C; .NET4.0E)\r\n","APPL_MD_PATH":"","APPL_PHYSICAL_PATH":"C:\\stuff\\WebApplication1\\WebApplication1\\","AUTH_TYPE":"NTLM","AUTH_USER":"REDMOND\\karstenj","AUTH_PASSWORD":"","LOGON_USER":"REDMOND\\karstenj","REMOTE_USER":"REDMOND\\karstenj","CERT_COOKIE":"","CERT_FLAGS":"","CERT_ISSUER":"","CERT_KEYSIZE":"","CERT_SECRETKEYSIZE":"","CERT_SERIALNUMBER":"","CERT_SERVER_ISSUER":"","CERT_SERVER_SUBJECT":"","CERT_SUBJECT":"","CONTENT_LENGTH":"0","CONTENT_TYPE":"","GATEWAY_INTERFACE":"","HTTPS":"","HTTPS_KEYSIZE":"","HTTPS_SECRETKEYSIZE":"","HTTPS_SERVER_ISSUER":"","HTTPS_SERVER_SUBJECT":"","INSTANCE_ID":"","INSTANCE_META_PATH":"","LOCAL_ADDR":"127.0.0.1","PATH_INFO":"/Default.aspx","PATH_TRANSLATED":"C:\\stuff\\WebApplication1\\WebApplication1\\Default.aspx","QUERY_STRING":"","REMOTE_ADDR":"127.0.0.1","REMOTE_HOST":"127.0.0.1","REMOTE_PORT":"","REQUEST_METHOD":"GET","SCRIPT_NAME":"/Default.aspx","SERVER_NAME":"localhost","SERVER_PORT":"4135","SERVER_PORT_SECURE":"0","SERVER_PROTOCOL":"HTTP/1.1","SERVER_SOFTWARE":"","URL":"/Default.aspx","HTTP_CONNECTION":"Keep-Alive","HTTP_ACCEPT":"*/*","HTTP_ACCEPT_ENCODING":"gzip, deflate","HTTP_ACCEPT_LANGUAGE":"en-us","HTTP_COOKIE":"comment=name=b&email=b@b.com&url=&country=us; WT_FPC=id=71.231.143.146-177222816.30061129:lv=1277910617997:ss=1277910147666","HTTP_HOST":"localhost:4135","HTTP_USER_AGENT":"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; MS-RTC LM 8; .NET4.0C; .NET4.0E)"}

Non-Linear Navigation in Silverlight 4

Karl Shifflett [MS] — 2010-07-07T19:25:00

In the last Seattle Silverlight User Group meeting I spoke about Non-Linear Navigation in Silverlight. This blog post is a proof-of-concept for Non-Linear Navigation in Silverlight 4 Navigation Applications. When I was first exploring this, I did not use the Navigation Application template, instead I implemented Non-Linear Navigation similar to what I did in BBQ [...]

XAML Compliance Suite V1

Lester Lobo — 2010-07-07T15:28:00

Generally, when theres an open spec format, theres usually a set of tests that ensure that the spec is being followed right. As as example, the Acid tests help in deterning the support of web standards in different web browsers. So when it came to XAML, we decided that we should have a basic set of tests that can be used to determine whether the parser implementation is compliant with the XAML spec. You can find the latest XAML spec at (LINK)

So here we have it, V1 of the XAML Compliance suite of tests. The suite consists of two parts: a custom type library and a collection of xaml files that use those types. The types are self verifiable - so using the library would need users to have a simple function that exercises their parser with the xaml files. A simple loader for the System.Xaml parser is included in the project as a sample. Since the types are CLR based they can easily be used with other parsers without needing a dependency on WPF.

The sample loader has the following usage:

Usage: SystemXamlLoader.exe XamlFileRepositoryPath TypesDll LogOnlyFailures
        XamlFileRepositoryPath: Path to directory of test xaml files
        TypesDll: Dll containing custom types to load.
        LogOnlyFailures: True|False. Defaults to True

E.g: SystemXamlLoader.exe Xaml Xaml.Test.dll false

The zipped up suite is attached

Share this post

XAML Power Toys for Visual Studio 2010 for Cider version 2.1 Silverlight 4 Support

Karl Shifflett [MS] — 2010-07-07T12:51:09

I have just updated XAML Power Toys for Visual Studio 2010 for Cider to version 2.1 adding support for Silverlight 4. Please Note I have two XAML Power Toys products on my blog. They are not the same. Get both, you’ll be glad you did. The first one is for working in the XAML Editor [...]

XAML Power Toys for Visual Studio 2010 version 6.1 Silverlight 4 Support

Karl Shifflett [MS] — 2010-07-07T11:28:28

I have just updated XAML Power Toys for Visual Studio 2010 to version 6.1 adding support for Silverlight 4. New Features and Fixes Added support for Silverlight 4 Corrected ViewModel creator spit If you remove the CommandParameter type in the Command Creation Window, the spit will no longer add the CommandParameter type to the RelayCommand [...]

Using Stringify With the New window.msPerformance in Internet Explorer 9

Karsten Januszewski [MS] — 2010-07-06T21:29:00

I've been playing with the new window.msPerformance that's part of IE9 as explained in this blog post: http://blogs.msdn.com/b/ie/archive/2010/06/28/measuring-web-page-performance.aspx. Of course, the main thing you want to do is capture this data. The blog post mentions that you can use the stringify method to serialize the object to JSON and then send the diagnostics back to the server. Well, I tried this with no luck. Here's what my code looked like:

                var json = JSON.stringify(window.msPerformance.timing);
                alert(window.msPerformance.timing);
                alert(json);
            }
        }
</script>

Even though the performance object was populated, the serialization to JSON failed.

I did some digging around and learned that the native JSON method in IE9 doesn't successfully stringify native objects, like anything hanging off window or document. However, I was able to work around this by using Crockford's JSON class from here: http://www.json.org/js.html. The one thing I had to do was to change the prototype to JSON2 so that the browser's native JSON prototype wasn't called. Then it worked!

Sample Data in the WPF and Silverlight Designer

Karl Shifflett [MS] — 2010-07-01T03:55:57

I just posted a comprehensive article on Sample Data in the Visual Studio 2010 WPF and Silverlight Designer here. This article is scenario based and fully explains sample data in WPF and Silverlight. It includes code sample in C# and VB.NET. Have a great day, Just a grain of sand on the worlds beaches. Filed [...]

For Wendy Friedlander

Charles Petzold — 2010-06-30T21:29:20

Two summers ago I was working three days a week on a large WPF application at a company in New York City, and that's where I met Wendy Friedlander. Wendy brought several important skills to the project. Whereas I functioned as little more than a coder, Wendy revealed herself as a talented WPF programmer and much more besides. Her extensive practical experience in agile development practices, pair programming, and test-driven development helped the project enormously, and introduced me to modern team development strategies. Wendy was also one of the friendliest people I'd ever met and a joy to work with.

... more ...

Seattle Silverlight User Group – Windows Phone 7 Summer Series

Karl Shifflett [MS] — 2010-06-30T07:34:21

The Seattle Silverlight User Group meets at the Redmond Campus building 40/41 Cafeteria the first Wednesday of every month. On Wednesday, 7 July we begin the Summer Series on Windows Phone 7. With the help of Jaime Rodriquez and other Microsoft folks we will be getting down and dirty with Windows Phone 7 and getting [...]

PivotViewer Released!

Jesse Liberty [MS] — 2010-06-29T23:27:06

Run, do not walk to Pete Brown’s blog and read about the new PivotViewer control. This is a very cool control just released by LiveLabs and that is fully supported in the new PivotViewer learning section on Silverlight.net. The home page provides links to the code you need, three overview videos and, at the bottom [...]

Migrating apps from Windows Phone April CTP Refresh to the beta build

Jaime Rodriguez [MS] — 2010-06-28T20:00:00

There were a good number of breaking changes and new features introduced in the “beta” release of the Windows Phone Developer Tools.
Going forward from beta to RTM; the number of breaking changes will be minimal, so let’s just “buckle up” and migrate our code this once.
The migration is a lot easier than it sounds. I will first walk through the obvious breaking changes that the compiler will catch, and then share tips and workarounds in some of that ‘missing’ stuff that the compiler will miss.
Once you have gotten through this, don’t forget to read my post on the new features in the beta release so you can start taking advantage of these.

Breaking changes:

Namespaces and assembly changes:
The following assemblies were removed, and merged into a single “Microsoft.Phone” assembly:
Microsoft.Phone.Controls
Microsoft.Phone.Controls.Navigation
Microsoft.Phone.Controls.WebBrowser
Microsoft.Phone.Controls.WebBrowserInterop
Microsoft.Phone.Shell
Microsoft.Phone.Notification
Microsoft.Phone.Execution
Microsoft.Phone.Info
Microsoft.Phone.Tasks
Microsoft.Devices
To fix: change all your project references and all your namespaces declarations (xmlns) in XAML. See MigrationTips.1 below for details on namespaces.
System.Device.Location assembly was merged into System.Device assembly
To fix: change assembly references that were pointing to System.Device.Location and point them to System.Device assembly.
Microsoft.Devices assembly was removed; the classes in this assembly were moved to Microsoft.Phone assembly. Some of the classes changed namespaces, but not all.
To fix: change assembly references and reference Microsoft.Phone assembly.
Application.Resources have been removed from App.xaml and templates have been changed
To fix: you will need to remove these from your own App.xaml. Can’t leave them in because it would break theming; also, there are breaking changes (controls removed) that would prevent your app from running if you do not get rid of the resources. See below on MigrationTips.2 for details on what to remove and how.
ToggleControlSwitch and ToggleControlButton have been removed.
To fix: You should use ToggleButton and copy the template from RC version of ToggleControlSwitch. You will then need to add the touch gesture. Wait for a sample for this. I will post one soon.
ListView and ListView Item were removed
To fix: Use ListBox and a Template that matches the old ListViewItem template.
Effects have been removed from the platform, this will be plan of record for v1 (the feature might come back later).
In earlier builds, we had DropShadow, and Blur bitmap effects. Unfortunately, these have been removed.
Right now, your XAML is not breaking, but the usage of the effects is turning into a no-op.

To fix: You should just remove the references to effects from XAML and code. You can use graphics (e.g. gradients for dropshadows) to try to get similar look & feel. Not exactly the same, but best workaround I can think of until Microsoft brings these back in a future version of the platform.

A few classes were renamed or moved namespaces:

Type	Old	New	New assembly (if changed)
namespace	Microsoft.Devices.NetworkInformation	Microsoft.Phone.Net.NetworkInformation	Microsoft.Phone.dll
namespace	Microsoft.Phone.License	Microsoft.Phone.Marketplace	Microsoft.Phone.dll
class	Microsoft.Phone.Controls.NavigatedEventArgs	System.Windows.Navigation.NavigationEventArgs	System.Windows.dll
class	Microsoft.Phone.Navigation.PhoneNavigationEventArgs	System.Windows.Navigation.NavigationEventArgs	System.Windows.dll
class	AccelerometerSensor	Accelerometer
class	AccelerometerReadingAsyncEventArgs	AccelerometerReadingEventArgs
class	AccelerometerStartFailedException	AccelerometerFailedException
class	WindowsPhoneEvents	Microsoft.Phone.Shell.PhoneApplicationService	Microsoft.Phone.dll
class	Microsoft.Phone.License.LicenseInfo	Microsoft.Phone.Marketplace.LicenseInformation	Microsoft.Phone.dll
enum	Microsoft.Phone.Shell.DownloadInterval	Microsoft.Phone.Shell.UpdateInterval	Microsoft.Phone.dll
enum	Microsoft.Phone.Shell.DownloadRecurrence	Microsoft.Phone.Shell.UpdateRecurrence	Microsoft.Phone.dll
class	NotificationChannelExceptionEventArgs	NotificationChannelErrorEventArgs	Microsoft.Phone.dll

To fix: simply replace the namespace and/or class name and reference the new assembly (if applicable)

Minor changes were made to the WMAppManifest.xml file
1. XNA projects used to have an PlaceHolderString="Default task" on the WMAppManifiest.xml this XML attribute is not longer valid.
  Fix: remove the attribute from manifest. .
2. In the App element, the Genre attribute changed from NormalApp to Apps.Normal
3. In the App element, the RuntimeType attribute changed from SilverLight to Silverlight. {notice the case difference on the L}
System.Reactive namespace was moved to Microsoft.Phone.Reactive and there is a new assembly called Microsoft.Phone.Reactive.dll
The System.Concurrency and System.Disposable namespaces are now on this assembly.
Removed ManipulationCompletedEventArgs.IsTapEvent property
To fix: remove references to the property. You can use OnClick handlers.
Choosers API are no longer returning on OnChooserReturn; they now have instance based events.
The PhoneNumberChooserTask and PhotoChooserTask used to always return on an override on the Page hosting. They now have events that the task exposes and you can add the handler and listen to the return from any class you like. The tasks have a Completed event you can listen to.
Other miscellaneous changes you might run into:
1. The ApplicationBarIconButton has a new Text property and it can't be empty.. whitespace does not work either.
  You must enter something; old projects will get an InvalidOperationException with message of “Text cannot be empty” if you try to use the buttons with no text.
  To fix: enter some text for your button.
2. OnOrientationChanging virtual method on PhoneApplicationPage has been removed; now you just get OnOrientationChanged
  To fix: remove references to Deprecated event
3. Signature change on PhoneApplicationPage class
  override void OnNavigatedFrom(Microsoft.Phone.Navigation.PhoneNavigationEventArgs e) becomes
  override void OnNavigatedFrom(System.Windows.Navigation.NavigationEventArgs e);
4. AccelerometerReadingEventArgs was refactored and it no longer has a Value property wrapping the sensor data; you can now get to the X, Y, Z properties directly.
5. I already mentioned that WindowsPhoneEvents class was replaced by PhoneApplicationService class.
  The events in these classes were also renamed from Paused to Deactivated and Resume to Activated.
6. System.Windows.Browser.dll has been finally removed. You should not have been using this assembly (since nothing worked, it was not supported). The common reasons to look for this assembly included:
  HttpUtility class, which is in System.Windows.dll in the System.Net namespace.
  Interop between browser and Javascript. If you are needing that, use the WebBrowser control and the ScriptNotify and
7. Changed PhoneApplicationPage.ApplicationBar property from type ApplicationBar to IApplicationBar.
  Your old code should still work, but there might be a cast needed pending how you coded it.
8. ManipulationDeltaEventArgs.CumulativeManipulation.Translation, ManipulationDeltaEventArgs.DeltaManipulation.Translation, and ManipulationDeltaEventArgs.TotalManipulation.Translation are now only populated when the user has moved certain number of pixels from original contact point.
9. Scale property in ManipulationDeltaEventArgs.DeltaManipulation and ManipulationDeltaeventArgs.TotalManipulation has been changed to return 1 when there is no changes (instead of returning 0 in CTP Refresh); this mostly means you can go through your code, and remove the check you would have had to add before where you were detecting 0.0 and throwing it away.
A few push notification changes (this list is best explained via sample, the new TrainingKit has a great hands-on lab that will walk you through these changes )
1. Microsoft.Phone.Notification went away, reference Microsoft.Phone
2. Channel.ExceptionOccurred event is now Channel.ErrorOccurred
3. HttpNotificationChannel.BindToShellNotification is now HttpNotificationChannel.BindToShellTile ()
4. NotificationChannelExistsException has been removed. You can now check if HttpNotificationChannel.IsShellTileBound before you bind to Shell
5. ShellEntryPoint class is gone. We not use standard Uris
6. HttpNotificationChannel.ShellNotificationReceived is now HttpNoficationChannel.ShellToastNotificationReceived

Steps for migrating your code (referenced above as MigrationTips.X ) :

Fix all project references.

Remove references to Microsoft.Phone.Controls, Microsoft.Phone.Controls.Navigation, Microsoft.Phone.Controls.WebBrowser, Microsoft.Controls.WebBrowser.interop
Add a reference to Microsoft.Phone assembly

Do a global search and replace for the xmlns declarations. For example:

Search for	Replace with
clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Navigation	clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone
clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.WebBrowser	clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone
clr-namespace:Microsoft.Phone.Shell;assembly=Microsoft.Phone.Shell	clr-namespace:Microsoft.Phone.Shell;assembly=Microsoft.Phone
clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls	clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone

The list above is not all inclusive, but it is the most common one and shows you the “pattern” to use: don’t replace the whole xmlns declaration, just replace the clr-namespace strings, and your code will be easier to migrate. The search above can be applied to just XAML files, making it slightly quicker to replace all.

Fixing themes and App.xaml resources issues:
Assuming you had not added your own resources,
1. open App.xaml and remove all the Application.Resources
2. Do a global find/replace for following strings, these are resources that were in App.xaml but are not automatically inserted by the run-time. Most of these are used by the default Mainpage.xaml that every new project includes:

Search for Replace with:

PhoneTextPageTitle1Style PhoneTextNormalStyle

PhoneTextPageTitle2Style PhoneTextTitle1Style

PhoneTextApplicationNameStyle PhoneTextNormalStyle

PhoneTextTitleNameStyle PhoneTextTitle1Style

Fixing your WMAppManifest.xml file
1. The easiest way to fix your manifest is to create a new empty project with same name than your existing one, and copy the whole WMAppManifest to your project. You can also copy a few of the attributes, elements. These are the commone ones to watch out for:
2. XNA projects used to have an PlaceHolderString="Default task" on the WMAppManifiest.xml this XML attribute is not longer valid, please remove it.
3. In the App element, the Genre attribute changed from NormalApp to Apps.Normal
4. In the App element, the RuntimeType attribute changed from SilverLight to Silverlight. {notice the case difference on the L}
5. Do clean-up or update the auto-generated metadata on your WMAppManifest, including App.Author, App.Description and App.Publisher
6. If you do not have capabilities (maybe you were not using refresh but MIX build) copy the whole <App><Capabilities> element from the empty project to yours
7. <Tasks> collection has a <DefaultTask> element with a new NavigationPage attribute. In previous builds this was set via code in App.xaml via the <Application.RootVisual> you can use either. They both work, just make sure you have one or the other approach (and not both)
Remove old workarounds:
1. Remove checking for 0 == ManipulationDeltaEventArgs.*.Scale.
2. TransformToVisual and FindElementsInHostCoordinates. Orientation has been fixed and now we rotate the application frame, so these workarounds are no longer needed.
3. You can now reference signed assemblies again, so if you had used the workaround to unsign them, you can remove it again.

Closing Advise/asks:
Please share back your experiences and tips!! I know this document is not 100% comprehensive. If you run into one change that I missed or get stuck along the way, please email me directly [via email blog author on the sidebar column] so we can update and improve this document.

Don’t forget to read the release notes. This document overlaps with some of the content in the release notes, but I focused on migration, so there are other tips and known issues there that will be useful to you; please take a look at the release notes.

Happy Windows Phone coding!

The Archivist Is Live!

Karsten Januszewski [MS] — 2010-06-28T19:57:00

Well, the project I've been working on for quite a while just went live to the world: The Archivist at http://archivist.visitmix.com. Go give it a whirl and let me know what you think. The intro article is here: http://visitmix.com/LabNotes/Intro-To-The-Archivist and you can download the source code here: http://code.msdn.microsoft.com/archivist.

Been quite an adventure building and shipping this puppy -- looking forward to seeing what happens now that it is out in the wild.

BeeEye (Bing Image Viewer)

Lester Lobo — 2010-06-28T12:56:00

BeeEye is a Bing Image viewer application. Its got a very Blendish look and feel and was a quick project for our intern, Aykut Bal.

Its Multitouch enabled and also has some facebook integration. The search history keep track of previous image searches along with the thumbnails. It also showcases the jumplist feature in Win7.

you can find the app\code at LINK .. Give it a try...

Share this post

2D matrices in WPF and Silverlight

Olivier Dewit — 2010-06-27T18:45:00

I've just published a review article about 2D matrices, which specifically addresses the rotation calculations. To be clear on the fundamentals...

Appearing on .NET Rocks

Charles Petzold — 2010-06-26T15:21:44

I will be appearing on a special Live Weekend edition of the Internet radio show .NET Rocks with hosts Carl Franklin and Richard Campbell. Many guests are scheduled; I'm slated for 9:00 – 10:00 AM Eastern Time on Sunday, June 27, 2010. Because it's live, you can call in and chat! Details are here:

... more ...

The Mathematics of Pathological Tennis

Charles Petzold — 2010-06-25T17:06:22

Many tennis fans seemed to enjoy the 5th set of the recent Wimbledon match between John Isner and Nicolas Mahut. In the absence of a tie-break for the final set, it went on for 138 games, finally ending at an unfathomable score of 70-68 with only one break of serve at the end.

... more ...

Visual Studio 2010 WPF Trace Settings Default Is Incorrect

Karl Shifflett [MS] — 2010-06-24T20:18:22

A few weeks ago I found that after setting the attached property PresentationTraceSources.TraceLevel=High on a binding, I was not getting the expected verbose output. You can see an obvious error in the Path property name. <TextBlock Text="{Binding diag:PresentationTraceSources.TraceLevel=High, Path=XCustomerID}" /> Using the above in WPF 3.5 SP1 would result in many messages being outputted in [...]

Creating A Silverlight Blog That Doesn’t Suck

Jesse Liberty [MS] — 2010-06-24T19:27:19

Want to stand out from the crowd? Provide me with information I can't get elsewhere.... You have to focus on what your blog has to offer that is different, new, interesting, better than all the other blogs available, or I return to my original question: is this worth doing?

HyperVideo & Windows Phone 7 Project Update

Jesse Liberty [MS] — 2010-06-23T20:12:39

This is a quick update on the next steps for the HyperVideo Project that will touch on the following three sub-projects scheduled to be completed in the next six months: Update to the web-based project (HVP v2) Initial “port” of the HVP to Windows Phone 7 (HVP/WP7 v1) Transmedia inspired WP7 application (HVP/WP7 v2) [...]

HttpClient and HttpResponseMessage Unhappy in Medium Trust

Karsten Januszewski [MS] — 2010-06-20T03:47:00

Just hit an issue where I was using the WCF REST Starter kit and their wrapper methods for handling HttpWebRequest and HttpWebResponse for consuming ATOM. All was fine -- until I deployed. Then I was getting a securtiy exception. So, I ported the code to use raw HttpWebRequest and all worked. My guess is that my provider has configured something to explicitly allow for HttpWebRequest but not wrapper methods around it. Or something. Anyway, here was my old code:

        private SyndicationFeed GetFeed(string url)
        {
            using (HttpClient http = new HttpClient())
            {
                using (HttpResponseMessage resp = http.Get(url))
                {
                    resp.EnsureStatusIsSuccessful();
                    return resp.Content.ReadAsSyndicationFeed();
                }
            }
        }

And here's my new code:

   private SyndicationFeed GetFeed(string url)
    {
        HttpWebRequest request = (HttpWebRequest)HttpWebRequest.Create(url);
        using (HttpWebResponse response = (HttpWebResponse)request.GetResponse())
        {
            if (response == null)
                return null;
            if (response.StatusCode != HttpStatusCode.OK)
                return null;
            using (XmlReader reader = XmlReader.Create(response.GetResponseStream()))
            {
                try
                {
                    return SyndicationFeed.Load(reader);
                }
                catch (Exception)
                {
                    return null;
                }
            }
        }

Optical Art

Karsten Januszewski [MS] — 2010-06-18T22:51:00

This picture is wack:

TestAPI V0.5 Released

Lester Lobo — 2010-06-18T14:54:00

TestAPI - It is a library of test and utility APIs that enables developers and testers to create testing tools and automated tests for .NET and Win32 applications. TestApi provides a set of common test building blocks -- types, data-structures and algorithms -- in a simple, layered, componentized and documented stack.

Its now the 5th version. In this release, we have put in a lot of fixes and updated things.

- New Theme Changing API - enables testing on different OS themese

- Sub image comparison support

- Revamped variation generation API

- Fixes\updates to command line parsing, tests, string generation, .....

Please do send feedback. Features are driven based on user feedback :)

Share this post

Some basic sample to make your code “Linq ready”

Mitsuru Furuta [MS] — 2010-06-18T10:58:00

Linq has been shipped with VS2008/.Net 3.5 and is not really new. If more and more people are getting used to its syntax, it’s sometimes hard to imagine all the scenarii where Linq to object can replace the classical way we program. During some Silverlight coding, I changed my code to make it run in a better Linq spirit and I wanted to share with you this little sample.

Silverlight (and WPF) maintains a tree of visuals. A useful class named VisualTreeHelper provides a very simple api to navigate this tree. One very common scenario is to look for the first visual parent of a T type for a given control. For instance, your control is in a template and you want to retrieve the templated control which you know is a ListBoxItem.

The VisualTreeHelper.GetParent() method (see prototype below) simply gives the graphical parent of any visual (as DependencyObject).

public static class VisualTreeHelper
{
    //
    // Summary:
    //     Returns an object's parent object in the visual tree.
    //
    // Parameters:
    //   reference:
    //     The object to get the parent object for.
    //
    // Returns:
    //     The parent object of the reference object in the visual tree.
    //
    // Exceptions:
    //   System.InvalidOperationException:
    //     reference is null, or is not a valid System.Windows.UIElement.
    public static DependencyObject GetParent(DependencyObject reference);
    ...
}

Let’s try to implement this simple scenario.

public static class MyDependencyObjectExtensions
{
    public static T GetVisualParent<T>(this DependencyObject source) 
        where T : class
    {
        do
        {
            source = VisualTreeHelper.GetParent(source);
        } while (!(source is T) && (source != null));
        return source as T;
    }
}

We can now call:

var lbi = button1.GetVisualParent<ListBoxItem>();

Now let’s try to think in a Linq way. From a given control in the control tree, we can consider all its graphical parents until the root (Page or Window) to be an iteration. In this first implementation we are classically using a while loop to retrieve each parent one by one. This is exactly the definition of an IEnumerable.

In a first step we will just try to retrieve the list of parents :

public static class MyDependencyObjectExtensions
{
    public static IEnumerable<DependencyObject>
        GetVisualParents(this DependencyObject source)
    {
        while (true)
        {
            source = VisualTreeHelper.GetParent(source);
            if (source != null)
                yield return source;
            else
                yield break;
        }
    }
}

Now we have a IEnumerable (a Linq compatible source), we can look for the first parent of a T type using Linq !
I have also created a version allowing to define the depth of your query in case you don’t want to find the first T element but a further one.

public static class MyDependencyObjectExtensions
{
    public static IEnumerable<DependencyObject>
        GetVisualParents(this DependencyObject source)
    {
        while (true)
        {
            source = VisualTreeHelper.GetParent(source);
            if (source != null)
                yield return source;
            else
                yield break;
        }
    }
    public static T GetVisualParent<T>(this DependencyObject source)
        where T : class
    {
        return source.GetVisualParent<T>(0);
    }
    public static T GetVisualParent<T>(this DependencyObject source, int level)
        where T : class
    {
        return source.GetVisualParents().OfType<T>().Skip(level).FirstOrDefault();
    }
}

We can see how Linq simplifies the implementation and the composition possibilities.

Last effort, let’s try to imagine a generic way to create enumerables from functional parts.

In our case we have :

the starting value
the way we get the next value
the exit condition

public static class EnumerableHelper
{
    public static IEnumerable<T> Create<T>(T startElement,
        Func<T, T> nextElementProvider, Predicate<T> exitCondition)
    {
        while (true)
        {
            startElement = nextElementProvider(startElement);
            if (!exitCondition(startElement))
                yield return startElement;
            else
                yield break;
        }
    }
    public static IEnumerable<T> Create<T>(T startElement,
        Func<T, T> nextElementProvider)
    {
        return Create(startElement, nextElementProvider, e => e == null);
    }
}

We can now call :

var parents = EnumerableHelper.Create(
    button1 as DependencyObject,
    d => VisualTreeHelper.GetParent(d));

var lbi = parents.OfType<ListBoxItem>().FirstOrDefault();

You can notice how generic is the Create method. From the caller view the Enumerable is created “on demand”.

Silverlight As Transmedia Platform – Silverlight TV

Jesse Liberty [MS] — 2010-06-17T18:57:25

I’m very excited to say that my discussion with John Papa about Silverlight as a Transmedia Storytelling Platform is live. View Video

Silverlight As A Transmedia Platform

Jesse Liberty [MS] — 2010-06-17T17:01:00

The advent of Windows Phone 7 is particularly exciting to current Silverlight programmers, because Silverlight (along with .xna) is the development platform for the new phone. I recently recorded two Silverlight TV episodes, and in one I created a typical form that might appear in any LOB application, but I created it simultaneously on both [...]

Orientation Strategies for Windows Phone 7

Charles Petzold — 2010-06-16T19:24:46

I've recently been thinking about ways to deal with orientation changes in Windows Phone 7. (That's when the user turns the phone sideways from portrait mode to landscape mode or back again.) I've also been working on the way-overlong chapter on data binding in my forthcoming book Programming Windows Phone 7, and it occurred to me that I might deal with orientation using data binding and data conversion techniques.

... more ...

Flip-Number Clock in Silverlight

Charles Petzold — 2010-06-16T18:18:04

I've seen some print ads recently that feature a phone with a simulation of 1960's style flip-number clock. Such a clock is fairly trivial in Silverlight:

... more ...

Search for	Replace with:
PhoneTextPageTitle1Style	PhoneTextNormalStyle
PhoneTextPageTitle2Style	PhoneTextTitle1Style
PhoneTextApplicationNameStyle	PhoneTextNormalStyle
PhoneTextTitleNameStyle	PhoneTextTitle1Style