Tag Info

New answers tagged

0

Leave your solution as it is and just add an 'Empty Element'-Item. Click on that item in the solution explorer and than double-click on the three-dots-button for the "Safe Control Entries"-Collection. There add a safe control entry. You can leave the values at proposed by visual studio. Now add that Empty Element-Item to your solution just by moving it to ...


1

You can go to the webpart gallery and check whether webparts are there first. If not, then you have to make sure you run as admin the PowerShell as well as try including the user as farm admin. There can be errors sometimes which occur only when activating the feature but not when installing the solution. So try running the script for just to add the ...


0

First thing is take backup of your wsp and rename it to say mywsp.cab . This will show you a zip file with all the items in wsp . Check if the desired webpart is there or no . If the webpart is present : Goto central admin -> System settings->Manage farm solution Retract and remove your solution which you deployed . Copy the wsp under above folder like ...


1

If the solution contains an assembly, only a site collection administrator can deploy it. If the solution does not contain an assembly, a user who has the Full Control permission level at the root of the site collection can deploy it. http://technet.microsoft.com/en-us/library/ee721992(v=office.14).aspx Now Fix to this problem. Add the account into Site ...


0

You can choose Run as different user in Visual Studio and give a site collection admin's credentials when starting Visual Studio. Else you can add the current user as a site collection admin and proceed further.



Top 50 recent answers are included