Customers and partners often ask me what the benefits are to moving from on-premise or traditional hosting environments to a cloud based platform like Windows Azure or AWS. If you're an ASP.NET application developer, you'll typically find the answer in one or more of these three reasons - Cost, Focus and Capabilities.
So, you're an ASP.NET developer and you're moving your app to the cloud. Time to learn about some alternate forms of persistent data storage... Don't worry, it won't hurt.
We're looking to help developers like you to build the apps that will drive Windows 8. If you're already building Windows 8 applications, or want to get started, let me know. I'll help get you early access to the app store, and even get you a Microsoft engineer to help you build it!
The timing on this couldn't be more, um... ironic. If you don't want to be the next LinkedIn, read this. (Hint: if you don't store passwords in your database, then people can't steal passwords from your database)...
I've been reinstalling a bunch of software on my brand new Win8 machines, and decided to keep a lightweight SQL development experience, so I installed the brand new 2012 LocalDB + SSMS. But then...
Ok, in the previous post we determined how we could attach to LocalDB using SSMS 2012. Next stop, creating a database. Turns out that it's potentially harder than it seems at first.
RoamingSettings is a great way to roam configuration data between your machines, but sometimes you want to keep more complex data than a simple string. Here's how you can do it.
Man, I miss the good old days of classic video games. Now that I'm trying to start writing a few games myself, I'd love to take my old sprites and bring them forward, but how can I maintain that silky smooth pixelated goodness?