Everyone,

I have an HtmlBox to which I'm streaming the bytes of a pdf via the form's gateway handler. The relevant code is:

      protected override IGatewayHandler ProcessGatewayRequest(System.Web.HttpContext httpContext, string action)
      {
         switch (action)
         {
            case "Document":
               if (SelectedDocument != null)
               {
                  httpContext.Response.ContentType = SelectedDocument.MimeType;
                  httpContext.Response.BinaryWrite(SelectedDocument.Data);
                  httpContext.Response.End();
               }
               break;
         }

         return null;
      }


When I run this from my local visual studio webserver, the pdf is displayed embedded in the HtmlBox. Yet when this is deployed to IIS, the pdf opens in an instance of Acrobat reader external to the browser. Same code, yet different behavior. The proper mime type is being sent.

Anyone seen this before and solved it? Any thoughts as to why this is happening? The desired behavior is to have it embedded in the HtmlBox.

Thanks.

-- Michael

Unfortunately, this behavior is indeed occurring on the development machine, along with other machines. I've checked the setting you mentioned and it's set to open in the browser. Rats.

I'm wondering if it's not a VWG issue. I've found that we have another website. on the same web server, that has the same code and displays PDFs in an embedded HtmlBox (in a splitter, also the same) that consistently shows the PDF in the HtmlBox. Quite odd. The IIS settings on both websites are identical.

If anyone has a clue, I'd be eternally grateful.

-- Michael

Hi again, Michael,

When I saw this issue it was in a corporate environment, where updates are distributed/controlled by some other process that applications self-updating.

In a couple of cases, I was unable to restore the desired behaviour, and  I had to wait for the version of Adobe reader to be upgraded (to V8.x I think) by this process.

Perhaps the version of Adobe reader has this type of issue.  On those machines where I waited, the registry key edit you can find with a quick google had no effect, and in one case even caused the external display, but this was not reversible by restoring the registry key, and that machine was stuck until the upgrade!

Good luck,
Geoff