none
Powershell and design manager RRS feed

  • Question

  • In  sharepoint 2013 I created a package using design manager and exported it to a wsp file. Is there a way to import a package using Powershell instead of from the design manager UI?
    Wednesday, September 4, 2013 7:50 PM

All replies

  • Hi Mike,

    Have you tried using the normal wsp deployment process like -

    1) Add-SPSolution

    2) Install-SPSolution

    3) Enable-SPFeature

    That should ideally work.

    Narahari

    ******If a post answers/helps your question, please click "Mark As Answer" on that post and/or "Vote as Helpful*******

    Thursday, September 5, 2013 3:23 AM
  • Hi,

    Check out the following articles and detailed content about how to install custom elements for SharePoint Server 2010. Applies to both SharePoint 2010 Products and SharePoint 2013.

    Deploy solution packages (SharePoint Server 2010)

    http://technet.microsoft.com/en-us/library/cc262995(v=office.14).aspx

    Features and solutions cmdlets in SharePoint 2013

    http://technet.microsoft.com/EN-US/library/ee906565.aspx

    Thanks.


    Tracy Cai
    TechNet Community Support

    Thursday, September 5, 2013 5:16 AM
    Moderator
  • I guess my point i is: Is a solution generated by design manager the same as any other solution and therefore we can apply Add-SPSolution or install-SPSolution? I am familiar with how to deploy a regular wsp generated by Visual Studio or by another method using PowerShell but not a package genetated by Design Manager.
    Thursday, September 5, 2013 1:25 PM
  • Hi Mike,

    The wsp generated by design manager is similar to a normal wsp. Hence we can use the normal wsp deployment steps for that too.

    Narahari

    ******If a post answers/helps your question, please click "Mark As Answer" on that post and/or "Vote as Helpful*******

    Thursday, September 5, 2013 2:20 PM
  • I am coming back to this question. When I installed/deployed and tried to enable the feature I get the below error. This is of course something  we wouldn't get if we package a solution using visual studio and scope it to a farm. Any idea how to change the scope to Farm? 

    Enable-SPFeature : The Feature is not a Farm Level Feature and is not found in
    a Site level defined by the Url http://extranet.domain.net.
    At line:1 char:1
    + Enable-SPFeature -Identity
    "FeatureDefinition/15/72278de5-15fe-42d9-8c6f-71af39e ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
        + CategoryInfo          : InvalidData: (Microsoft.Share...etEnableFeature:
       SPCmdletEnableFeature) [Enable-SPFeature], SPCmdletException
        + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletEnableFe
       ature

    Thursday, September 5, 2013 4:52 PM