What is the best approach to deploying multiple web parts?
- Create one Visual Studio solution and add all the web parts as separate SPIs?
The thing about this approach is when one change is made to one web part, all web parts get updated since they are compiled into one dll.
- Or, create a separate solution for each web part, which in turn gives us a seperate dlls.
But do I really want 20 solutions to manage for the 20 individual web parts?
- Or individual Features?
I'm after advantages and disadvantages of each approach. (All web parts will have the same level of security and the dlls can be placed in the GAC.)