December 17, 2015 1 Comment
In the previous post we constructed the database objects that represent the database version of the load testing domain objects. Recall that there’s no automated code generation and mapping tool for MongoDb .NET – at least not yet. Therefore decoupling database and domain objects with MongoDb as the backing store usually means some extra coding but in turn you’ll have completely independent database and domain objects.
We also inserted an abstraction and a concrete implementation for the connection string repository.
In this post we’ll seed the database with the same initial values as we had for the EF data store.