Skip to content
This repository has been archived by the owner on Jul 12, 2024. It is now read-only.

'ConfigurationManager' missing #23

Open
charlotte-murray opened this issue May 9, 2017 · 2 comments
Open

'ConfigurationManager' missing #23

charlotte-murray opened this issue May 9, 2017 · 2 comments

Comments

@charlotte-murray
Copy link

I've just updated to the latest version and am seeing an error on line 75 of PDFConvert.cs:

 private static string GetWkhtmlToPdfExeLocation()
 {
    string filePath, customPath = ConfigurationManager.AppSettings["wkhtmltopdf:path"];
    ...

The error is:
The name 'ConfigurationManager' does not exist in the current context

How can I fix this? I'm downgrading temporarily as this is urgent but will upgrade again once you have a fix.

@mstijak
Copy link
Member

mstijak commented May 9, 2017

Have you tried adding System.Configuration reference to your project?
I'll check if it can be automatically added during NuGet install.

@elsauto
Copy link

elsauto commented Aug 15, 2017

I tried the code just today, I got the same error. Yes, System.Configuration is there. I will try fix it and upload a bug fix.

In the meantime, you can hardcode the location for your .exe file. In my case, that would be...
string filePath, customPath = @"C:\Users\Sebastian\Documents\visual studio 2015\Projects\ConsoleApplication\ConsoleApplication\wkhtml";

Thank you all.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants