Target netstandard2.0 - Githubissues

lahma commented 5 years ago

I tried to test out this new lib in a full framework project with little luck. There seems to be no reason to target netcoreapp when netstandard2.0 would suffice. By enabling netstandard20 as target it gives us still migrating a chance to use the library.

changed the target to netstandard2.0
changed the test running to use the new embedded ravendb server that Raven 4.1 offers, deleted the binaries as obsolete
main library still targets latest 4.0.7 client library, only tests take advantage of 4.1
fixed the tests that were fixable and I marked ones for features that are not implemented as Skip.

It seems that the Appveyor build configuration is still somehow overriden with MSBuild, but the updated appveyor.yml should do the trick otherwise.

In the future I'm hoping to give a PR to allow customization of migration stamping logic so that I can test this with our old solution.

lahma commented 5 years ago

Ping @JudahGabriel , any interest in this?

JudahGabriel commented 5 years ago

Thanks!

lahma commented 5 years ago

Thank you for accepting! I'll probably offer some others too to make migration easier.

migrating-ravens / RavenMigrations

Target netstandard2.0 #45