Jon Galloway

We're continuing the ASP.NET Authentication series (yes, I'm doing a few overlapping series, and yes, it's making me dizzy). The previous post covered Global Authentication and Allow Anonymous. This one continues with a simple tip that can be summed up as follows: keep it simple by extending rather than rewriting.

Many of the key Windows 8 Metro Style application features either require or can greatly benefit from a connection to online services. ASP.NET Web API is a great fit for these services, as it's tightly focused around providing HTTP services to applications. I'm starting a series that will look at how to leverage ASP.NET Web API services from Windows 8 applications.

As I was recently updating the Wrox Professional ASP.NET book for ASP.NET MVC 4, I thought about some of the common questions, tip, and tricks I've seen over the past few years, and thought it was time for a... quick blog series! Let's start with Global Authentication.

I've been at Microsoft for a little over two years now, working in groups that focused primarily on publishing online content for developers. In addition to the obvious things, there's a lot of work that goes on behind the scenes in creating and maintaining content  - maintaining and improving existing content, planning content for unreleased platforms and products, handling dozens of spoken languages and several programming languages, etc. It's been a pleasure working with some real professionals. I've also enjoyed working in a small but dynamic group that's focused on the developer community. During that time I had two excellent bosses, Scott Hanselman and Pete Brown. Both really made it fun to show up to work every day. Well, I work from home, but still.

I'm really excited by the big announcements earlier this week: