Tag Info

New answers tagged

1

Usually when you do retract on Visual Studio it deactivates features first. If your content type is already being used in some library or list, this content type will not be deleted. First of all you should delete every list with this content type, even from the site collection recycle bin (IMPORTANT!). After this you should successfully retract you solution ...


0

Here another solution that I have tried successfully: In SharePoint 2010 Management Shell run net stop "SharePoint 2010 Timer" and thereafter run net start "SharePoint 2010 Timer" Go back to retract the solution


1

First you should prepare the list of solutions that are deployed in your local machine. For that you can go into Central Admin - System Settings - Solutions From here list down the WSP names. Now you can use following PowerShell to download each WSP to your local folder $farm = Get-SPFarm $file = $farm.Solutions.Item("wspfilename.wsp").SolutionFile ...


0

Verify your core resource file at following location: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\Resources See if you can find entry for "True_Unless_Jpn". If not, create one and save. Hope this helps!!


0

I was facing the same issue recently. To solve this, I just removed the entries in 'Safe Controls' and 'Class Resources' section and saved 'Edit Existing Assembly' form. Then, it got deployed without issue.


0

When you deploy the WSP containing a feature using Visual Studio for the first time, it will automatically install and activate the feature. So code in feature activated event is getting called. Or if the list is created using List definition it will get created. Any subsequent deployment through Visual Studio first results is deactivating the feature, ...


0

The other option is create the list using list instance XML and it to the feature to created on activation. Then in feature activation method you can updated it accordingly. Note: First it will create the list if not exists and then fires featured activated method.


2

In your feature receiver, you can have the method to update the list first, and if getting this list throws an exception, you create it. Below is a "pseudo" code for how you might approach it: protected void ProcessList(){ try{ var list = //code to get list from SPWeb. } catch(exception ex){ CreateList("ListTitle"); } finally{ //do something } } ...


1

Go to Package.package in your project and double-click it. Click the "Advanced" tab Click "Add" and "Add Existing Assembly.." Click the "triple-dots (...)" Navigate to your project folder and then to the .dll in the bin-folder and click "Open" That should be it



Top 50 recent answers are included