Hello,

One thing about the attached dll:

My Visual Studio Solution compiles and builds correctly with that dll. But annoyingly, even after compiling and building successfully, it fails when is about to debug (see attached pictures).

That problem didn't appear with several previous Aspose.Pdf.Kit dll versions (and the code has not changed).

I just wanted to discard the origin of the issue (somehow the dll itself, or a Visual Studio weird behaviour).

Thanks.

Hi,

According to the error message, it seems the application can't find the Aspose.Pdf.Kit at run time. I think it should not be the problem of Aspose.Pdf.Kit. Please check if the dll is correctly refered. You can also do the following to make it clear:

1) Change the dll to the old version and check if it work.

2) Create a new project and test if the new dll work.

---

Tommy Wang
Lead Developer
Aspose Changsha Team
About Us
Contact Us

Hello,

I have completed those suggested steps:

1) I changed the dll to the old version, and it works.

2) I have created a new project with just 2 lines of code (see atachments).
    
      2.1) See in the picture justReplacingDll.jpeg

        - It compiles
        - The listed error ocurrs in runtime
        - The properties of the dll says it is version 3.1.0.0, while the file is the 3.1.0.7, but also
          the path is not the one where I replaced the dll. It displays next path:
          C:\Program Files\Aspose\Aspose.Pdf.Kit\Bin\net2.0, which is not
          the path where I have replaced the dll at.

      2.2) Just to try, I have moved the dll to that path that the properties displayed   
        (C:\Program Files\Aspose\Aspose.Pdf.Kit\Bin\net2.0),
         and refresh the reference (delete and add again)

        The result is in picture placing_dll_in_AsposeInstallationPath.jpeg: The dll is not recognized.

Am I missing any step? Why then does it work well with older versions?

(I don't want to waste your time with Visual Studio issues, it's just that it's weird that it works with older versions)

Best Regards.

Hi Emilio,

I had experienced the same problem as yours before, I am sure it be a weird behavior of VS which  had agonized me for several days, but now I disremember how did I get out of the nightmare (maybe by modifying/clearing 'references path' of the 'project properties', or something else?). The worst thing is, I even can not reproduce it .  

BTW, we will release our new version middle next month, which will solve your problem of weird behavior of VS, if you still in it.

Thanks,

---

Felix Liu
Developer
Aspose Changsha Team
About Us
Contact Us