We are using a structure with multiple levels of nested master pages.  It would be pretty difficult for me to re-create a sample to send that would simulate what I’m experiencing.   Suffice it to say that we have WebPaneManagers at each level of the master pages that break the screen real estate into more granular containers. 

Our main master page has this layout:

+-----------------------------+

| Caption                     |

+---------------------+-------+

|                     |   L   |

|                     |   I   |

|         Content     |   N   |  

|                     |   K   |

|                     |   S   |

+---------------------+-------+

We then have what we call a Profile Master Page that nests inside of the Main Master page’s content area.  Its layout is as follows:

+-----------------------------+

| Sub-Caption                 |

+-----------------------------+

| Page Menu                   |

+-----------------------------+

| Tab Control with mult. Tabs |

+-----------------------------+

| Menu specific to sel. Tab   |

+-----------------------------+

| Content                     |

|                             |

|                             |

|                             |

|                             |

+---------------------+-------+

The final master page nests inside of the content area of the Profile Master Page and is laid out as follows:

+-----------------------------+

| Caption                     |

+--------------+--------------+

| Microsoft    |  Pane with   |

| Templated    |  info        |

| GridView     |  specific    |

| Control      |  to          |

|              |  selected    |

|              |  grid row    |

|              |              |

|              |              |

+--------------+--------------+

The WebPaneManager control seems to work quite well in most of the areas of our application; however, the couple of pages I'm having difficulty with have Microsoft Templated GridView controls in the WebPanes.  When the "Edit" link in these grids is clicked the postback occurs as expected and you can debug completely through the C# code to the point where control is handed back to the browser.  It is at that point that IE goes into some sort of infinite loop that occasionally recovers.  On those occasions where IE does recover it takes approximately 60 seconds for the loop to terminate and the browser to return to a normal state. 

I backward tested the same code with the 2008 Intersoft Suite and those problematic pages work flawlessly.  These are all relatively mature pages that worked great on the prior release.  We caught this strange behavior during regression testing after the 2009 upgrade.  I’m assuming that some sort of change crept into the latest Intersoft release that is causing the issue.

Would it be possible for me to use the 2008 WebDesktop assemblies and JavaScript files in conjunction with the newer assemblies for the other modules (e.g. WebGrid, WebInput, etc.) until this issue is resolved?  Or would there be some incompatibilities?

Thanks in advance,

Jerry

I'm experiencing the same issue on my deployment.  I have all of the DLL's you mentioned above in the project bin folder, I've run the deployment manager to setup the license keys in the web.config, I've verified that the web.config also contains the proper defitions for using SmartWeb resources.  I've also copied the CommonLibrary folder on my production machine and created a "Virtual Directory" for the site called CommonLibrary which appears along the with other folders on my project.  Am I missing something else?  According to the documentation this is all I need to do for a project with SmartWeb resources.  My deplyment server is Windows Server 2008

Thanks,

Jerry