New answers tagged feature
If you are using visual studio ultimate to develop your feature IntelliTrace would be an option. IntelliTrace team done a great job to plugin SharePoint events with IntelliTrace .
In order to make ULS logging work for a AppPool account that is not Administrator you have to add your AppPool user to "Performance Log Users" group. And restart the Application Pool that is using this AppPool account.
You really shouldn't be debugging in production. Instead, add additional logging capabilities to your app and do more defensive coding. By defensive coding, I mean that if your code is calling some method to get an object, check to see if you got the object before doing anything with it.
i know it is a bit late but i was just involved in a similar Scenario: I used the MembersWebPart in SharePoint 2013 and this is a working example: <WebPart xmlns="http://schemas.microsoft.com/WebPart/v2"> <Assembly>Microsoft.SharePoint, Version=18.104.22.168, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly> ...
The dependent feature and the dependee feature should have different GUIDs. Your code sample shows both features having same GUID. Here is an example: <Feature Id="GUID1" Title="Feature Title" Description="Feature Description" Version="22.214.171.124" Scope="Site" Hidden="false"> <ActivationDependencies> <ActivationDependency FeatureId="GUID2" /> ...
Top 50 recent answers are included