Home › Forums › WinForms controls › Xceed Chart for WinForms › Exception : Could not load file or assembly ‘Xceed.Chart.GraphicsGL.v4.3.dll’ or one of its dependencies. The specified module could not be found.
User (Old forums)MemberAugust 30, 2010 at 4:25 amPost count: 23064
I am using Xceed controls in my Asp.Net application. While deploying the web site I came accross the below exception :
“Could not load file or assembly ‘Xceed.Chart.GraphicsGL.v4.3.dll’ or one of its dependencies. The specified module could not be found.”
Please provide me the solution for this. I have attached image of the exception i came accross.
Thanks in Advance!!
Imported from legacy forums. Posted by Aniruddha (had 4184 views)User (Old forums)MemberSeptember 7, 2010 at 11:07 pmPost count: 23064
I also have this problem.
I use Xceed, it can run in my computer.
But if I put it on the web server, it shows
Could not load file or assembly ‘Xceed.Chart.GraphicsGL’ or one of its
dependencies. An attempt was made to load a program with an incorrect
Can any one give me the solution?
Imported from legacy forums. Posted by Alice (had 583 views)User (Old forums)MemberDecember 29, 2010 at 6:39 pmPost count: 23064
I dont work for Xceed but I ran into this Issue 4 times with this control (all being operator error on my part). If his helps here is what I did those times:
1. My dev machine was x86 and my Server was x64. To fix this I just asked Xceed for x64 bit binaries for the Xceed chart. They are not included in any install package you get from the site, you have to request them. Dropped in x64 bit dlls (without recomplie), everything worked great. Alternatively or ensure its just a x86 vs x64 bit issue: if your in a C# exe project, right click on the project select properties go to the build tab and instead of “Any CPU” force it to be x86 instead. Then when you run the app even if your on a 64bit box it will run using x86 version of chart, which is what you get with the default installed of the Xceed Chart.
2. I forgot to install the signed version of the Xceed chart in the GAC (or you can just include all the dlls in the exe directory if its a standalone application), so installed them there on the production box, everything worked great
3. The GraphicsGL relies on the C++ runtime. On my win2K3 server even with automatic updates it does not get installed. So you have to make sure the right C++ runtime is installed. For example:
a. 2008 x86 versions of Xceed install this-> http://www.microsoft.com/downloads/en/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en
b. 2008 x64 versions of Xceed install this-> http://www.microsoft.com/downloads/en/details.aspx?FamilyID=BD2A6171-E2D6-4230-B809-9A8D7548C1B6
c.2010 x86 version of Xceed install this -> http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84&displaylang=en
d.2010 x64 version of Xceed install this -> http://www.microsoft.com/downloads/en/details.aspx?FamilyID=BD512D9E-43C8-4655-81BF-9350143D5867
From my limited experience, If you ever get the “Incorrect format” in most cases it means that your application is running 64bit and it is trying to load a x86 binary into the app domain which will give you the “bad image” or “incorrect format” exceptions(or your application is running x86 and it is trying to load a x64 version of a dll into your domain)
Imported from legacy forums. Posted by Robert (had 777 views)
- You must be logged in to reply to this topic.