Home - Forums-.NET - FlyTreeView (ASP.NET) - Javascript error when expanding node

FlyTreeView (ASP.NET)

Technical support and KB related to the FlyTreeView control

This forum related to following products: FlyTreeView for ASP.NET

Javascript error when expanding node
Link Posted: 14-Oct-2005 07:15
I have a tree instantiated in a page. It has four nodes at the top, all with a NodeSrc pointing to a page with a FlyNodeSet in there.

When I click on any node to expand it, I get a message in an IE (6) window:
Error while parsing data. The download of the specified resource failed
.

I click on OK to close the window, and I find myself with Visual Studio complaining about a Microsoft Jscript runtime error: Exception thrown and not caught, and pointing to the line in FlyTreeView.htc's function o61 with a throw statement in it.

The Page_Load() event of the page containing the FlyNodeSet does not even get called; it dies before.

This used to work fine with the Trial version 3.5.something.

I just upgraded to the Single Developer licence v3.5.17.0, and it no longer works.

Anything special I had to do to upgrade ?

I'm stuck...  
Thanks for your help.
Pyt.
Link Posted: 14-Oct-2005 21:44
Error while parsing data. The download of the specified resource failed

This error typically occure when the XML data is not valid.
Please check the NodeSrc url. And try to download this XML data in a separate window. It may just fail with some exception and that's why flytreeview cannot parse it as XML.

Anything special I had to do to upgrade ?

Typically you should uninstall trial version, install retail one and rebuild your project.
Link Posted: 15-Oct-2005 02:02
[quote="EvgenyT"]And try to download this XML data in a separate window.


Thanks for the hint. I had not thought about that. Looks I had several definitions of the FlyNodeSet, due to several versions of the FlyTreeView dll in GAC (the old trial version and the retail one), plus a bunch of  directives referencing the trial version (3.5.5) rather than the retail 3.5.17.

It's back to working fine, now. Thanks again.

Pyt.