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