Support Forum
 
  Support Forum  Modules  Engage: Publish  AJAX Toolkit Version 3.0.11119.0 ??
Previous Previous
 
Next Next
New Post 3/11/2008 9:44 PM
  John Henley
140 posts
5th Level Poster


AJAX Toolkit Version 3.0.11119.0 ?? 

Can you tell me if Engage-Publish will work with that version?  I have another module with requires it.

 
New Post 3/11/2008 9:51 PM
  John Henley
140 posts
5th Level Poster


Re: AJAX Toolkit Version 3.0.11119.0 ?? 

Well I guess here's my answer.  I have 3.0.11119 installed, and here's what I get:

DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load file or assembly 'AjaxControlToolkit, Version=1.0.10920.32880, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.Web.HttpParseException: Could not load file or assembly 'AjaxControlToolkit, Version=1.0.10920.32880, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'AjaxControlToolkit, Version=1.0.10920.32880, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'AjaxControlToolkit, Version=1.0.10920.32880, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' at System.Signature._GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, IntPtr fieldHandle, IntPtr methodHandle, IntPtr declaringTypeHandle) at System.Signature.GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, RuntimeFieldHandle fieldHandle, RuntimeMethodHandle methodHandle, RuntimeTypeHandle declaringTypeHandle) at System.Signature..ctor(RuntimeFieldHandle fieldHandle, RuntimeTypeHandle declaringTypeHandle) at System.Reflection.RtFieldInfo.get_FieldType() at System.Web.UI.Util.GetNonPrivateFieldType(Type classType, String fieldName) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildFieldDeclaration(ControlBuilder builder) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.TemplateControlCodeDomTreeGenerator.BuildMiscClassMembers() at System.Web.Compilation.BaseCodeDomTreeGenerator.BuildSourceDataTree() at System.Web.Compilation.BaseTemplateBuildProvider.GenerateCode(AssemblyBuilder assemblyBuilder) at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. --- End of inner exception stack trace --- at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at Engage.Dnn.Publish.ItemDisplay.LoadControlType() --- End of inner exception stack trace ---

 
New Post 3/11/2008 9:56 PM
  John Henley
140 posts
5th Level Poster


Re: AJAX Toolkit Version 3.0.11119.0 ?? 

If I "downgrade" to 10920, Engage-Publish works, but not my other module which requires 11119....

PLEASE FIX. 

 
New Post 3/11/2008 10:38 PM
  SuperUser Account
12 posts
10th Level Poster


Re: AJAX Toolkit Version 3.0.11119.0 ?? 
Modified By SuperUser Account  on 3/11/2008 9:40:00 PM)

Unfortunately when we compile Publish against the 9/20 release for some reason the newer releases won't work. I'm not sure why, but I believe it has something to do with the way the toolkits are compiled.

Shoot me an email and I can see about compiling you a special version of the module. We'll be putting a 05.00.01 release out later this week but aren't likely to do a public recompile using a newer version of the Toolkit for another release or two.

chammond - engagesoftware.net

 
New Post 3/12/2008 8:42 AM
  John Henley
140 posts
5th Level Poster


Re: AJAX Toolkit Version 3.0.11119.0 ?? 

OK, I must be an idiot.  I went back and looked at my notes on why I installed 11119, and it turns out the compatibility issue I had before was between 10618 and 10920, and I had to install 10920 in order to get the other module to work.  Which means that both the other module and your module should both work, since they use 10920....

Now I just need to figure out when I "upgraded" to 11119....

 

 
New Post 3/21/2008 3:52 PM
  Brian
5 posts
No Ranking


Re: AJAX Toolkit Version 3.0.11119.0 ?? 

I just downloaded and installed Publish 5.0.0 yesterday and installed AJAX toolkit 1.0.20229  and am seeing the same exact error.  I really don't want to have to reinstall DNN (as I have seen that some have done).  This is obviously going to be a continual issue for people IF it is related to the newer AJAX toolkit build.  Does anyone know of a fix yet or if I am doing something wrong?

 
New Post 4/15/2008 5:09 PM
  Brad
20 posts
9th Level Poster


Re: AJAX Toolkit Version 3.0.11119.0 ?? 

I am running Assembly AjaxControlToolkit, Version 3.0.20229.20843 and I am getting an error too.
I just purchased this module, but I have yet to be able to use it. 
Should this module working using .Net 3.5 and the AjaxControlToolkit, Version 3.0.20229.20843 ?

Thanks for any help anyone can give,

Brad

 
New Post 5/5/2008 3:16 PM
  Accuraty/Jeremy
13 posts
10th Level Poster


Re: AJAX Toolkit Version 3.0.11119.0 ?? 

I am having the same problem.  The DLL comes in two version 1.0 and 3.0, which one should I be using?

 
New Post 5/5/2008 3:19 PM
  Chris Hammond
822 posts
2nd Level Poster


Re: AJAX Toolkit Version 3.0.11119.0 ?? 

For the 5.1.3 release we have two packages, one that will work with 1.0.10920, or one that works with 1.0.20229. These are both available from the downloads page here on the site.


DotNetNuke Core Team Member
Engage Software
St. Louis, MO
314.966.4000



The leading provider of DotNetNuke support, training and custom development.
 
Previous Previous
 
Next Next
  Support Forum  Modules  Engage: Publish  AJAX Toolkit Version 3.0.11119.0 ??
Buy now!

Purchase modules

click here to buy now

Please click here to register for an account and payment will be processed via PayPal.

Test Drive!

Test drive our modules

click here to test drive our modules

Want to find out how it works? Visit our demo site to see the modules in actions!

Subscribe

Sign up for our newsletter and get the latest product updates!

Online Support

Get the latest!