Sharepoint development - multiple webparts in same solution, or project for each? -


i'm working on sharepoint 2010 project has quite few visual webparts.

currently have web parts in same solution. colleague working on same project, creating project each web part inside solution.

what's best practice here? advantages/disadvantages of each approach?

thanks.

i tested both approaches when started developing sharepoint solutions , conclude following pros / cons:

pros of having separate project every webpart:

  1. much faster deployment , testing of code changes <- don't have deploy webparts everytime make single change.
  2. easier , better team collaboration <- every developer works on single webpart way, everyone's code separated , there won't checkin/checkout conflicts.
  3. better code reusability, if needed @ time in future use single webpart in project find easier go , webpart project.
  4. all webpart resources in single place, webpart uses resources (resx / images) can include in it's project, imagine having big solution , resources of webparts spread around in single project, it's harder webpart use in future project because have find related resources.

i hope that's enough let enjoy webpart per project appreach.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -