Microsoft 70-486: Manage data integrity

Exam Objectives

Apply encryption to application data, apply encryption to the configuration sections of an application, sign application data to prevent tampering

Quick Overview of Training Materials

Exam Ref 70-486: Developing ASP.NET MVC 4 Web Applications - Objective 5.4
Cryptography the .NET Way
My Post on Objective 5.5 - Implementing a secure site in ASP.NET
MSDN - System.Security.Cryptography Namespace

MSDN - Encrypting and Decrypting Configuration Sections

MSDN - Walkthrough: Encrypting Configuration Information Using Protected Configuration
MSDN - Encrypting Data, Decrypting Data
Simple two-way encryption for C#
Reading from a cryptostream to the end of the stream

Using CryptoStream in C#

Signing and verifying signatures with RSA C#
RSA Encryption of large data in C#

MSDN - Generating Keys for Encryption and Decryption

Pitfalls of trying to mix Entity Framework providers for SQLite and SQL Server

As part of my annual evaluation, I was given the task of figuring out how we might use an in memory database (such as SQLite) to run integration tests against instead of using the full test database (SQL Server).  I was initially optimistic, but after some experimentation I have decided that this approach is fundamentally flawed.  While I think you could theoretically pull it off, you would never recoup the amount of work involved.  Ultimately, I think for integration tests you are better off just pointing EF at a test database of the same type.