If I switch out the dll to 20229 it just gives me exceptions. If I use 40412, it shows the page with nothing in it, and only IE shows the script error "AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts..." FF and Chrome just shows blank page with no script errors.
Now, it requires .Net v3.5, that's clear, what's unclear is that I have server 2008 R2, and it shows it has v3.5.1 installed on it (which is v3.5 SP1), when I go to the app pool I see v2.0 (under basic settings it is v2.0.50727), and when I get the error page on the website it reports "
Version Information: Microsoft .NET Framework Version: 2.0.50727.4927; ASP.NET Version: 2.0.50727.4927", which is supposedly v2.0 SP2, so why can't I find v3.5?!? Based on the info at
this link v3.5 SP1 is v3.5.30729.4926. What is going on with this .net versioning? It's just messing up my brain.
I remember talking with some tech support guy on some app support, when I asked why is it 2.0 and not 3.5, he just asked me whether I have seen 3.5 somewhere (which I really haven't, only on paper but never in settings), so v2.0 is v3.5 he said. That's a messed up math right there, it's 2 but really it's 3.5, so if that's true then v2.5 would really be v4.0? And why then v1.1 was v1.1?!?
Could someone, please, shed some light on this messed up versioning so I get the math right?
And if I got it right, DNN does *not* support Ajax Control Toolkit unless you go back to .net v2.0, the one that's not really v3.5, which really is needed for DNN v5.2 and higher to work, thus making Ajax Control Toolkit incompatible with DNN v5.2 and up?
Well, it's really that bad in my brain right now, can't help it...
Thanks,
Val