In this article I would like to show you my implementation and approach for using abstract repository no matter if the client is connecting directly to the database using Entity Framework, over WCF service or WCF Data Services (WCFDS) service.
This blog shortly describes a few chosen DI containers and their out-of-the-box functionality. If a certain container does not have a specific platform listed, it doesn’t necessarily mean that it’s not possible to use it there – it just means that it’s not in the box.
Recently I needed to do some research on the topic of authentication, authorization and related stuff. After spending quite some time on it, I was pretty depressed – one would imagine, that a topic so common has already been handled in a standardized, common and comfortable (both for the user and the developer) way – well, it hasn’t, or do I demand to much?
I’ve recently heard a couple of times about mongodb and finally had a moment to look further into it.
The concept is pretty familiar – to have a data store that is not a relational database. I’ve stumbled upon the info about xml or file system databases (the latter one is used e.g by svn), though nothing seemed to stick.
A while ago Microsoft released a very handy feature that allows for transforming web.config files during builds. This is a great thing, except for some reason, they limited the functionality to web.config files, which was strange, because the engine itself was designed to work against any xml file. Thankfully, that limitation is pretty much gone with a plugin called SlowCheetah.
Just run the YSlow test on our blog. We got a grade “B” which in my opinion is pretty decent (and if I run it with “small site or blog” profile – which is exactly what this site is, we even get grade “A”, but hey, aim high).