What steps are needed in order to actually use the code in the git repository for EF?
if I just do a clone of the repo and remove the broken VB test, it will compile, sometimes.
I'm not sure if it is the Test Explorer that starts to fiddle with the tests and prevents further re-compilation or if it is the build steps in the projects that do some funky stuff.
But either way, the solution holds quite a bit of friction for this reason.
I thought I'd give the HasFlags enum support a go since I've written quit a few expression tree translators for EF already, but I'm still unable to even compile this stuff..
The times it actually does compiles, none of the test assembiles load in xUnit.gui.clr4 because of strong naming issues.
What am I missing here?
I'd like to tamper as little as possible with the projects before starting to write tests.
if I just do a clone of the repo and remove the broken VB test, it will compile, sometimes.
I'm not sure if it is the Test Explorer that starts to fiddle with the tests and prevents further re-compilation or if it is the build steps in the projects that do some funky stuff.
But either way, the solution holds quite a bit of friction for this reason.
I thought I'd give the HasFlags enum support a go since I've written quit a few expression tree translators for EF already, but I'm still unable to even compile this stuff..
The times it actually does compiles, none of the test assembiles load in xUnit.gui.clr4 because of strong naming issues.
What am I missing here?
I'd like to tamper as little as possible with the projects before starting to write tests.