deploying web parts sp2013 in bin folder vs gac pros and cons RRS feed

  • Question

  • we would like to know deploying web parts sp2013 in bin folder vs gac pros and cons.

    I think only event receivers and timer jobs can not be in bin and other custom code can be.

    MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

    Tuesday, October 4, 2016 10:16 AM


  • Pros:

    - Tighter control of where web parts can be used.  The bin folder will limit the web part to a single web application

    -CAS security policy can be used to limit what a web part can do


    - CAS security policy file will need to be manually edited

    - WSP manifest file will need to be edited for alternative deployment location

    - Not sure about this, but I don't think the automated [F5] debug will work with this kind of deployment.

    - Potentially multiple copies of the same code running from different locations (minor performance and memory drain)

    In short, yes there are some advantages in terms of control.  But those advantages are not normally needed and it does require a significant amount of manual effort to develop and deploy.  There is no real difference in terms of the code.

    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    • Marked as answer by Dennis Guo Friday, November 11, 2016 6:54 AM
    Tuesday, October 4, 2016 11:24 AM