In this fifth part of my Architecting Windows Phone 7 applications I will tackle the nature of tombstoning. If you've missed the past parts of the series, you you can visit them here:
While I recognize my original schedule is slipping, let's continue the ten part Windows Phone 7 architecture discussion. In this sixth part of the article series, I want to discuss messaging in phone applications. If you've missed the past parts of the series, you you can visit them here:
The last two stops of the Silverlight Tour are headed to Atlanta and Portland (OR) in the next two months. The Silverlight Tour Workshop is a three-day course on Silverlight 4. It divides the content into three distinct areas: Design, Development and the Server-Side. Students should be able to develop Silverlight 4 applications once attending the workshop. The Workshop is structured with a mix of didactic lessons, demonstrations and hands-on labs. Each student will leave the workshop having created several small Silverlight applications. This variety of learning techniques will ensure that all students become proficient in the technology quickly and in an exciting way.
I spent most of the last week with my early demo Windows Phone 7 (e.g. WP7) phone as my primary phone. See I am a Verizon customer currently and therefore I couldn't use Verizon on the demo phone (as it takes SIM cards and Verizon can't spell SIM). So I took the opportunity while in Europe to get a pre-paid SIM card and use it as my main phone (since my Droid was useless there). You're probably wondering what my impressions were? Well, two caveats to start with...I have bet pretty heavily on the phone so I am not exactly a neutral party, but I'll try to be. Also, I've never owned an iPhone (AT&T is true evil incarnate) so take that for what its worth.
Today AgiliTrain is announcing their schedule for the 1st half 2011. We are visiting cities with both our Silverlight Tour Workshop and our new Silverlight for the Windows Phone Workshop. We are visiting cities around the US including Los Angeles, Chicago, Seattle, Atlanta and San Francisco. You can view the full schedule (which also includes our partner's international stops) here:
In this (somewhat belated) part 6 of my Architecture for the Windows Phone 7, I want to talk about dealing with data across the wire (or lack of wire I guess). If you've missed the past parts of the series, you you can visit them here:
I am pretty invested in the Windows Phone 7 and in that light I went ahead and got a phone at launch. I had a LG developer device that Microsoft got me to help me work on the book. While having an early device is really helpful, I was ready for an up-to-spec device. To get a device early, I left Verizon and moved to T-Mobile (for what its worth, AT&T is just more evil than the rest so I my hand was forced to T-Mobile). I went with the HTC HD7. I took a leap of faith and actually pre-ordered the phone without getting my hands on it. But because this phone hardware was used for the Sprint Android Phone and the HD2 WinMo phone, I'd had a chance to see the other devices and liked the overall size and heft of the device.
I am writing a new Windows Phone 7 application called GooNews to show Google News in an application for the phone. I am writing this application because I needed an app like this. Being able to keep up with news (and create news categories based on keywords) is key to what I wanted to get on my phone. I tried a lot of the other apps out there and when I didn't find what I wanted, I decide to build it myself.
In this eighth part of my series on architecting Windows Phone 7 (WP7) applications, i'll show you how to deal with Toast Push Notifications. If you've missed the past parts of the series, you you can visit them here:
OAs some of you know, in learning to build Windows Phone 7 applications, i've come up with several applications for the phone. Some of the apps started as Demo's for conferences (e.g. Winning the Lottery) and others are ones I wanted to write to get familiar with other parts of the phone API's.
In this ninth part of my series on architecting Windows Phone 7 (WP7) applications, i'll discuss threading on the phone. If you've missed the past parts of the series, you you can visit them here:
In this fourth part of my Architecting Windows Phone 7 series, I will tackle client-side data. If you've missed the past parts of the series, you you can visit them here:
In this second part of my Architecting Windows Phone 7 applications, I want to tackle the use of the Pivot and Panorama control. If you missed the first part of the series, you you can visit it here:
While I have been exceptionally fortunate to get a Windows Phone 7 device, I still am using my Motorola Droid as my primary phone. The primary reason is that I use Verizon and my WP7 phone uses a SIM chip (Verizon doesn't use SIM chips). I expect you're reading this post to gleam some information about the WP7 phone, but let's start with the Android.
I was having a conversation with Chris Tavares of the Patterns and Practices group (the Prism guys). We were talking about the future of Prism (et al.) and the topic of the Windows Phone 7 came up. While MEF, Prism and Unity might make an appearance on the device, the real question to us was why.
Now that the Windows Phone 7 Tools are fully released, I sit here waiting for the phones to be released. In the time between the tool release and the phones being released, I have some precious time to get my applications ready for release as well. While I am not building any mass-market applications (nope, no fart apps here); I am building a number of small applications that should show off some features of the phone.
My Windows Phone 7 Workshop at DevConnections is coming up on November 1st (http://www.devconnections.com) in Las Vegas at Mandalay Bay Resort on the Las Vegas strip! If you are looking for a way to quickly get up to speed on building Silverlight applications using Silverlight for the Windows Phone, its time to sign up!
|Implementing and Securing an API with ASP.NET Core (new)|
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS|
|Building a Web App with ASP.NET5, MVC6, EF7, and AngularJS (Retired)|
|Best Practices in ASP.NET: Entities, Validation, and View Models|
|Front-End Web Development Quick Start|
|Lessons from Real World .NET Code Reviews|
|Node.js for .NET Developers|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||126.96.36.199||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.24628.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|