ComponentArt 2006.1 and Atlas

I was testing the ComponentArt menu control with a site that has March CTP Atlas installed. I am seeing some very strange behavior. I originally tested the menu control with a single page and no Atlas stuff enabled. It worked as expected. Then I put the menu control into a master page with

<atlas:ScriptManagerID="SM1"runat="server"EnablePartialRendering="true"/>

Now the functionality of the menu and the updatepanel contents is at best inconsistent. Within a single updatepanel located on a content page I have a dropdownlist that has an event and a submit button that has an event. Neither event fires. If I remove the menu control, all works correctly again.

When both the menu control and scriptmanager are in the master page, even pages that don't have any atlas functionality don't work correctly. If I remote the scriptmanager, these other pages work successfully.

I am suspicious that these two items, ComponentArt and Atlas, are beating against each other for AJAX type functionality. Has anyone else had any success using both of these together?

Thanks, Mike

I had the same problem with the same setup, Master Page, Component Art 2006.1 Menu, where all worked fine on localhost, then strange problems you describe showed up on the live site.

The problems were event different when using different browsers. I am back to Feb CTP of Atlas.

I take it from the fact that you are back to using the Feb CTP, that the issue does not appear with it.

I wonder if the Atlas team is looking into this. I hate to start using these two together and find out that the release version of Atlas still has the issue with ComponentArt. By the way I test Telerik's menu control and it did not show the same issue. So it must be something specific between these two.

Thanks,

Mike