If you missed the Build conference a week or two ago, you probably didn’t hear about a bunch of cool stuff. One of the cooler things was the concept of a Universal App in the Windows ecosystem – you can now target both Windows 8.1 and Windows Phone 8.1 with any C#/C++/WinJS application you make.
It’s Day 2 of the Prairie Dev Con conference! I’m giving two talks today (updated summaries below), but I’ll also be blogging the few sessions I’ll be at between freaking out / preparing for my own.
Today and tomorrow is Prairie Dev Con 2014 in Winnipeg – I’ll be talking on two topics and attending others, so I’ll jot my notes down as we pick things up. Consider this a live blog!
Playing around with some cache headers last night, I ran into some unexpected behaviour from Chrome. Normally I’d blame my code, but there’s a number of devs on the interwebs that have run into the same thing.
For a lot of platform-as-a-service scenarios, you don’t necessarily need to control every aspect of your server’s configuration – in fact, that’s the point of PaaS; you shouldn’t have to worry about such things. In the off chance you do have to make a manual tweak, it can range anywhere from impossible to difficult to do. With Azure, making a change to a server-level file such as ApplicationHost.config is as simple as setting a variable.
If you were to do an audit of the average web application, you’d probably find anywhere from one to ten calls to a database per page rendered or API call served. There’s a certain amount of overhead associated with each individual database query, so instead let’s make one query and return as much data back as needed.
SQL Server 2014 has a new feature called “In-Memory OLTP” – it lets you declare a table as “memory optimized”, which loads and interacts with that table in memory as opposed to disk. This, along with other related improvements, can get you anywhere from a 5x to 20x performance gain compared to traditional tables.
Finally, after months of sketchy integration test failures and banging heads against keyboards, last Friday I figured out the issue with our e-mail based integration tests. Read on!