-
Notifications
You must be signed in to change notification settings - Fork 160
JetBrains.Annotations dependency problem #170
New issue
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
Comments
Hmm, that's a scenario I have not thought about, I suppose it's really a general problem with using nugets? |
I'm getting the same error, could you remove the JetBrains reference, please? |
This seems to have been built against The downside to doing this is that consumers of the assembly don't get the benefits of attributes - they're only useful when editing the source of the SQLite library. If you'd like consumers of your library to get use out of the annotations, you should remove the reference to the Hope this helps. |
@citizenmatt Ok, I will try that, thanks for the help:) |
@oysteinkrog Seems to work fine after I manually replace JetBrains.Annotations.PCL1.dll reference with JetBrains.Annotations.PCL328.dll. I'm not sure why the wrong library gets referenced during installation, but this is a stable behaviour. |
Hmm ok, well IMO this seems like a general nuget problem to me. |
Thanks for your work, much appreciated! @oysteinkrog |
I'm using the latest
SQLite.Net.Async PCL 3.0.4-beta
in my Universal Store Project. Works fine when built for WP8.1, but gets me an error (below) when built for Windows 8.1. The error is thrown on the firstCreateTableAsync()
call.The package installs
JetBrains.Annotations 9.1.1
dependency which gets you a reference toJetBrains.Annotations.PCL1.dll
in desktop part of the project. (While when installing for Windows Phone part, it gets you a reference toJetBrains.Annotations.PCL328.dll
.)When I launch desktop version:
So, it looks like the reference is wrong or something... Is ReSharper annotations dependency even needed there?
The text was updated successfully, but these errors were encountered: