Sunday, March 11, 2012

Debug.traceDump generates Sys.InvalidOperationException

nevermind, this was an exception generated by my code and not when Debug.traceDump was called.

But now, the problem is "Debug is undefined"


In Atlas 1.0 RTM, "Debug" has been renamed "Sys.Debug".

-Mike


I get always an error that Sys.Debug is null:

1 parsePadding : function(padding) {2/// <summary>3 /// Parses a padding string into a pixel size4 /// </summary>5 /// <param name="padding" type="String" mayBeNull="true">6 /// Padding to parse ('inherit',px unit,null,'')7 /// </param>8 /// <returns type="Number" integer="true">9 /// Number of pixels in the padding10 /// </returns>1112if(padding) {13if(padding =='inherit') {14return 0;15 }16 var unit =this.parseUnit(padding);17 Sys.Debug.assert(unit.type =='px','A unit type of ' + unit.type +' is invalid for parsePadding');18return unit.size;19 }20return 0;21 },In line 17.
What might be wrong here? That happened since the last update today.


Where is this "parsePadding" function defined? Is it in your code, or maybe in the AJAX Control Toolkit? If you are using the Atlas 1.0 RTM, then Sys.Debug should be defined. You can check the debug version of MicrosoftAjax.js and ensure it is defined there.

-Mike


The AjaxControlToolkit, but the problem is solved as of this minute. The IE was using an old cached version of some javascript files, after wacking out all temporary files it works.
thanks mike. looks like I was one day too early. all the docs are nice and updated now!

No comments:

Post a Comment