app; development

It seems that every supplier of identity libraries has their own idea about controlling the login flow. Of course, none of them seem to match ours. The problem is, they automatically want to

This has been far more difficult than it ever should have been. None of the pieces of the puzzle ever seemed to fit. But here's what happened and what we're doing: Constraints: The

So I thought I would just use Azure Table Storage for everything, given the fact that it's about $0.12 per gigabyte per month. Pretty awesome. But Storage Tables only allow one index.

So, just when I thought I had this figured out... I had selected Authorize.NET as our gateway to allow people to charge credit cards. They have a nice .NET library to connect

In developer blogs over the last year or so, I’ve seen a drift away from a single data model that describes the solution and that every aspect of the app uses. Used

Pro tip: If you are cutting and pasting using Edge and Ghost, be sure to copy and paste instead. Just lost an entire post trying to split one post into two. sigh I

This is the end of day two of trying to get this working. Basically, Microsoft has included this set of Mobile libraries to allow access to Azure Mobile Apps in order to make

Authentication is the process of making sure you are who you say you are. The App is a consumer facing app and that will certainly require authentication by a variety of third party