Dima Bardakov

Just noticed that `Microsoft.Azure.Documents.Document` has `IDynamicMetaObjectProvider` so my straightforward solution is just to downcast it: `var doc = (EveneumDocument)(document as dynamic);`.

> Hello Dmitry - thank you very much for your PR. > Could you please take a look at the failing build? > Hi, Jakub, I've fixed some things to...

Also it could work if you replace devops task that runs test in full .Net Framework with [task that runs them in .Net Core](https://docs.microsoft.com/en-us/azure/devops/pipelines/ecosystems/dotnet-core?view=azure-devops&tabs=dotnetfive#collect-code-coverage). Btw, do you usе some dedicated...

Guess it's clear at this point. I wonder, though, if `Version` itself belongs to `Event` or should be moved to it's metadata.

> It seemd to work nice! Here's my code if anyone's interested > > ``` > public class UnitOfWork : IUnitOfWork > { > private readonly ApplicationDbContext _context; > private...

Since then, I've discovered that JSON5 format is supported and works fine when corresponding option is checked. Maybe an error could give user a hint to use this flag?

Ofc we _can_ write all the "wiring" ourselfves, the question is - should we? Azure functions states the serverless aproach - and logging to attached AppInsights exceptions thrown in `Startup`...

My vote is to just drop it. `.Net Standard` was introduced for compatibility, is there any reason not to embrace it?