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.
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.
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.
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS (New)|
|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|
|Implementing ASP.NET Web API|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||184.108.40.206||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|