Web Parts and Atlas with Beta 1

Could someone please help me with the steps required to get asynchronous drag-and-drop of Web Parts using Atlas Beta 1?

I have my own web part manager that inherits fromWebPartManager. Do I need to explicitly make it inherit from the Atlas web part manager instead? The online pre-Beta 1 tutorials on this topic (which I never got to work after several days of trying) said to add a <tagMapping> for the Atlas WebPartManager and WebPartZone. Is this still required?

I'm also using master pages and want the ScriptManager and WebPartManager to both live on the master page. Is this OK? Would there need to be an update panel in the master page since the whole content area will need an asynch refresh with web parts in the picture?

This topic seems like it would be a common question to me, so I hope someone will explain the "approved way" of combining the two.

Thank you,

Terry

I haven't read yet a successful experience with Webparts and beta1, that's why I am waiting for a future release, so I can migrate from the July CTP.

It would be nice if someone from Microsoft could respond.

I'm replying once again to move this issue to the top of the forum.

Can't someone on the Atlas team help me with this? I've seen other posts on the same topic, so I know I'm not the only one that can't this to work.