I'm having problem working with ASPXToPDF, I'm working with SharePoint and I'm using ASPXToPDF control inside one of my Web Parts, Can I do it in SharePoint?

Line 7: <%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
Line 8: <%@ Control Language="C#" AutoEventWireup="true" CodeBehind="NewHireWebPartUserControl.ascx.cs" Inherits="OsnielTest.NewHireWebPart.NewHireWebPartUserControl" %>
Line 9: <%@ Register assembly="EO.Web" namespace="EO.Web" tagprefix="eo" %>


Source File: /_CONTROLTEMPLATES/OsnielTest/NewHireWebPart/NewHireWebPartUserControl.ascx Line: 9

Assembly Load Trace: The following information can be helpful to determine why the assembly 'EO.Web' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

I reviewed this post:
http://www.essentialobjects.com/forum/postst319_Could-not-load-file-or-assembly-EOWeb-or-one-of-its-dependencies.aspx

But didn't help me.

Thanks

Hi,

I reviewed my Log files and I figure out that EO.Web.dll is never deployed or copy in any place, I found that lines

---

01/03/2013 08:32:30.74 vssphost4.exe (0x1050) 0x1E8C SharePoint Foundation Topology 5mgz Medium Solution Deployment : UpdateFiles - Processing file EO.Pdf.dll of Type GlobalAssembly FileDir
01/03/2013 08:32:30.74 vssphost4.exe (0x1050) 0x1E8C SharePoint Foundation Topology 5mhc High Solution Deployment : Installing to GAC - EO.Pdf.dll

---

But I have not found any "EO.Web.dll" in log files. I copied EO.Web.dll in Bin folder, and I added EO.Web.dll manually to GAC but it still not working. Am I doing something wrong in the deployment?, what else I need to do?

Hi,

No. It has nothing to do with the license. You just need to make sure the right DLLs are there.

Thanks