Accessing CollapsiblePanelProperties

Hi all,

I see there has been alot of discussion in this area but i have been unable to find a definitive yet simple solution to my prob. Basically all i want to to is set a property of a CollapsiblePanelProperty from a page load event, Simple?

PageLoad....

if (someCondition)

{ CollapsiblePanelProperties1.Collapsed = false;}

Thought this would be done like other ASP controls but ?? Any one have any pointers?

Cheers, Ryan :)

Could anyone help? I'm still stuck :(

Access denied cross-domain issue, 10920

Hi,

I'm using the lastest toolkit (10920) and was wondering if the best solution for the access denied cross-domain issue are still:

http://weblogs.asp.net/bleroy/archive/2007/01/31/how-to-work-around-the-quot-access-denied-quot-cross-domain-frame-issue-in-asp-net-ajax-1-0.aspx

&&

http://blogs.msdn.com/delay/archive/2007/02/05/safely-avoiding-the-access-denied-dialog-how-to-work-around-the-access-denied-cross-domain-iframe-issue-in-the-ajax-control-toolkit.aspx

TIA

Anything that works for you must be the best solution.

About Sys.WebForms.PageRequestManagerParserErrorException error

Hello everybody,

My ajax powered web site throws an error when pressing a button or linkbutton inside an UpdatePanel.

I've searched for a solution. All of the blogposts, solutions etc is about the "common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled." suggestion written in the error text itself.

But in my scenario, only IE6 (and may be below) users see this error. I am using IE7, and my site works like a charm. (all my friends using IE7 doesn't have problems with the site)

I've searched my code for response.write stuff but there isn't any. I've removed some custom controls (msn like popup win, flash container controls etc.) but it's the same with IE6 users. The error is :

--------
Microsoft Internet Explorer
--------
Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.

Details: Error parsing near 'eTitle||Favorilerim|

0

'.
--------
Tamam (OK)
--------

Anybody have suggestions?

Hi bsarica,

Maybe this article is useful for you:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q312496

Regards,

I forgot to mention smthng.

It is not working on firefox too.

Any other suggestions? :(

I had a very similar error when I encountered code where the asynchronous call back was making a call to Server.Transfer(). I'm not sure whether or not this helps you or not, but doing a Server.Redirect() fixed the problem for me.

ABCs of compiling the AtlasControlToolkit source

Hello,

I was able to successfully change a few small items in the July CTP, build and use the binaries in a web solution. Very nice!

But the latest Sept. AtlasToolKit has me stumped. First of all, there is one less DLL (microsoft.AtlasControlExtender.dll) after I build and I wonder how this effects my old code. Also, when I remove the reference to the old DLL in VS an unknown process retains a lock on some files from the old referenced Atlas.

After I build the AtlastToolKit solution and add a reference to the TWO generated DLL's in VS everything looks fine within VS, no errors or missing references there. But when I run the code the Atlas portion simply does not work giving a simple JavaScript error "object does not exist"

So, my question is: Is there an FAQ or basic run down of how to transition from one version of Atlas to another...especially if we have modified some of the older versions scripts and code?

Hi,

all the code in Microsoft.AtlasControlExtender was moved into the AtlasControlToolkit namespace (this means that the source is now public), thus a required step is to replace all the references to Microsoft.AtlasControlExtender into references to AtlasControlToolkit. This has to be applied also in the JavaScript behaviors (look at the registerClass() function at the end of the file) that must inherit from AtlasControlToolkit.BehaviorBase.

Great, that helps a bunch.

Another question then, if I wanted to compile the source and NOT have the JS files as an embedded resource but instead use something like the SCRIPTPATH= , how do I build the AtlasControlToolkit? Ideally, this would also allow me to have a directory of JS files to debug against as well.

thanks!

Hi,

I don't know if it is possible to compile the Control Toolkit to reference external files. What you can do is reference an external JavaScript file when declaring an extender, via the ScriptPath property of the extender control.