We are working on LoB app with lot's of content. XAP download will be rather large I think for one time download. I'm planning to break solution into separate projects.Not sure why - but I DO NOT like many many projects in solution. IMO it is not very good idea. Even when we were working as a large team - it was pain with many projects. Even now when I'm using MEF/PRISM - there still going to be some core dependencies like:PRISM librariesInterfacesNavigationShell/BootstrapperApp stylesConverters/Commands/Validatorsetc.And than I'm going to have modules that will use all that CORE stuff. Modules will have following inside them:RIA Services client sideViewModel'sViewsThose modules will be loaded on demand using MEF. I think size-wise all those modules will be larger than core module because of ammount of logic in them. I expect to have about 5-6 modules and CORE. I think that will give me reasonable number of client-side projects and libraries/XAPS and it will be manageable solution to work with.Do you see any issue with breakdown like this? Some online videos will make 7+ projects out of CORE module. What's a point? I think it adds to complexity. Than they show 3-4 DLL out of module. One for views, one for viewmodels and so on. They still need to be loaded together so why?I'm looking for do's and dont's from you guys who went through this..Thank you!
Silverlight - modularity. Best way to physically separate binaries?
architecture;silverlight;enterprise architecture
Why do you feel that a solution with multiple projects is a BAD IDEA?If your only doubt about this approach is that the solution will become cluttered then you can simply create multiple solutions, each with a different development perspective.Solution == Perspective ApproachA solution is merely a collection of projects and defines building a series of projects.  In my project setups I will typically have a Server side Solution, Business Entity Solution, a number of different Presentation Layer solutions and a Master solution that builds all projects.Projects in the Server Side Solution may be in the Business Entity Solution as well.  This way developers only need to develop in the solution/perspective which is applicable to them.  This avoids the clutter of large numbers of projects.