Einar Ingebrigtsen

The easiest thing and actually would avoid this being a breaking change is to make it configurable for now. Typically in the WebConfiguration there could be a flag saying something...

Never mind.. I misunderstood what this was about. Agree - the way things are today, its pretty useless. Added an issue for what I think should do the trick in...

Due to a limitation of the DocumentDB client library, we can't add our Newtonsoft JSON.NET Converters to the serialization pipeline. It looks like its getting fixed though - [here](https://github.com/Azure/azure-documentdb-dotnet/issues/229)

I believe so - time to clean up for duplicates — Sent from Mailbox for iPhone On Wed, Oct 30, 2013 at 8:57 PM, Pavneet Singh Saund [email protected] wrote: >...

Some MetaData should be possible to add from the client as well - take for instance information related to versioning for a readModel a command has been linked with. Handy...

With your EntityContext implementation pulled in - I guess this will fix it all?

Sorry about slow answer. We're in the midst of moving over to doLittle: https://github.com/dolittle/home http://www.dolittle.io I'll get back to you when we have a working end to end sample there.

Look into having something like an extension method or something that says Discover and hook up. The discovery extension method could apply to all properties, or just for individual rules...

With your EntityContext implementation pulled in - I guess this will fix it all?

It should read the /Bifrost route instead. So I'm changing it to that. Well spotted!