Hi
I have been developing and running an ASP.NET app that uses SpirePDF for the last 12 months, without issue. I recently updated Visual Studio to the latest version (17.1.1 -> 17.7.1) and now all calls to the PDF component fail with:
The conversion provider cann't be found. " & vbCrLf & "Please make sure the folder ""plugins"" is under the same folder of Spire.Pdf.dll.
The plugins folder is definately in the bin folder (and always has been) and my solution has not changed. Only difference is now its a new version of VS.
I have tried removing all versions of C++ and reinstalling as VS Installer pulls down the latest C++ x64 installer and as I'm on an ARM machine, installs that version. I have removed C++ ARM64 and installed C++2015 x64 just in case (as this is what was installed prior to VS update) - no difference.
I'm running this as an ASP.NET Framework 4.8 application on M1 Mac under parallels.
Tried updating to latest SpirePDF dll (9.8.5) from my account and replaced older, working version of 8.1.0 - no change
All out of ideas! This is causing me massive issues as currently cannot make changes and redploy this app for the client. HELP - PLEASE!
Hi,
Thank you for your feedback. We apologize for any inconvenience caused.
To address this problem, we recommend checking the following points:
Plugin Permissions: Please ensure that the necessary permissions are granted to the plugin.
Visual Studio Configuration: Check if the "Use the 64-bit version of IIS Express for web sites and projects" option is enabled. You can find this setting under Options -> Projects and Solutions -> Web Projects. Enabling this option can help resolve compatibility issues.
Additionally, we suggest creating a separate simple project to perform a test. By doing so, you can determine whether the problem persists with a minimal setup, which will aid in identifying the root cause more effectively.
Best regards,
Triste
E-iceblue support team
Thank you for your feedback. We apologize for any inconvenience caused.
To address this problem, we recommend checking the following points:
Plugin Permissions: Please ensure that the necessary permissions are granted to the plugin.
Visual Studio Configuration: Check if the "Use the 64-bit version of IIS Express for web sites and projects" option is enabled. You can find this setting under Options -> Projects and Solutions -> Web Projects. Enabling this option can help resolve compatibility issues.
Additionally, we suggest creating a separate simple project to perform a test. By doing so, you can determine whether the problem persists with a minimal setup, which will aid in identifying the root cause more effectively.
Best regards,
Triste
E-iceblue support team
-
Triste.Dai - Posts: 1000
- Joined: Tue Nov 15, 2022 3:59 am
Thanks for coming back to me.
Use the 64-bit version of IIS Express for web sites and projects is already selected in my settings - it has been since the projects start. As I say, after the update, no code was modified or settings changed in VS itself - it just stopped running the SpirePDF plugin.
Moving the exact same solution to an older Windows10 VM, running VS 17.1.1 runs as expected; the PDF writer works fine.
I'm convinced this is something to do with the new ARM64 C++ install thats part of the latest VS update - have you tested locally with this config? If not, can you to see if this is the issue?
Creating a new project from scratch to test the plugin gives the same error BTW.
Use the 64-bit version of IIS Express for web sites and projects is already selected in my settings - it has been since the projects start. As I say, after the update, no code was modified or settings changed in VS itself - it just stopped running the SpirePDF plugin.
Moving the exact same solution to an older Windows10 VM, running VS 17.1.1 runs as expected; the PDF writer works fine.
I'm convinced this is something to do with the new ARM64 C++ install thats part of the latest VS update - have you tested locally with this config? If not, can you to see if this is the issue?
Creating a new project from scratch to test the plugin gives the same error BTW.
-
Proximity - Posts: 2
- Joined: Fri Jan 20, 2023 2:47 pm
Hi,
We appreciate your feedback and apologize for any inconvenience caused.
Unfortunately, we do not have access to an M1 Mac, which makes it challenging for us to conduct specific testing on your environment. However, we recommend that you contact the technical support team at Visual Studio for further assistance.
Once again, we apologize for any trouble this has caused you and appreciate your cooperation. Should you have any other questions or concerns, please feel free to reach out to us.
Best regards,
Triste
E-iceblue support team
We appreciate your feedback and apologize for any inconvenience caused.
Unfortunately, we do not have access to an M1 Mac, which makes it challenging for us to conduct specific testing on your environment. However, we recommend that you contact the technical support team at Visual Studio for further assistance.
Once again, we apologize for any trouble this has caused you and appreciate your cooperation. Should you have any other questions or concerns, please feel free to reach out to us.
Best regards,
Triste
E-iceblue support team
-
Triste.Dai - Posts: 1000
- Joined: Tue Nov 15, 2022 3:59 am
Page 1 of 1