Reacting to ForeignKey API change.
Enabling the test code to run on mono

This does not include the deployment helper on mono. So the test needs to point to a statically deployed application url to run.
There are some bugs in mono Httpclient like in case of 302's RequestMessage's Uri not modified, cookies not cleared in cookie container etc. I will file bugs in mono on those and this is a work around until then.

There is still more work and refactoring. This is a first step.
Increasing the wait time out to 3 seconds after the db file is created.

A couple of selfhost variations are failing on some of the new CI machines. While trying to reproduce I see that the klr.exe processes are lauching fine. But the tests fail for a couple of self-host variations. Only suspicion is this time out as the client gets a socket exception. It is possible that client is making a request before the server is ready.
Updating instructions to run the sample on Mono

With some recent product bug fixes the sample can now run on Mono. The sample uses InMemory store to run on mono due to lack of SqlClient.
Increasing the wait timeout after the application deployment

I'm starting to see that tests start running too soon before the application started. Increasing the wait time to a bigger number.

It will increase the test runtime of each selfhost variation by a couple more seconds, but it will increase the reliability.
React to Identity Rename
Updating deployment helpers to start the host on mono.
Update sample data to include 100 users
remove the packages cause 500
Remove the comment in project.json which break performance build script