5
Vote

Not working with Web Deployment Project

description

(originally reported by Hubo)

I am using only Ajax Control Toolkit from ASP.NET Ajax Library. Everything work just fine, but when I make release (using Web Deployment Project) and copy files to server the WatermarkTextBoxExtender stops working (not working at all). When I copy all source files to the server (instead of depolyment release build) the WatermarkTextBox works well. The only clue I have is JavaScript error from browser: "Sys.Extended is undefined" in "Sys.Application.add_init(function() { 166 $create(Sys.Extended.UI.TextBoxWatermarkBehavior, "ClientStateFieldID":"ctl00_ContentPlaceHolder_FirmManagement_AddFirmTextBox_TextBoxWatermarkExtender_ClientState","WatermarkCssClass":"watermark","WatermarkText":"Firm name","id":"ctl00_ContentPlaceHolder_FirmManagement_AddFirmTextBox_TextBoxWatermarkExtender"}, null, null, $get("ctl00_ContentPlaceHolder_FirmManagement_AddFirmTextBox"));
167}); "
The TextBox is in PlaceHolder which is not visible by default.

The same problem I have with ModalPopupExtender.

nallejacobsson wrote Mar 19 at 11:43 PM
I have the same problem, the exact same error message. It is related to the output cache. I only get the error when output caching is enabled for the pages containing the control. Hope this info helps!


Stephen_Walther wrote Jan 20 at 4:28 PM
Can you please attach your Visual Studio Project? At least enough of your project to reproduce the issue? Thank you.


Hubo wrote Dec 16 2009 at 10:54 PM
Without ToolkitScriptManager it does not work at all. I am using it.


Stephen_Walther wrote Dec 16 2009 at 4:07 PM
Are you using a ToolkitScriptManager? In the new Beta release, you need to use the ToolkitScriptManager. You cannot use the standard ASP.NET ScriptManager if you want to use the updated scripts.


Hubo wrote Dec 8 2009 at 10:57 PM
Both assemblies are here. It is not working when the TextBox is inside PlaceHolder. At the begining Visible="false" and with update/postback in UpdatePanel it is set Visible="true".


JimWang wrote Dec 8 2009 at 11:01 AM
Are you using the AjaxControlToolkit.dll assembly here? It sounds like your deployment

file attachments

comments

CarouselDesigns wrote Apr 14, 2010 at 11:53 PM

We're getting this problem as well after just upgrading from 2.0 to 3.5 and the latest AJAX Toolkit.

AjaxControlToolkit.dll is version 3.5.40412.0

Project references are up to date. The old Toolkit files were deleted and the new ones copied from the distribution ZIP. ScriptManagers were replaced with ToolkitScriptManagers. The project builds with zero errors. The built-in AJAX controls (UpdatePanels, etc.,) work but the Toolkit controls don't. This is happening on local developer boxes and on our development server.

I saw the comment about output caching, but I don't know much about that. Our Web.config doesn't have an output caching section. Is this feature enabled by default?

Hubo wrote May 4, 2010 at 3:01 PM

Here is the test code...
add reference to aspx like:
<%@ Register Src="~/Test.ascx" TagName="Test" TagPrefix="test" %>
and
<test:Test ID="Test" runat="server" />
debug will be ok, but release will be broken...
Do not forget to click on "Add new firm" button to show up textboxes with watermarks.
I am using <ajax:ToolkitScriptManager EnableScriptGlobalization="true" runat="server" /> in master page.

lindows wrote May 23, 2010 at 2:48 PM

yeah, i seem to have the same problem with 5 of my applications,

4 are .net 4.0 and 1 is 3.5, both using the correct ajax assembly file for 40412
when deployed with source code it works fine, but when deployed as compiled web app it doesn't work and only clue i got is "Sys.Extended is undefined"
it seems any of the controls from the ajax toolkit will fail if it is to be shown on page load

the previous version that worked for me when compiled and deployed on server was 30512

please look into this

imarrero wrote May 16, 2011 at 4:39 PM

this is a headache :(