It can still be some problems with your IE plug-in configuration. The difference between the two cases is when you dynamically create a PDF file, the extension is not .pdf. So the browser will have to rely on the "ContentType" header to determine which application to load. When you load a static .pdf file, the browser does not have to rely on the "ContentType" header at all. The plug-in supposes to register that it can handle this particular "ContentType" and fire up accordingly. If that part is corrupt, then your browser won't load the plug-in when it sees the corresponding content type.
I would recommend you to change your code to load a static Pdf file on your server and then send it to the client. The code will be something like this:
Code: C#
//Set up the header
response.Clear();
response.ClearHeaders();
response.ContentType = "application/pdf";
//Load the pdf data from a file
byte[] pdfData = File.ReadAllBytes(a_pdf_file_on_your_server);
//Send the raw bytes down to the browser
response.OutputStream.Write(pdfData, 0, pdfData.Length);
response.End();
If even this does not work, then the problem definitely has to do with your IE. You may want to reinstall Adobe Reader to get it working.
If this works but when you call ConvertUrl it does not work, then change your code to the following:
Code: C#
//Get the raw bytes of the pdf document
PdfDocument doc = new PdfDocument();
HtmlToPdf.ConvertUrl(your_url, doc);
MemoryStream ms = new MemoryStream();
doc.Save(ms);
byte[] pdfData = ms.ToArray();
Now you should come to the same scenario with your “working scenario” because in both cases you are sending the raw bytes down to the browser directly.
Thanks