Running modules independently

Topics: Prism v4 - Silverlight 4
Feb 24, 2011 at 1:51 PM


As I can tell the modules in Prism v. 4 is themselvs Silverlight Applications, that is not Library Projects as they contains App.xaml file and so on. Why is this?

I guess the usage of modules as XAP-files may be one reason? The other reason may be that I can be developed and run independently of the shell? But with the registration of views into regions kills that, right?

Could anyone shed some light on this issue?

PS! I'm a newbie to Prism so handle me with care... ;-)

Feb 24, 2011 at 3:52 PM
Edited Feb 24, 2011 at 3:52 PM


Silverlight modules in Prism can be either Silverlight Class Libraries or Silverlight Applications. The main reason for using applications over class libraries is that the Silverlight Application template outputs a xap file by default. You can read more about this in the following thread:

How to have XAP against every module

However, regardless of whether it is a class library or a Silverlight Application, a module isn't intendede to be run in a stand alone fashion. You might find the modularity chapter from the Prism MSDN documentation useful to further clarify on this.

I hope you find this helpful.

Guido Leandro Maliandi

Feb 25, 2011 at 12:11 PM

Thanks for your answer. So in order to clear up my code and remove some deadwood I could just delete the App.xaml and App.xaml.cs files then?


Feb 25, 2011 at 2:12 PM

That's right, you could remove those files as they're not necessary for the modules.

I hope you find this helpful.

Guido Leandro Maliandi