The scene is like this.
A user will visit a gameboard web site
and choose a game to play. Let’s call
it Checkers. He likes it, so then he
installs the out-of-browser app to his
desktop. He then finds Chess, and
installs that too. For both games,
while played on the site, he has stats
(games played, win/loss records,
etc.). For each game on the site, he
navigates to a different page.But now he wants to play offline and
view his stats and other cross-games
information. He wants to have a single
app to launch to play either game.
From his single out-of- browser app, he
sees that Go is also available, and he
places a checkmark against it to
download on his next connection.
Experience in developing multiple out-of-browser Silverlight applications located in a single main application? What factors need to be considered in this type of design? How does this affect the installation experience of different web pages?
You can read more about it here, here& there is an example here
I am looking for a scene where I need to create a “main” Silverlight application and then for browsing Add a “child” application to the Silverlight application outside the device.
The scene is like this.
A user will visit a gameboard web site
and choose a game to play. Let’s call
it Checkers. He likes it, so then he
installs the out-of-browser app to his
desktop. He then finds Chess , and
installs that too. For both games,
while played on the site, he has stats
(games played, win/loss records,
etc.). For each game on the site , he
navigates to a different page.But now he wants to play offline and
view his stats and other cross-games
information. He wants to have a single
app to launch to play either game.
From his single out-of-browser app, he
sees that Go is also available, and he
places a checkmark against it to
download on his next connection.
Does anyone have any experience developing multiple out-of-browser Silverlight applications located in a single main application? What factors need to be considered in this type of design? How does this affect the installation experience of different web pages?
What you need is MEF (it will be included in the CLR of the upcoming Microsoft .NET Framework 4)
You can read more about it here, here& there is an example here