Hi - I am getting the following. I am using an older version (because of FIPS mostly).
(function() {var fn = function() {$get("ToolKitSM0_HiddenField").value += ';;AjaxControlToolkit, Version=4.5.7.607, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e:en-US:7c8623f1-14eb-488e-91cc-0436fe374fb8:f2c8e708:de1feab2:720a52bf:f9cec9bc:589eaa30:ab09e3fe:87104b7c:8613aea7:3202a5a2:a67c2700:be6fb298';Sys.Application.remove_load(fn);};
The jQuery
$get("ToolKitSM0_HiddenField").value
returns null likely because the name of the control is "ToolKitSM" not "ToolKitSM0". Could it be something is futzing with the name? I do use the Navigation package from this site (1.9.1.0). A net trace indicates a couple 302 errors
URL Protocol Method Result Type Received Taken Initiator Wait Start Request Response Cache read Gap
/NAEMOWeb/Admins/SourceManagement.aspx?_TSM_HiddenField_=ToolKitSM_HiddenField&_TSM_CombinedScripts_=%3b%3bAjaxControlToolkit%2c+Version%3d4.5.7.607%2c+Culture%3dneutral%2c+PublicKeyToken%3d28f01b0e84b6d53e%3aen-US%3a7c8623f1-14eb-488e-91cc-0436fe374fb8%3af2c8e708%3ade1feab2%3a720a52bf%3af9cec9bc%3a589eaa30%3aab09e3fe%3a87104b7c%3a8613aea7%3a3202a5a2%3aa67c2700%3abe6fb298 HTTP GET 302 text/html 0.74 KB 15 ms <script> 344 0 15 0 0 141
Turning off combine scripts "fixes" the issue.
Comments: this is a result of the old version. the next version (July) doesn't do this. However, the FIPS non compliance has forced me to go thru the .... of creating a Nuget package of the modified version of the Dec release to fix the one line of code. During this above sojourn, I used a bunch of the install builder scripts and they all have problems.
(function() {var fn = function() {$get("ToolKitSM0_HiddenField").value += ';;AjaxControlToolkit, Version=4.5.7.607, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e:en-US:7c8623f1-14eb-488e-91cc-0436fe374fb8:f2c8e708:de1feab2:720a52bf:f9cec9bc:589eaa30:ab09e3fe:87104b7c:8613aea7:3202a5a2:a67c2700:be6fb298';Sys.Application.remove_load(fn);};
The jQuery
$get("ToolKitSM0_HiddenField").value
returns null likely because the name of the control is "ToolKitSM" not "ToolKitSM0". Could it be something is futzing with the name? I do use the Navigation package from this site (1.9.1.0). A net trace indicates a couple 302 errors
URL Protocol Method Result Type Received Taken Initiator Wait Start Request Response Cache read Gap
/NAEMOWeb/Admins/SourceManagement.aspx?_TSM_HiddenField_=ToolKitSM_HiddenField&_TSM_CombinedScripts_=%3b%3bAjaxControlToolkit%2c+Version%3d4.5.7.607%2c+Culture%3dneutral%2c+PublicKeyToken%3d28f01b0e84b6d53e%3aen-US%3a7c8623f1-14eb-488e-91cc-0436fe374fb8%3af2c8e708%3ade1feab2%3a720a52bf%3af9cec9bc%3a589eaa30%3aab09e3fe%3a87104b7c%3a8613aea7%3a3202a5a2%3aa67c2700%3abe6fb298 HTTP GET 302 text/html 0.74 KB 15 ms <script> 344 0 15 0 0 141
Turning off combine scripts "fixes" the issue.
Comments: this is a result of the old version. the next version (July) doesn't do this. However, the FIPS non compliance has forced me to go thru the .... of creating a Nuget package of the modified version of the Dec release to fix the one line of code. During this above sojourn, I used a bunch of the install builder scripts and they all have problems.