title: What type of project should I create if I want them to act as individual modules in Prism WPF?
body: <p>I'm having some issues using an App.config file to load modules as outlined in <a href="https://stackoverflow.com/questions/29995215/wpf-prism-modules-not-being-initialized-using-app-config-method">another question I started</a> and was thinking through what the issue might be. I'm using <a href="https://www.youtube.com/watch?v=ni5YuyYR8-Q&amp;index=5&amp;list=LLwJkr8C5p2x04YxVJ6I6ajQ" rel="nofollow noreferrer">Mike Taulty's Prism tutorial</a>, in which you create individual projects within the solution to act as containers for the modules.</p>
  
  <p>Some of the projects are created as a Class Library, while others should be console applications. I have my main project (with the Shell, Bootstrapper, etc) as a Console Application, but I ran into an error stating "[the project] does not contain a static 'Main' method suitable for an entry point" when setting the sub projects as Console Applications.</p>
  
  <p>My solution? Set them up as Class Libraries instead since it gets rid of the error! I think it's possible that the modules aren't loading because they're Class Libraries, but I have no idea since I'm so new to all of this. Any insight would be much appreciated!</p>