Hello Cezus, I'm unsure as I have not been able to repo it but you may face some issues due to the fact that the assembly is strongly signed. Perhaps, since your project was build with a previous version of the assembly, it looks for that version which you have deleted.
Try to add an assembly binding redirect in your web.config. You should already find one auto inserted into your web.config if your using the asp.net ajax extentions, just add one for jiffycms as well, telling it which version to resolve to.
| XML |
|
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Jiffycms.Net.Toolkit" publicKeyToken="888641302368c167" culture="neutral"/> <publisherPolicy apply="yes" /> <bindingRedirect oldVersion="1.0.0.0-1.0.6.6" newVersion="1.0.7.7" /> </dependentAssembly> <!-- following is the default stuff you may find already in your web.config. It's unrelated but I'm including it for clarity --> <dependentAssembly> <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/> </dependentAssembly> </assemblyBinding>
|
For now copy the bit i added for jiffycms and add it in your web.config file. Next time onwards, when you take a new version, replace the old version 1.0.6.6 with the oldest you have, and put the new version number in the place of 1.0.7.7 ;
All images are extracted from the assembly via an httphandler and its possible that it was unable to find the assembly as you have deleted it and ignores your current version since it's not matching with the previous assembly you had in there.
I think that maybe it and hopefully I'm not wrong.
Have a good day,