missed published packages
See original GitHub issueHi and thank you for sharing this awesome projects.
Can I ask to publish all prereleased Equinox packages at the same time?
I just gave up solving dependencies manually after the latest version 4.0.0.rc.1.11
Problem appeared after the ICategory
contract was changed- 53a8c6, but a package Equinox.SqlStreamStore
wasn’t released. Also, it not possible to rollback to the previous Equinox.Core (= 4.0.0-rc.1.3), since this one was unlisted from nuget.org
Issue Analytics
- State:
- Created 10 months ago
- Comments:6
Top Results From Across the Web
the published packages disappeared · Issue #2390
I just updated to v5.1.3 and it seems to have stopped deleting my package list after each restart. I still get unsupported registry...
Read more >Packages are missing after a successful dotnet publish
The publish command works fine but after it is run, I have to restore the project as there are missing packages.
Read more >NuGet Package Restore
If you have missing packages or package-related errors after you run Package Restore, such as error icons in Solution Explorer, follow the ...
Read more >Troubleshoot missing packages - Deployments
If the package exists in the external feed, check it hasn't been hidden/removed from the package feed's index. For example, in NuGet.org you...
Read more >Package missing in Content View - Support
I've a content view with products added. When I publish new version of same content view it dones't show the packages. When I...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The SSS test suite is thorough, and I believe there is significant usage out there.
Ultimately if you’re following the Decider concept (which is hard to avoid with Equinox), your code should be in a good place wrt things being consistent, and you having options due to your Domain logic being persistence ignorant.
It’s still the best SQL Server-backed store I’m aware of; the only proviso being (the pretty major one!) that it’s on its final release.
Great! Thank you, once again