Current filter:
                                You should refresh the page.
                                  • I know you get a lot of questions and tickets about "The located assembly's manifest definition does not match the assembly reference" and .DLL's not matching.

                                    I run a dozen sites on DevEx and I have updated probably a dozen times on those dozen sites. I'm VERY familiar with all the tricks, steps, techniques, issues and troubleshooting related to this. Every time I update, I have at least 2-3 sites that have some .DLL's "mismatch" issue which I eventually figure out. For what its worth, it almost always involves .DLL's for HMTLEditor, Reporting or SpellCHecker. SpellChecker .DLL version issue probably account for 80%+ of the problem.

                                    I almost always figure it out but I have site doing the SpellChecker error and I cannot get it fixed. Several times already,  I have: deleted all .DLL's; redeployed them, republished a fresh copy of the webwite with no build errors; stop/started/restarted IIS, recycled App pools; cleared .NET temp folder files, etc etc etc. Everything you guys typically recommend for this issue.

                                    Runs fine locally; builds with no errors; remote site throws the error when an HTMLEditor is called. Any suggestions?

                                    No, I cannot give you a sample of the site. It's hundreds of pages, and a very large database for an internal secured site.  Here is a non-secure page with an HTMLEditor. The only thing on the page is a basic HTML editor.


                                    Normally the first standard answer I get back is "update to the latest" but I just finished updating to 14.1.6 last week, and nothing in ".7" really applies to me, so please don't throw the "update" thing back at me.

                                    BTW, DevEx is THE BEST DEVELOPMENT TOOL on the planet. I would NOT do web development without it.  Hands down, no comparison. I've been using DevEx for several years, and have tried the competitors. No contest...

                                Show all comments
                                • Brent Riggs 09.26.2014

                                  And FYI, I've built large, six figure, comprehensive sites with DevEx... much of what I have created would have taken me 10x longer to build, and been much less in quality without DevEx.
                                  Everybody always sounds like they are griping and complaining in these tickets, so I wanted to make sure that you got some well deserved kudos too....

                                • Paul (DevExpress Support) 09.26.2014


                                  We're really appreciate that you're developing your web applications using our products and I am concerned to hear that you are experiencing difficulties using our components. Usually, issues like the this one are resolved after performing steps from the The "Could not load file or assembly 'X'" error message appears article. If the issue still persists even after doing this, it is rather strange. To begin with, would you please provide us with a Bin folder screenshot, so we can check if all necessary dlls are deployed?

                                  Best regards,

                                • Brent Riggs 09.26.2014

                                  Paul, thanks for your help, and not giving a canned answer.  I have referenced that article and have done everything in it (found no instances of "DevEx" ANYTHING in the machine.config files...).... attached is a screen shot of the BIN folder of my app; again, it builds with no errors, and runs with no errors locally.... I have confirmed that the local BIN folder matches the remote folder exactly in size and count... I also totally deleted the remote BIN folder, and republished the local BIN to the remote site again; still errors with the spellcheck error...

                                • Brent Riggs 09.26.2014

                                  bin folder screen shot... your attachment function is throwing an error uploading a small simple JPG... i've put it online here:

                                • Anthony (DevExpress Support) 09.29.2014

                                  Hi Brent,

                                  Thank you for this information. To help us resolve the issue, please clarify the following:

                                  1. Do you have our components installed to GAC?
                                  2. What is the file version of the DevExpress.SpellChecker.v14.1.Core assembly in the Bin folder? You can check this by right-clicking the assembly => Properties => Details => File Version.
                                  If possible, provide also the mentioned website's Web.config and Global.asax files.
                                • Brent Riggs 09.29.2014

                                  DevExpress.SpellChecker.v14.1.Core assembly in the Bin folder? You can check this by right-clicking the assembly => Properties => Details => File Version.

                                • Brent Riggs 09.29.2014

                                  provide also the mentioned website's Web.config and Global.asax files.

                                • Anthony (DevExpress Support) 09.29.2014

                                  Thank you for the provided screenshot. It seems that something happened with the attachment, please attach it again. In addition, it is still not clear whether or not our components were installed to GAC on the deployment server.

                                • Brent Riggs 09.29.2014

                                  Can you give me specific instructions on how you "install to GAC" or check that on the web server so I can make sure I'm verifying it correctly.
                                  global and webconfig attached

                                • Anthony (DevExpress Support) 09.30.2014

                                  Please refer to How to: Install an Assembly into the Global Assembly Cache. I assume that the assemblies weren't installed to GAC.
                                  As for the attachment, I see nothing wrong with the global.asax file, however, there is no web.config. Please reattach it.

                                  In addition, I suggest that you use the Assembly Deployment Tool to automatically deploy all referenced assemblies to the project's Bin folder.

                                • Brent Riggs 10.01.2014


                                • Brent Riggs 10.01.2014

                                  I have two major sites now throwing this error when an HTMLEditor is called... and
                                  I have deleted/published/built, etc several times. NOTHING is fixing this error.
                                  This is huge problem... I've updated a dozen sites, a dozen times, have always been able to fix these issues.
                                  I have never had to "install an assembly into the Global Cache" and honestly, I have no stinkin' clue what all that means on the link you sent me: How to: Install an Assembly into the Global Assembly Cache.

                                • Anthony (DevExpress Support) 10.02.2014

                                  The only assumption left is that the assembly is corrupted. Please perform the following steps to clear the cached assemblies and deploy the fresh application:

                                  1. Close Visual Studio;
                                  2. Restart your IIS or better yet, restart the "World Wide Web Publishing" service (Start menu\Settings\Control Panel\Administrative tools\Services);
                                  3. Clear existing "Temporary ASP.NET Files" directories:
                                      - C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\
                                      - C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\
                                      - C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\
                                      - C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\
                                      - C:\Users\[your_user_name]\AppData\Local\Temp\Temporary ASP.NET Files\
                                  4. Clear the project's Bin and Obj folders and deploy new assemblies. Use the attached DevExpress.SpellChecker.v14.1.Core assembly if your Bin/Framework assembly is corrupted;
                                  5. Look for the App_Licenses.dll file within your solution and delete it, if found;
                                  6. Rebuild your application;
                                  7. Deploy the application to the deployment server.
                                • Brent Riggs 10.02.2014

                                  After running out of options and two sites down, I went ahead and updated to 14.1.7 which I was avoiding because I manage more than a dozen sites with DevEx, and because there was really nothing in 1.7 that affected me.
                                  However, I went through the whole usual routine of upgrading, and things are working now on those two sites. Now I just have to go do the other 10+...

                                • Anthony (DevExpress Support) 10.02.2014

                                  I am happy to hear that the issue has been resolved. Do not hesitate to contact us if you encounter the same issue with the rest of your sites.

                                1 Solution

                                Creation Date Importance Sort by

                                The issue has been resolved by updating the DevExpress suite to 14.1.7.