Hi naspence,

I followed the steps you suggested and was unable to reproduce the behavior you're describing.  I added a WebExplorerBar and handled its ItemClick server side event and set its AutoPostBackFlags.ItemClicked to On.  I added a label to help keep track of how many times the event was run.  When I ran my sample in IE8, Firefox 12, and Chrome 19 and clicked the item, the label only changed once on each browser.

It may help if you could provide more information regarding how you are testing this and how you are posting back to the server.

I have attached the sample project I used to test this.  Please test this project on your PC; whether or not it works correctly may help indicate the nature of this problem.

If the project does not work correctly, this indicates either a problem possibly specific to your environment, or a difference in the DLL versions we are using.  My test was performed using version 12.1.20121.1005 in NetAdvantage for ASP.NET 2012 Volume 1.

If the project does show the product feature working correctly, this indicates a possible problem in the code of your application.  It will help if you can provide a small, isolated sample application that demonstrates the behavior you are seeing.

Or, if this sample project is not an accurate demonstration of what you're trying to do, please feel free to modify it and send it back, or send a small sample project of your own if you have one.

Please let me know if I can provide any further assistance.

Hi naspence,

Thank you for the update.  I'm glad to hear you were able to work around this with the WebDataMenu.

I can look into this over the next week and perform some tests with the information you've provided.  I'll let you know if I come up with anything helpful.

If you have any further questions, please let me know and I'll be glad to help.

Thank you for your response.

Your sample application works fine for us.

We've decided to use the WebDataMenu instead for these specific menu items so we can work around the issue.

Unfortunately, providing a sample application that exhibits this behaviour is going to be difficult due to the comlex nature of our application.

Just so you're aware, we are using the .net framework 2 and a master page with an asp script manager control (not your own WebScriptManager) maybe that's a clue?

Additionally, we also derive from the WebExplorerBar so that we can easily make application wide customisations.

Since we have a work around, feel free to close this (for now).

Regards.