Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove direct dependency on Microsoft.Data.SqlClient
See original GitHub issueVersion: 3.1.0
I don`t have any dependency to SQL-Server in my whole project and don’t want to have in future. I don’t need DB-Based Quarz-Features. Now I upgraded the Quartz NuGet package and it installed 50 new dependencies to libraries i will never use… I immediately reverted the update. Isn’t there a way to split the Quartz Lib into a non-DB part, without SQL-Server dependency and the DB dependent part as a sepparate library? Otherwise it will not be possible for me to upgrade Quartz in future…
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think we need to start with re-implementing the
JobStoreSupport.IsTransient, the delegate comes via interface and we cannot add new members before 4.0.I think it will be doable to change the bits checking against SqlException to use reflection instead. This will transfer dependency handling requirement to library consumer as then there’s no out-of the box support for SQL Server anymore as the package isn’t pulled automatically.