Hi All,
I am growing concerned as I walk through the Quickstart guide on how the Silverlight MapSuite component is implemented. It seems that by creating the server side rendering (we will NOT be pushing map data to the client) connection between the aspx page that launches the map enabled Silverlight application and the application itself, it would creating overhead for the non map enabled portions of the Silverlight app. I would have preferred to have seen the server side mapping service seperate from and pointed to via a property of the XAML Map object. But - that does not appear to be the case...
The short story is that we are porting a LOB application currently in ASP.NET with the ASP.NET AJAX version of MapSuite into Silverlight. Mapping is a small but important piece of the application that only is used in certain screens, not the entire application. So my questions are:
1) Is there overhead or problems associated with running your entire application with the Map Connector always there?
2) Is there something I am missing and there is a way to point a map to a service?
3) Does anyone else have a similar situation or implemented something akin to what I described above?
Thanks for any feedback or hopefully clarifications to my minute understanding of how Silverlight MapSuite works!
Justin