I have a Sharepoint 2010 application that consists of Sharepoint application pages and donot contain any web parts. So when I deploy the wsp of the application from the central administration the application will be globally deployed. I want avoid this and deploy the application on to a particular site. How do I accomplish this?
Can you use module for storing Application page and Deploy this solution as Sandbox Solution.
Sandbox solutions are not stored in File System(Physical path) and assemblies can't be deployed to Global Assembly Cache(GAC). But it's available on C:\ProgramData\Microsoft\SharePoint\UCCache at runtime. Note the ProgramData is a hidden folder.
Related
I have a sharepoint farm that has 2 WFE+1 APP +1 SQL server architecture. I have deployed a solution package which contains webparts and a few things related to site level.
It warns me that the setup files, webparts are missing in the central administration even though the solution packages are deployed the web application. BTW, there is a web application on the farm.
I have checked the below articles. But in those articles offers the deploy the solutions for whole web applications on the farm. Furthermore, one of those articles is related to search webpart and the another of them is related to default webpart in the admin_ content db. But my issue is related to custom solution files that is in the wss_content db.
https://blogs.technet.microsoft.com/christianheim/2016/09/15/missing-server-side-dependencies-errors-on-your-multi-server-sharepoint-farm/
https://sharepointsoldiers.wordpress.com/2013/04/22/sharepoint-2013missing-serverside-dependencies/
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
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!
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)
See http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/385eb454-5083-47a6-b378-615b67a065a3/
After deploying my new Sharepoint solution, containing a feature with WebApplication scope, I noticed that feature was added to ALL webapplications in the farm.
The solution was deployed to a one particluar webapplication, so I wonder if such behavior is correct. Any way to make feature appear only in WebApplication, solution was deployed to?
How did you deploy from powershell or from central admin? If you deployed from central admin you should have been given a list of web apps to deploy too, but if you did powershell and left off the WebApplication flag (http://technet.microsoft.com/en-us/library/ff607534.aspx), it would have deployed to all of the web apps.
This is unfortunately by design.
The solution is deployed to a single web application, e.g.
but the features are visible on all web applications, i.e.:
Feature /= solution. That means that some elements from the solution (not features) will appear only in the designated web application.
One workaround is to hide the feature so that users cannot activate it.
Check out also these posts:
Is it possible to deploy a solution to a web application so that its features are only visible within this web application?
Creating a solution that deploys to selected WebApplications but copies the assembly to GAC
if the solution deployed to ABC webApp so it won't deployed to another WebApp, if it happened better remove from all WebApp and deploy to ABC webApp by PowerShell command.
-
Praveen
I have a custom webpart for Sharepoint 2007. I am trying to deploy it to a new Sharepoint web application. I am using WSPBuilder with VS2010 to do the deploy. When I examine the wss\VirtualDirectories\ folder for the web app, the wpcatalog folder does not exist there. When I go to the Web Part Gallery and click "New" button, the web part is no there either. What could be causing this behavior? Are there any other ways to troubleshoot it?
Thanks.
the wpcatalog is actually a document library containing the .webpart definition files. It is stored in the content database, not the file system.
You need to verify the solution is in fact deployed to your web application, and then activate any features if necessary. You can verify the solution deployment under central administration\operations\solution management.
How can I deploy a custom authentication provider in MOSS 2007?
Is there any provided functionality to do this (like a Sharepoint feature)?
Or do I have to install it in the GAC on each box in the farm manually?
The usual approach for installing extensions like this is to use a feature, yes. However, you won't be using any specialized XML as this kind of extension is not catered for explicitly. So how can you do it? By using an essentially empty feature project that contains an Event Receiver assembly. The event receiver assembly is called automatically by sharepoint for 4 different events: install, uninstall, activate and deactivate. I suggest you hook the install and uninstall events to deploy your provider.
http://msdn.microsoft.com/en-us/library/bb862634.aspx
Make sense?
-Oisin
You can deploy a custom membership provider under minimal trust in SharePoint 2007 using Code Access Security (CAS).
Altough the author seems to not recommend using the GAC since some Sharepoint installations are on a hosted environment and you can play with GAC.
It is often easier to install the
membership provider DLL in the Global
Assembly Cache to achieve full trust,
but in cases where you're working with
a hosted SharePoint site and cannot
deploy to the GAC these instructions
should steer you right.
The detailed article is here. I hope it helps.
The Windows Live Authentication feature of the Community Kit for Sharepoint provides a nice example (with source code) of creating a solution package with a custom authentication provider. A solution package can be deployed to all servers in the farm without manually touching them