Starting at the September 26th stop of the Silverlight Tour in Atlanta, AgiliTrain’s Silverlight courseware has been updated to include all the new features of Silverlight 5 RC. If you’re getting ready to fire up a new Silverlight project, this is the course you should be in.
In my previous post, I encouraged users to upgrade their applications to the newest version of the Windows Phone so that users that get Windows Phone 7.5 (or developers who already have it) can benefit from a newer version of your application. While I readily admit, some of that post is pure selfishness as I want apps to be ready for Mango (and on my phone ;) But there are some things to consider.
I am looking for a great designer/UX person. I am in the middle of a rather large project that I can’t talk about…but I need that great designer-minded person. I am more interested in your sense of usability and flair for great looking apps. The person should be familiar with web and mobile applications and have helped out with consistent look and feel through a full project.
Of note, I am not interested in super-polished, corporate design work – I am looking for something more special than that. Usability is important, but a great sense of style and theme are more important. HTML/CSS wireframes are not nearly as important.
In Windows Phone OS 7.0, you could update your Live Tiles (but not create them) – but you had to do it via a push notification. In Windows Phone OS 7.1, this changes to allow you to not only update the Live Tile for your application, but your application can create multiple Live Tiles.
I am currently reading the Mango (Windows Phone OS 7.1) version of my Phoney Tools project. But I have a particular problem: I need to maintain both a 7.0 and a 7.1 version of the project builds. You might have the same issue with your own project so I thought it’d be a good way to show off some special features that Visual Studio has to help you solve these sorts of situations. Essentially my goal was to maintain one set of code but build both sets from the same source.
First off, I took my original project and created two solution folders and created the 7.1 projects as shown here:
Ok, maybe I can’t leave it at that. As Windows Phone 7 users upgrade to Mango, they probably want a Mango (e.g. Windows Phone OS 7.1) version of your application. Don’t disappoint them. This doesn’t mean you should completely retool your application for Mango. But if I am suggesting that you don’t spend a lot of time on the new app, then why create one to begin with? Fast Task Switching.
In finishing up my new Windows Phone book, I had to deal with the confusing version problem. There are three version numbers to be aware of:
So what is Mango? It comes down to this:
Recently, while working on my Windows Phone 7.5 book, I found the need to display a short URL to some specific documentation. I found that you could use msdn.com to do this but the results were not very satisfying. In fact, if you take a typical documentation ID (e.g. “ff402535”), you can simply do this:
This works but takes you to a simple page that reformats the topic instead of the full MSDN documentation. I didn’t like that solution so I registered http://msdnlink.net. With this new address you can do the same thing:
|Vue.js by Example (New Lower Price)|
|Bootstrap 4 by Example (New Lower Price)|
|Intro to Font Awesome 5 (Free Course)|
|Building an API with ASP.NET Core (New Course)|
|Building a Web App with ASP.NET Core, MVC6, EF Core, Bootstrap and Angular (updated for 2.2)|
|Less: Getting Started (New)|
|Using Visual Studio Code for ASP.NET Core Projects|
|Implementing ASP.NET Web API|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||v4.0.30319||Runtime Framework||x86|
|App Path||D:\home\site\wwwroot\||Runtime Version||.NET Core 4.6.27514.02|
|Operating System||Microsoft Windows 10.0.14393||Runtime Arch||X86|