Hi Shawn,

I don't suggest you to use button for your scenario. But maybe use some options control such as DropDownList. Also it could not do in client side/flypostback. You will need to do this in FullPostBack.

Attached is my simple sample to show you how i bind it with another node. Hope this helps.

Regards,
Handy

I need to use a button. Why can't I use a WebButton or any other control that calls a POSTBACK and/or AJAX callback? I tried using FullPostback and the TreeView didn't update. I also tried using a standard ASP button but got the same result.

However, I can use a WebButton with FullPostback and update a WebTreeview if it is not integrated with a WebCombo. Can you please confirm?

I found another bug. Similar to the page I modified above to illustrate another bug but this TreeView does not load on demand. Using the TreeView's Nodes property, only the first level exist. For example: 

ISGetObject("treePortfolioNav").Nodes .length (3 is returned; Correct value)

ISGetObject("treePortfolioNav").Nodes[0].Nodes.length (0 is returned; Incorrect value)

ISGetObject("treePortfolioNav").GetArrayNodes() (38 is returned;)

ISGetObject("treePortfolioNav").Nodes[0].Nodes.length  (2 is now returned; Correct value)

Why would GetArrayNodes cause the rest of the collection to "load"?

Hi Shawn,

It's true, but what we suspect is there's a conflict between your css with our control. For example in my end I used the same sample that I gave you and the performance didn't increase but when you tested and modified the sample by adding your css the performance is bad. That's why I suspect that probably there's a conflict between our control and your style but then again it's just my suspection.

Frankly say that I cannot replicate the issue in here without your css therefore I really need you to send the css that you add in my sample, if you dont want to send it by forum, you can send it to my email(handy@intersoftpt.com) so I can immediately replicate the issue and forward it to our development team so they can fix the issue.

Best Regards,

Handy

This is getting frustrating.  Please compare the original with the modified to see that the changes are not just CSS but I added a WebMenuBar, another WebPane, etc.. In fact, I removed the CSS that exists within the WebMenuBar so we can get away from blaming the CSS because the performance bug still increases from 4-5 seconds to nearly 25 seconds.

You have everything you need in the provided solution. You can replicate it in the solution very easily as I have explained in my posts above:

Compare the page load with and without the WebNavBar rendering (Set Visible=false). Confirm the performance bug exists.

Compare the page load with and without the WebGrid's AutoFitColumn property (true/false) with the WebNavBar rendering on the page. Confirm the performance bug exists.

Remove every CSS you can find in the WebNavBar and the WebGrid. NO EXTRA CSS. Confirm the performance bug exists.

If I remove the WebMenuBar, the performance comes back. However, I am still skeptical that other performance bugs exist. 

Ok. I understand your situation. As you can see in my recording, the performance works well, right?
In fact, I have used all latest hotfixes in this modified project. Also, after it got cache, the page is loaded just within 10s in my environment.
Please let me know your environment details (pc environment (32 bit or 64 bit) or the browser you used) and send me your html out put when you view source.
I got news from our developer that it's true that at the past, some styles can be slower performance at browser, that's what we fixed or changed at framework and Webdesktop level.

e.g at the past, there's an issue slow performance if WebMenuBar applied many styles.

Regards,
Handy

We run both 32 and 64 bit and typically use IE7-IE8.

Also, I don't think the problem here is styles (CSS) because this same code base was much faster in the 2008 RC release.  It was never "fast" but a 14 second to 1 minute+ performance increase is easily noticeable and not acceptable to our users.  Furthermore, if you remove the styles within the WebMenuBar, it is still slow.  It only becomes faster if you change the WebMenuBar's IntegratedTo or the WebGrid's AutoFitColumn property to true.  I am not sure how either of those would remove styles on the page.

It is also interesting to note that if you remove the code to dynamically add items to the WebMenuBar, it becomes faster again. Even *1* item in the WebMenuBar has a major performance hit.

At this point, we are in a criticial spot because we have a production release that includes the 2009 R1 SP1 Refresh and we cannot release it with these problems.

1) Do you have a workaround?

2) Do you have a timeline for when these bugs will be fixed?

Thank you for your help. It is very much appreciated.

Hi,

I ran the modified project you sent me. I wonder why the result is different from yours. Please see my recording. I never got 1 minute or something. Maybe your computer cache can affect on the performance or something. Please try to remove IE cache and asp.net cache at C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files. Then try to rerun again. For the first time maybe it would get slower because there is no cache of the current page. Please let me know an update that can help me more investigate the issue.

About the render issue, i can also replicate it. I will forward this to our developer. 

Regards,
Handy

The page that takes nearly 1 minute to load is another page within the application that is similiar to the modified project I sent.  I made reference to the load time to illustrate the performance problem that appears to be related to the WebDesktop (WebPaneManager/WebPane/WebMenuBar/etc.) and/or the WebGrid.  I am not sure where the problem is coming from but it's easily duplicated with that modified project. Again, I am not sure how it's related but the peformance problem goes away when the IntegratedTo property is removed (but the WebMenuBar style goes away) and/or the Grid's AutoFitColumn property is set to true (We prefer false to set our own widths).

Can you please reply with a timeline as this is very crucial to our application. We are currently planning to rollback the 2009 R1 SP1 release to the 2008 R2 that doesn't have these performance issues if there is no resolution within the next day or so.