references.
isolate the interactions cassette makes with the dependency graph behind an interface and factory so we can easily swap between the two.
stub out the hosting service and a quick test app.
simple named pipe service that streams.
move the dependency graph stuff to the hosting project.
nevermind
hammer out the interface a bit more.
spin up a viable instance of cassette in a console app...
integrate with the website
cassette images also go through the interaction interface
dont hold onto a reference to the original assembly
Merge pull request #3 from ZocDoc/IsolateInteractionsWithTheDependencyGraph

Out of Process Cassette.