%3CLINGO-SUB%20id%3D%22lingo-sub-509835%22%20slang%3D%22en-US%22%3ERunning%20SharePoint%202013%20in%202010%20mode%20and%20solution%20%26amp%3B%238220%3BCompatibilityLevel%26amp%3B%238221%3B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-509835%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3E%20First%20published%20on%20TECHNET%20on%20Jul%2022%2C%202013%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EThis%20post%20is%20a%20contribution%20from%20Vitaly%20Lyamin%2C%20an%20engineer%20with%20the%20SharePoint%20Developer%20Support%20team.%3C%2FP%3E%0A%3CP%3ESharePoint%202013%20allows%20users%20to%20run%20sites%20in%20SharePoint%202010%20mode.%26nbsp%3B%20In%20this%20scenario%2C%20the%20solution%20(WSP)%20deployment%20needs%20to%20be%20deployed%20with%20the%20%E2%80%9CCompatibilityLevel%E2%80%9D%20flag%20set%20to%20%E2%80%9CAll%E2%80%9D%26nbsp%3B%20or%20%7B14%2C15%7D.%3C%2FP%3E%0A%3CP%3EWhen%20deploying%20the%20solution%20from%20the%20Central%20Administration%20UI%2C%20there%E2%80%99s%20no%20option%20to%20set%20the%20%E2%80%9CCompatibilityLevel%E2%80%9D%20flag%20and%20therefore%20the%20deployment%20job%20reverts%20to%20using%20the%20%E2%80%9CSharePointProductVersion%E2%80%9D%20attribute%20in%20the%20solution%20manifest.%26nbsp%3B%20Since%20the%20%E2%80%9CSharePointProductVersion%E2%80%9D%20attribute%20can%20only%20be%20set%20to%20a%20single%20number%2C%20solution%20deployment%20from%20CA%20is%20limited%20to%20using%20that%20number%20for%20the%20%E2%80%9CCompatibilityLevel%E2%80%9D%20setting.%3C%2FP%3E%0A%3CP%3EThe%20suggested%20method%20for%20this%20type%20of%20deployment%20is%20to%20use%20PowerShell%3A%3C%2FP%3E%0A%3CP%3E%3CEM%3E%20Install-SPSolution%20%E2%80%93Identity%20Solution.wsp%20%E2%80%93GACDeployment%20%E2%80%93CompatibilityLevel%20%7B14%2C15%7D%20%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3EResources%3A%3C%2FP%3E%0A%3CP%3E%3CA%20title%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fee617150.aspx%22%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fee617150.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fee617150.aspx%20%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20title%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fff607534.aspx%22%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fff607534.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fff607534.aspx%20%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20title%3D%22http%3A%2F%2Fblogs.technet.com%2Fb%2Fmspfe%2Farchive%2F2013%2F02%2F04%2Fplanning-deployment-of-farm-solutions-for-sharepoint-2013.aspx%22%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Fb%2Fmspfe%2Farchive%2F2013%2F02%2F04%2Fplanning-deployment-of-farm-solutions-for-sharepoint-2013.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%20http%3A%2F%2Fblogs.technet.com%2Fb%2Fmspfe%2Farchive%2F2013%2F02%2F04%2Fplanning-deployment-of-farm-solutions-for-sharepoint-2013.aspx%20%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EHTH!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-509835%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20published%20on%20TECHNET%20on%20Jul%2022%2C%202013%20This%20post%20is%20a%20contribution%20from%20Vitaly%20Lyamin%2C%20an%20engineer%20with%20the%20SharePoint%20Developer%20Support%20team.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-509835%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

First published on TECHNET on Jul 22, 2013

This post is a contribution from Vitaly Lyamin, an engineer with the SharePoint Developer Support team.

SharePoint 2013 allows users to run sites in SharePoint 2010 mode.  In this scenario, the solution (WSP) deployment needs to be deployed with the “CompatibilityLevel” flag set to “All”  or {14,15}.

When deploying the solution from the Central Administration UI, there’s no option to set the “CompatibilityLevel” flag and therefore the deployment job reverts to using the “SharePointProductVersion” attribute in the solution manifest.  Since the “SharePointProductVersion” attribute can only be set to a single number, solution deployment from CA is limited to using that number for the “CompatibilityLevel” setting.

The suggested method for this type of deployment is to use PowerShell:

Install-SPSolution –Identity Solution.wsp –GACDeployment –CompatibilityLevel {14,15}

Resources:

http://technet.microsoft.com/en-us/library/ee617150.aspx

http://technet.microsoft.com/en-us/library/ff607534.aspx

http://blogs.technet.com/b/mspfe/archive/2013/02/04/planning-deployment-of-farm-solutions-for-share...

HTH!