Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Web parts are ASP.NET controls that can be added to web part zones. They are generally distributed through the deployment of .WSP files. Pre-2013, they could be developed off the hosting server. With 2013, Web Parts for the most part have to be developed on the hosting server for proper library inclusion.
0
votes
1
answer
479
views
SharePoint 2010 One of two web front ends have broken Audience on web parts
I have encountered a problem with Audiencing in our SharePoint 2010 farm. Hopefully someone out here has encountered this before.
We have 2 web front ends (web1 and web2) 1 app server (app1) and a c …
0
votes
SharePoint 2010 One of two web front ends have broken Audience on web parts
This issue was resolved by running the SharePoint 2010 Products Configuration Wizard on the specific web front end that was causing the problem. I am still researching the root cause of this incident …