Hi Johnny,
I'd previously been using the Microsoft AJAX API, but one of the reasons I've bought Map Suite is so that I don't have to do that. You don't buy a car and then continue to walk everywhere ;-)
When I take the Virtual Earth example from the OpenLayers site and run that within an ASP.NET page I don't get the problem on a full page postback, which indicates the problem lies in the ThinkGeo wrapper around OpenLayers.
The first link I providedin my original post suggests the root cause is the DOM being manipulated before the page has completed loading. The workaround for this is to initialise the map via the onLoad() event.
Looking at the differences in the client scripts generated on first load and subsequent postbacks there is a key difference which could pose a potential problem. In the initial load the following script is generated to initialise the map:
Sys.Application.add_load(CreateAllMaps);
However on subsequent postbacks this is replaced with:
Sys.Application.remove_load(CreateAllMaps);
parserMap1.createMap();
I think all the CreateAllMaps() function does is iterate through a set of parserMap objects and call the createMap() method on each, but the differerence is that on the initial page rendering this is done via the Sys.Application.add_load() method which fires when the page has loaded.
On subsequent postbacks the call to parserMap1.createMap() happens immediately, without waiting for the page to load.
Is there a good reason for this?
Best regards,
Gary