I’ve been in the market for a new mouse at my day job. I was looking for something that was precise, portable, and most of all comfortable since I’ve been feeling some discomfort in my mouse hand.
I finally settled on the Microsoft Arc Touch Mouse.
I worked on a couple interesting stored procedures at a client this week that dealt with parsing & building XML data. Complex types turned out to be a little more challenging than I realized. Or, to put it another way, I realized my SQL skills when it comes to parsing XML were inadequate when dealing with a complex type.
I have been very interested in the Surface Pro tablet since it was announced this summer. And I knew if I was going to buy any Windows 8 tablet or laptop, it would probably be the Surface Pro. Until, that is, I heard Microsoft’s announcement on Thursday regarding the Surface Pro’s pricing.
Windows 8 is finally been released to the public and Microsoft is evolving their flagship OS for the Post-PC era. For developers in the Microsoft camp, this is an exciting (or terrifying) time depending on who you talk to. The introduction of Metr…I mean, Modern UI Apps via the Windows App Store could prove to be a very lucrative place to release applications. My Windows 8 review will be a little different than most, focusing on topics more related towards a developer.
Message Handlers, commonly known as DelegatingChannels in WCF or DelegatingHandlers in ASP.NET Web API, provide an essential tool for developers to access and manipulate an incoming message prior to that message reaching the HttpControllerDispatcher.
Why would this be useful? Well, you could use a custom message handler for authentication, usage metrics, request logging, the list goes on. I’ll show you an example on basic authentication via simple key validation, but it could be easily extended for OAuth, or some other form of authentication.
We all know perfection is unattainable in software, yet I find myself inadvertently striving for it in my day to day work. What I don’t understand is that I know perfection is unattainable, yet I keep pursuing it. I make mistakes every single day in my work, yet I fear admitting this fact to myself or heaven forbid my colleagues.
I decided to post a follow up to my service locator design pattern post based on all the feedback I received. I certainly agree with the notion that, for most, this pattern is considered a nono anti-pattern that should never been touched or seen in the corporate world. However, this pattern is seen ALL THE TIME in the corporate sector. Whether the community wants to admit it or not.
The Service Locator Pattern is no stranger to enterprise design patterns. In fact, you will see it quite frequently when working in corporate infrastructures. Some developers love it, others despise it. This post isn’t to debate the case for or against the Service Locator. It is, however, a practical example on how to leverage the pattern utilizing WCF & Unity.
Message security and Kerberos seem to go hand in hand these days in the world of WCF. While Microsoft makes it particularly easy for you to secure a respective service under wsHttpBinding with Kerberos, I was unsure how do to this while running under SOAP 1.1. Thankfully, Microsoft gives us a very robust customBinding configuration solution for these cases when wsHttpBinding or basicHttpBinding just won’t do.
After wrestling with Blogger for a few months, I’ve decided to move my blog from Blogger to WordPress hosted on Microsoft Azure. I think Blogger is a great solution by Google for those that just want to write what’s on their mind, but if you’re trying to blog about software development, you really should look elsewhere.