UPDATED: Added comments on backend story.
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.
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:
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:
I've been an advocate of Silverlight since it was called WPF/E, so I am not quite an unbiased observer. I decided to sit back and watch the twitterverse explode and see what the world thought. The Silverlight guys got angry; the ASP.NET guys got glib; the open source guys ignored us all.
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.
Sorry everyone but I am still going to finish the last four parts of the Windows Phone 7 Architecture series, but with travel and conferences I am a little behind. But they *are* coming! I promise.
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.
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:
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:
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 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:
Blogging everyday is getting exhausting. But seriously folks (and don't forget to tip your wait staff)... Here in day three of Architecting Windows Phone 7 applications, I want to talk about locating the view-model. 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:
UPDATE: James Ashley correct mentioned that there is no forward navigation in Windows Phone 7. So I updated the example.
With the big announcement of dates, phones and carriers today, there is a log of buzz around the new phones. I intend on picking one up on T-Mobile when their launch happens mid-November. It looks like the number of applications at launch should be around 2,000. I expect this to increase pretty fast. But that means a lot of you out there will be starting to write your own applications.
I recently finished my Blood Sugar monitoring app ("Stay Glucose to Me") for the Windows Phone 7. I battled with the idea of which of the Metro styles to use for my application. Since the new Windows Phone 7 tools shipped with a Panorama control, I started there. What I find most interesting about the iterations of design I went through was how a real app can use (and probably should) use a couple of different metaphors. I could easily see a Pivot or Panorama for a home page then individual pages (that might still have individual simple pages).
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!
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.
|Using Visual Studio Code for ASP.NET Core Projects (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||22.214.171.124||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.25211.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|