We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, the NEventStore.Sqlite nuget package expects connection string information to be in the old-style Web.config configuration file.
Because ASPNet Core has moved away from this it has made using the nuget package a bit... difficult.
I managed to hack together some support, but it's nasty. It should be reverted as soon as possible.
See the hack in question
The hack requires copying SQLite.Interop.dll to your DNX runtime's bin folder.
SQLite.Interop.dll
eg, ~\.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-final\bin\SQLite.Interop.dll
~\.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-final\bin\SQLite.Interop.dll
Don't forget to delete that file too.
The text was updated successfully, but these errors were encountered:
The hackery just got worse: fdb9096
Sorry, something went wrong.
No branches or pull requests
Currently, the NEventStore.Sqlite nuget package expects connection string information to be in the old-style Web.config configuration file.
Because ASPNet Core has moved away from this it has made using the nuget package a bit... difficult.
I managed to hack together some support, but it's nasty. It should be reverted as soon as possible.
See the hack in question
The hack requires copying
SQLite.Interop.dll
to your DNX runtime's bin folder.eg,
~\.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-final\bin\SQLite.Interop.dll
Don't forget to delete that file too.
The text was updated successfully, but these errors were encountered: