Closed nicholasguyett closed 7 years ago
We are still using this package, so I do intend on maintaining this project alive (albeit not as high priority), and also I am willing to accept PRs (if/when those PRs aling with proyect's styling and goals).
However, upgrading to newer wkhtmltox native libraries' version has proven risky in the past, with new bugs and issues arising. So I tend to only upgrade when I am quite confident on new version's stability. Given the end-user can provide it's own wkhtmltox native libraries (or even create his own bundle and register it during initialization) this has not been an issue.. (until now?).
Cheers
On Sat, Dec 10, 2016 at 1:29 AM, Nicholas Guyett notifications@github.com wrote:
Hi Pablo, I noticed this project hasn't been updated recently and wanted to know how much you intend to keep this project (and the associated NuGet package) up to date with the original library.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pruiz/WkHtmlToXSharp/issues/38, or mute the thread https://github.com/notifications/unsubscribe-auth/AALq-YtvWXK5yBK7SZ-O01WbuiJVU625ks5rGfJfgaJpZM4LJfiR .
Thank you very much. I understand, just wanted to be certain this was being maintained.
Hi Pablo, I noticed this project hasn't been updated recently and wanted to know how much you intend to keep this project (and the associated NuGet package) up to date with the original library.