Do Not Cache When Response not succesful.
Change projects to framework 4.0 to work in vs2010
Merge remote-tracking branch 'upstream/master' into DoNotCacheWhenRequestNotSucces
When Response is null or Response Not succesful, then do not cache on client or server.
If no content, than no server side caching, but do clientside caching.
Remove null default value.
Merge pull request #14 from rjvdboon/DoNotCacheWhenRequestNotSucces

great, thanks!
Null check for actionExecutedContext.Response.

actionExecutedContext.Response is null when error occurs during action execution.
VS formatting
Merge pull request #17 from mdonatas/null-reference-fix

Fixing null ref exceptions in *InvalidateCacheOutput attributes
store and read content as byte[] instead of string

Found this issue when i tried to cache png images. Got corrupted data.
I see no reason to make assumtions about the content. byte[] works for
strings aswell.
Merge pull request #18 from svenclaesson/master

Binary data: store and read content as byte[] instead of string
changed project structure
Issue #15: First request after cache invalidates doesn't go into cache

Seams to be because the CacheMentryChangeMonitor in MemoryCache is not
triggered when calling Add. It will be triggered internally from
memorycache scheduled but too late. That is the issue #15.
Merge remote-tracking branch 'filipw/master'
Fix project references
Merge pull request #19 from svenclaesson/master

Fix issue #15