<bindingRedirect> settings I tried in machine.config and also in web.config.

Hi,

please try to use something similar to code below, although this is for older version this approach should work:

Also please take a look at the following
http://www.mono-software.com/Mono/Pages/Discussion/dtopic/5g2sMDkZR0KyP57eAJewDw/Danish-alphabet/?dmsgId=1oZZcSW2IkGAkZ7gAQRexg#Post1oZZcSW2IkGAkZ7gAQRexg 

Regards

I guess you were missing the <assemblyIdentity...> so it didn't know which assembly you were speaking of

btw, you may need to have an assembly compiled with same version of .NET of your MonoX build (maybe also doublecheck which .net runtime your apppool uses). I guess a 3 or 3.5 .net assembly would load in .net 4, but the other way arround might not always work (?)

Same results, still not working.

Can you explain me differences between mine and yours solution? It seems to me, that your code is the same as mine.

I try it also with <assemblyIdentity> and still not working. I use Mono-X .NET4 version and my project is also .NET 4 project.

<runtime>
<assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="AjaxControlToolkit" publicKeyToken="28f01b0e84b6d53e" culture="neutral" />
<bindingRedirect oldVersion="3.0.30930.28736" newVersion="4.1.60623"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Hi,

can you please try to use this, we are using this without any issues:

Note: you have 0 at the end of the AjaxControlToolkit version - 4.1.60623.0

Regards

If it's not the ".0" you were mising at the end of "newVersion", an other question is whether you're placing this statement at the correct position in web.config file (guess if you use Visual Studio.net to edit it it will check the schema and also I think ASP.net also checks if it follows the correct XML schema at runtime). So it would remain that you're placing it at wrong web.config (at some parent folder it should work too I think, so should it do at machine.config for all ASP.net I guess)

Hello boys,

finally it works. Many thanks to all. Whole problem was based on mising ".0" in newVersion attribute.

I'm glad that you have fixed the issue, I'm closing the topic and if you have any further questions please open a new one.

Regards