This question is locked. New answers and comments are not allowed.
Hey there,
In my background agent I'm updating the front of a WP7.8 FlipTile, i.e. I'm preparing three controls (SmallVisualElement, VisualElement & WideVisualElement) for the front of the tile and I'm passing the data to the UpdateTile method of the LiveTileHelper.
However, since the update routine is quite complex and already takes a lot of memory, it fails due to the memory constraints of the background agent (whereas it work perfectly within the limits when using WP7.1, which requires only one control per tile).
As a workaround I'm storing the control in a static field and render it one by another in different sizes, so that at any time only one control has to be loaded in memory. Since RadFlipTileData.CreateTileData() is calling LiveTileHelper.SaveImageFromVisual(), I made the latter method public and call it consecutively from my code.
So, my suggestion would be to make LiveTileHelper.SaveImageFromVisual() public in case you don't have a better solution ;)
In my background agent I'm updating the front of a WP7.8 FlipTile, i.e. I'm preparing three controls (SmallVisualElement, VisualElement & WideVisualElement) for the front of the tile and I'm passing the data to the UpdateTile method of the LiveTileHelper.
However, since the update routine is quite complex and already takes a lot of memory, it fails due to the memory constraints of the background agent (whereas it work perfectly within the limits when using WP7.1, which requires only one control per tile).
As a workaround I'm storing the control in a static field and render it one by another in different sizes, so that at any time only one control has to be loaded in memory. Since RadFlipTileData.CreateTileData() is calling LiveTileHelper.SaveImageFromVisual(), I made the latter method public and call it consecutively from my code.
So, my suggestion would be to make LiveTileHelper.SaveImageFromVisual() public in case you don't have a better solution ;)