Hot answers tagged

9

As far as I know, the only way to upgrade a feature is by calling the Upgrade() method. Any other operation, including deactivation/reactivation, solution upgrade/update etc should in no way force a feature upgrade. I have upgraded some feature after a solution update in the past and they were NOT automatically upgraded by the Update-SpSolution cmdlet (I had ...


9

If the WSP has any assemblies in it - no. The assemblies developed for SharePoint 2010 will be referencing the SharePoint 2010 core assemblies, and will fail when trying to load them in SharePoint 2007. If the WSP only has XML in it, and no server side code in assemblies, it should deploy fine, given it has no Feature code that's new in 2010 (such as ...


9

Please visit this blog from Joel Oleson where he describes about SharePoint 15 and Office 15 Wave of Products !!! You can also check out for the Technical Preview Program from Office


7

I resolved the issue. It appears based on the Microsoft Knowledge Base information that: Some document-conversion services in SharePoint Server are not secure when they run in a particular environment In order to allow the services to continue to run, the following registry key needs to be added: Name: AcknowledgedRunningOnAppServer Type: DWORD Value: ...


6

Looks like you're using default Update method of SPContentType when updating your content type in feature updating receiver. To push changes to all inherited list content types, you should use another overload of the Update method, and pass true to it: contentType.Update(true); Description of the parameter from MSDN: updateChildren Type: ...


5

SharePoint doesn't delete either list or its data on feature deactivation or deinstallation, at least if it was created through CAML (Elements.xml, schema.xml). Probably you're using Visual Studio deployment in your testing environment, and it is Visual Studio who deletes the list, treating its existence as a deployment conflict. But if you re-deploy ...


5

You can install CKSDev extension using VS.NET extension Manager, if you have not already done so. It provides a project configuration called Upgrade Solution. You can switch to it by going to project properties as shown below: By going to Project’s property pages (SharePoint tab), you can also inspect what actions it takes.


5

You could loop through all the existing sub-sites with a PowerShell script, and use the feature cmdlets to activate the feature on existing sites. Using this method you could also insert some logic/conditions to enable or not enable the new feature if that is useful.


4

When you install the executable for a Cumulative Update (CU), you have not actually upgraded your servers yet. The PSConfig.exe (Command Line), or the SharePoint Products Configuration Wizard (GUI), will need to be run to upgrade both the running binaries, and make any changes to the SharePoint database schemas provided in the CU. In this case, you have the ...


4

As Chris explains in Feature upgrade (part 1) - fundamentals Feature upgrade does NOT happen automatically (including when the Feature is deactivated/reactivated)! The only way to upgrade a Feature is to call SPFeature.Upgrade() So, on first deployment you'll activate the Feature and the Feature_Activated event will run. Now you make some changes ...


4

The point here is that there are many possible upgrade scenarios, and in some cases performing historical upgrades is not desired. Instead of managing only upgrade actions, you should also keep up-to-date the main version of your feature, i.e. you should include the FieldRef elements into the content type XML. This will not interfere with UpgradeActions, ...


4

Nobody knows. Well, nobody who is talking knows. However, on January 30 Microsoft has released Office 15 and SharePoint 15 into ‘Technical Preview’, a program that allows select users to try out the new software and provide feedback to Microsoft. You can download both document sets at http://www.microsoft.com/download/en/confirmation.aspx?id=28768 and ...


4

Esteban, The .CS code is compiled into the assembly. The actual .cs file is never deployed to SharePoint, so the only thing you would need to do is rebuild the WSP solution and upgrade it. This will update the assembly, recycle the app pool, and deploy your change to any web application. Beyond that, Ashish is right that removing a solution will not ...


4

You will need to re-activate the feature that you updated. Upon re-activation, the web part should show in the gallery.


4

If you wanted to do it the "right" way then you should have used Feature Upgrading. It's unfortunately not simple but gives you a lot of control of what happens when you deploy a new version of a feature. In your case it would have involved: Add the elements.xml files for the new web parts inside <ApplyElementManifests> inside ...


4

While it is possible to upgrade features while upgrading solution, it is a very bad practice, so only consider this as a warning of how not to do it: Using -force parameter on Install-SPSolution will force solution to be installed and underlying features to be enabled even if they were already enabled. Forcing a feature to be enabled will also trigger ...


3

You cannot install SharePoint 2010 WSP on a SharePoint 2007 environment, because it references the SharePoint 2010 DLL files and the package Product Version is set to 14.0. If you got the visual studio project, you could try and downgrade the project so that it works for 2007. More information about this can be found on this blog post.


3

My understanding is that when you add a new field to Content Type while upgrading a FEATURE, you have to : Use your code (UpgradeActions/VersionRange in your question) for FEATURES already activated and need to be upgraded Add the fields to the original content types also to make sure that fresh activation also includes the fields because, it (fresh ...


3

Farm Administrators do not by default have access to Site content. Site collection feature upgrade and activation is normally delegated to the Site Collection Administrators (I think).


3

You should use Feature Upgrading to register the new EventReceiver. Just creating the code will not tell SharePoint to call the EventReceiver you have to do that in either an Elements.xml file using <Receivers> element or through code by creating a new element in the right EventReceivers collection For the following examples assume you're upgrading ...


3

im presuming that the feature is in a wsp so you should be able to do this: Update-SPSolution –Identity YourSolutionName.wsp –LiteralPath “C:\YourSolutionName.wsp” –GacDeployment http://technet.microsoft.com/en-us/library/ff607724.aspx EDIT forgot to mention you need to change the version number ;) for a more finer detail you can follow this: 1.Open ...


3

Based on the information found on this blog you actually have to attach to the PowerShell process if you upgrade your feature like you did. . Simply pressing F5 in Visual Studio will deploy the solution, launch the browser window and attach the debugger to the w3wp.exe process. However, upgrading the feature is done in PowerShell. Running the ...


2

When you retract the solution, it will not delete the list data. For similar changes (update code behind), I have redeployed the solution many times without any issue.


2

I was still having the same error, even after adding the registry entries. It turns out that the Net.Tcp Port Sharing Service was disabled, once I enabled it and started, I re-ran the Configuration Wizard again and it went past stage 5.


2

We have exactly the same case as yours, our production and beta environments are not in our hand and we have to do deployments using WSP solution package (even if those are updates to existing solutions) We also use content types, site columns and list definitions and instances, all declarative.. For the updates (I'm not sure if this is the best method but ...


2

There are only a few instances where you get any real benefit from the CompatibilityLevel having both 14 and 15. If you have a solution where you are adding ghosted files to a site, you will get health analyzer warnings that the files don't exist in the 15 HIVE if you only deploy in 14 mode. Another instance is having site definitions for both 2010 and ...


2

I implemented similar behavior some time ago, I used xml file with following structure: <?xml version="1.0" encoding="utf-8" ?> <Fields ListUrl="Lists/Test"> <Add> <Field ID="{1174073D-CD08-4A8A-A70E-5199200E04AC}" Name="TestField" Required="TRUE" Indexed="TRUE" MaxLength="255" ...


2

We found that by using PowerShell code like this [Microsoft.SharePoint.SPSecurity]::RunWithElevatedPrivileges( { $site = get-spsite "http://localhost/nonfarmadminsitecollection" }) $elevatedSite = new-object Microsoft.SharePoint.SPSite([Guid]$site.ID,$site.SystemAccount.UserToken) We are then able to upgrade the features in $elevatedSite.


2

Could you add your field manifest? Also, what does the feature receiver do? Are you using sp2010or sp2007? I havent tried with choice fields, but setting DisplaceOnUpgrade="true" instead of owerwrite="true" for field declaration helps upgrading existing fields.


2

From the comments in your question it seems that the system team used the Update-SpSolution PowerShell cmdlet. In that case they are performing a solution update which won't work to provision any new artifact. As discussed in this other question SharePoint supports two main ways to upgrade a solution: a retraction/readd cycle, also refered to as solution ...



Only top voted, non community-wiki answers of a minimum length are eligible