Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.
If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.
When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:
You may also want to review the installation or upgrading documentation.
I am trying to upgrade my site to 2.3.7.6
I am currently running 2.3.5.3
My database is MSSQL and the OS is XP (on my dev machine) and Windows 2008 r2/ 64 (on production).
When I copy the release code for .NET 4 (or 3.5 for that matter), none of my Ajax accordion controls are working on my site. The area that the controls should be in is just blank.
I have recompiled my controls to use .NET 4, but still, the upgraded site will not see my Ajax functionality in the custom controls.
I have restored the application back to 2.3.5.3 and all is working as it should.
Does anyone have any ideas why the Ajax stuff is no longer working?
thanks
david
are you talking about the jQuery accodion or something else you use in custom code like AjaxControlToolkit?
I am using the AjaxToolkit accordion.
<ajaxToolkit:AccordionID="accordGallery"runat="server"Visible="true"HeaderCssClass="mapGalleryAccordionDisplayHeader"HeaderSelectedCssClass="mapGalleryAccordionDisplaySelectedHeader"Width="80%"RequireOpenedPane="false"></ajaxToolkit:Accordion>
We've updated to newer version of AjaxControlToolkit so you probably need to re-compile your custom code against it.
yeah ... am doing that.
I have changed the custom code to use .NET 4 and use the AjaxControlToolkit 4.1.x
I recompiled it and put the aspx, ascx into the folder the app is expecting and put the dll into the bin directory.
I keep getting this error:
Could not load file or assembly 'AjaxControlToolkit, Version=4.1.50731.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.
If you're working with the source code you may need to delete that dll fromthe /Web/bin so it gets reloaded from _libs and you may also need to drop your reference and then add it back browsing to the new dll.
thanks Joe,
I downloaded the source code (I was using the deployment files) and just started from scratch with re-compiling my controls and re-adding the references.
It is looking like the controls are now working again.