Re: FW: Calling Assembly from ASP

> -----Original Message-----
> From: Shawn Davies [mailto:Shawn.Davies@...]
> Sent: Monday, June 08, 2009 3:13 PM
> To: Post all your questions about iTextSharp here
> Subject: Re: [itextsharp-questions] Calling Assembly from ASP
>
> I was finally able to get my class to run and generate a pdf from ASP
> code. Whew!
>
>
>
> After running regasm, I didn't think I needed them in the GAC
> - so I removed my previous entries. Once I added them back in, it
> started working as designed.
>
>
>
> I have my development machine updated with the Reader 9, the PDF opens
> fine from ASP code - although I noticed it opens in the browser
> window. When I use the same class to create a PDF from managed code,
> it opens an separate Adobe Reader window containing the output. This
> may be a browser setting.
>
>
>
> I just tried Adobe 7 and "The file is damaged and could not be
> repaired" from Reader. Any ideas about why? It works fine when calling
> from C# (versus ASP). ???
>
>
>
> Thanks!
>
> Shawn
>
>
>
> Shawn.Davies@... | Office: 918-488-4052 |  Fax:
> 918-488-4245
>
>
>
> From: Fabrizio Accatino [mailto:fhtino@...]
> Sent: Monday, June 08, 2009 1:40 AM
> To: Post all your questions about iTextSharp here
> Subject: Re: [itextsharp-questions] Calling Assembly from ASP
>
>
>
>
>
> - give the full exception
>
>
>
> - place itextsharp dll in the same folder of CustomPdf.CreatePdf dll.
> And try again.
>
>
>
>
>
>    fabrizio
>
>
>
>
>
>
>
> On Fri, Jun 5, 2009 at 10:20 PM, Shawn Davies
> <Shawn.Davies@...> wrote:
>
> Thanks for your response. I used the Framework config tool to change
> the permissions for the Local_Intranet zone to "Full Trust". Same
> results. I would think that if there was a security issue, it would
> have popped-up when the object was instantiated using
> "Server.CreateObject".