There was a old post with the same error; but, there was no resolution, I've upgraded to the latest release and still getting the error. Entries in web.config.Version=13.2.20132.2028
<package id="AjaxControlToolkit" version="7.1213" targetFramework="net40" /> <package id="AjaxMin" version="5.7.5124.21499" targetFramework="net40" /> <package id="HtmlAgilityPack" version="1.4.6" targetFramework="net40" /> <package id="jQuery" version="2.1.0" targetFramework="net40" /> <package id="Microsoft.Data.Edm" version="5.6.0" targetFramework="net40" /> <package id="Microsoft.Data.OData" version="5.6.0" targetFramework="net40" /> <package id="Microsoft.Data.Services.Client" version="5.6.0" targetFramework="net40" /> <package id="Microsoft.WindowsAzure.ConfigurationManager" version="2.0.3" targetFramework="net40" /> <package id="Newtonsoft.Json" version="6.0.1" targetFramework="net40" /> <package id="System.Spatial" version="5.6.0" targetFramework="net40" /> <package id="WindowsAzure.Storage" version="3.0.3.0" targetFramework="net40"
Getting the 'Infragisitcs' is undefined on line:Sys.Application.add_init(function() { $create(Infragistics.Web.UI.WebDataGrid, {"id":"MainContent_WebDataGrid1","name":"WebDataGrid1","props":[[[,2,,],{"c":{"hdlay":false,"dcwidth":"","rac":"ig_RedPlanetAlt igg_RedPlanetAlt","ea":"false","_pi":"[\"../ig_res/Default/images/ig_ajaxIndicator.gif\",,,\"ig_AjaxIndicator\",,1,,,,\"ig_AjaxIndicatorBlock\",,3,,3,\"Async post\"]","ecr":false,"uid":"ctl00$MainContent$WebDataGrid1","shH":true,"en":"true","hmcf":false,"incolcnt":"0","ocs":1,"we":"false","cbdci":0,"pi":"[]","sv":"1","ti":0,"cbc":0}}],[[[[0]],,],[[[2]],,],[[["Selection",1,0,1,,,,],{"c":{"sc":"ig_RedPlanetSelected igg_RedPlanetSelectedCell","sr":"igg_RedPlanetSelectedRowSelector","si":"igg_RedPlanetSelectedRowSelectorImage","ehs":false,"sh":"igg_RedPlanetSelectedHeader"}}],,,["RowSelectionChanged::1"]],[[["RowSelectors"],{"c":{"rsc":"ig_RedPlanetHeader igg_RedPlanetRowSelector","rn":true}}],,,[]]],[{'0':[[1,"igede12b8d",0,,,""],{"c":{"css":"","headTxt":"ApplicationID","cf":"","type2":6,"htmlEnc":true,"type":"number","footTxt":"","fcs":1,"key":"ApplicationID","dfn":"ApplicationID","vIndex":0,"nullable":false}}],'1':[[0,,0,,,""],{"c":{"css":"","headTxt":"Select An Application:","cf":"","type2":0,"htmlEnc":true,"type":"string","footTxt":"","fcs":1,"key":"ApplicationName","dfn":"ApplicationName","vIndex":1,"nullable":false}}]},{}],[],]}, null, null, $get("MainContent_WebDataGrid1"));In web.config:
<pages> <controls> <add tagPrefix="ajaxToolkit" assembly="AjaxControlToolkit" namespace="AjaxControlToolkit"/> <add tagPrefix="ig" namespace="Infragistics.Web.UI.GridControls" assembly="Infragistics4.Web.v13.2, Version=13.2.20132.2028, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"/> <add tagPrefix="ig" namespace="Infragistics.Web.UI.LayoutControls" assembly="Infragistics4.Web.v13.2, Version=13.2.20132.2028, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"/> <add tagPrefix="ig" namespace="Infragistics.Web.UI.ListControls" assembly="Infragistics4.Web.v13.2, Version=13.2.20132.2028, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"/> <add tagPrefix="ig" namespace="Infragistics.Web.UI.EditorControls" assembly="Infragistics4.Web.v13.2, Version=13.2.20132.2028, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"/> <add tagPrefix="ig" namespace="Infragistics.Web.UI" assembly="Infragistics4.Web.v13.2, Version=13.2.20132.2028, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"/> </controls> </pages>
One item I forgot to document. When compilation debug="true" was set, there was no error; however, when debug="false" was set, the error appeared.
yes
Bit of a late reply ( at over 2 years) : but to confirm, this resolved the issue. (Which makes me wonder if perhaps I should get the latest version.)
Thanks very much to you, Mike.
I should also mention if you choose to use the AjaxControlToolkit.config file, it should be placed inside the ROOT of your application.
Here is the solution to this issue:
I assume you are using the latest version of the AjaxControlToolkit? For every instance of the ToolkitScriptManager in your application, you will need to add the following properties:
<ajaxToolkit:ToolkitScriptManager ID="ScriptManager1" runat="server" EnablePageMethods="true" ScriptMode="Release" CombineScripts="false" />
Another suggestion if you're only using a handful of the ACT controls in your application, is to use a config file to only include the necessary controls from the Toolkit in your ScriptResource.axd's that are pushed to client. Create a file called AjaxControlToolkit.config (this should match the name of the ACT assembly, so if you've built it from source as something else, modify name accordingly) and inside add the following as it pertains to your project:
<?xml version="1.0" encoding="utf-8"?><!--If you do not create an AjaxControlToolkit.config file then the ToolkitScriptManager will download all of the JavaScript files required for all of the controls in the Ajax Control Toolkit. --><ajaxControlToolkit> <controlBundles> <controlBundle> <control name="CalendarExtender" /> <control name="ModalPopupExtender" /> </controlBundle> </controlBundles></ajaxControlToolkit>
With these configuration changes, your web applications will run as expected in your deployed environments where debug="false" :
<compilation debug="false" strict="false" explicit="true" targetFramework="4.0">
We spent way more time getting this sorted than I would care to admit, so I hope this helps someone down the road...
Cheers,
Mike
Are there any update about this problem? I've encountered the same problematic. With debug=true everything works, with debug=false same error occurs.
For now it seems that Infragistics and Ajaxtoolkit lastest version are not compatible. I've asked to support team (even sending a sample app) but the answer was to leave debug=true, obviously it is not an accettable answer.
Any update?
Hello guys,
The only suggestion I could provide now is upgrading to the latest service releases and test the projects with them. As I have asked in one of my previous responses we will need more information on the scenarios in which the issue persists.
Looking forwards to your replies.