SharePoint 2007 WSP Deployment Best Practices
https://stackoverflow.com/questions/13039496
-
14-07-2021 - |
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianQuestion
I'm building a few WSPs (a custom web part and a branding wsp both scoped to site collection level) using WSP builder on VS2010. Our SharePoint 2007 Farm contains two Web applications.
I'd like to know whether deployment of a WSP to a particular web application (Web App A) will only recycle the application pool for that given web application (Web App A). And that the other web application (Web App B) would be unaffected during this process.
What I want to ensure is users of the other web application won't experience any down time in anyway during this release and that the wsp appears only in one Web App when viewing the site collection features lists.
Does this type of deployment only cause app pool recycling or does IIS get reset too?
Many thanks in advance
Solution
The WSP deployment only recycles the app pool containing your site collection, as opposed to an iisreset which resets all app pools.
Users of the other web application will experience down time during this deployment only if the two web applications share the same app pool (unlikely in best practice SharePoint setup).
The WSP will appear only in one site collection features list, the site collection where it was deployed.
WSP Builder is a good tool to use in VS2010 for SharePoint 2007 deployment, the tool is correct in terms of paths and naming and can be trusted!
OTHER TIPS
Visual studio 2010 and wspbuilder 2010 will possibly give you an incorrect structure or naming. Just thinking about the 14 hive and the 12 hive. I might be wrong but worth a check.
However back to your question.
Adding a solution(WSP) to the farm should have any impact on what the users see.
Deploying the solution causes the Application pool of the given web application to recycle. Remember that(i have seen this) some places host many on one application pool meaning you will effectively see anything attached to that application pool suddenly become slow/ unresponsive for a short period of time.
Theoretically as long as Web App A and Web app B are on seperate application pools you should only see one or the other affected ( depending where your deploying)
