Extract Wsp solutions

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
1
down vote

favorite












Our dev team has developed SharePoint solutions, suddenly the source control is damaged and we don't have back up from the source code !! Only the deployed wsp solutions



Is it possible to reflect the wsp files to source code solution? Any reflector for that?










share|improve this question





























    up vote
    1
    down vote

    favorite












    Our dev team has developed SharePoint solutions, suddenly the source control is damaged and we don't have back up from the source code !! Only the deployed wsp solutions



    Is it possible to reflect the wsp files to source code solution? Any reflector for that?










    share|improve this question

























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      Our dev team has developed SharePoint solutions, suddenly the source control is damaged and we don't have back up from the source code !! Only the deployed wsp solutions



      Is it possible to reflect the wsp files to source code solution? Any reflector for that?










      share|improve this question















      Our dev team has developed SharePoint solutions, suddenly the source control is damaged and we don't have back up from the source code !! Only the deployed wsp solutions



      Is it possible to reflect the wsp files to source code solution? Any reflector for that?







      2013 sharepoint-server sharepoint-on-prem solution-package






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 1 hour ago









      Waqas Sarwar MVP♦

      50.1k112864




      50.1k112864










      asked 2 hours ago









      Fabio

      1019




      1019




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          try below steps to get the files.



          • First of all, locate the WSP package that needs to be investigated.
            you can go to Central Application system settings > manage farm solutions and download the required wsp. Youc an use the following code to download it via powershell:


          $frm = Get-SPFarm



          $file = $frm.Solutions.Item("nameof.wsp").SolutionFile



          $file.SaveAs("c:wspnameof.wsp")




          • Rename the .wsp to a .cab format.

          • Accept the warning which advises you the file may become unusable

          • Extract the cab contents somewhere to your drive.

          • Browse to the directory and have a look at the extracted files

          SharePoint 2010: Reverse Engineering SharePoint WSP Packages






          share|improve this answer




















          • Thanks waqas, I will try and let you know
            – Fabio
            11 mins ago

















          up vote
          2
          down vote













          Unfortunately, WSPs contain compiled code, not source code. Of course, if the code in question is javascript, then that is easily obtaintable. For c#, there are a variety of tools, such as ILSpy to decompile the code. Here is a similar question with answers that recommend different tools.



          For future reference, both visualstudio.com and github have source code control, and both offer it for free.



          edit: as Helb commented, the wsp file is really just a cab file. Change the extention of the wsp to .cab, and then open it with windows explorer. This will give you access to the files that are being deployed, including any js, css, html, etc., files, plus the dll. I'll assume that the decompilers don't know how to read wsp files, so go through this process, and copy the dll to another location, and then use the decompiler from there.






          share|improve this answer






















          • Thanks Mike for your help
            – Fabio
            10 mins ago










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "232"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsharepoint.stackexchange.com%2fquestions%2f250594%2fextract-wsp-solutions%23new-answer', 'question_page');

          );

          Post as a guest






























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote



          accepted










          try below steps to get the files.



          • First of all, locate the WSP package that needs to be investigated.
            you can go to Central Application system settings > manage farm solutions and download the required wsp. Youc an use the following code to download it via powershell:


          $frm = Get-SPFarm



          $file = $frm.Solutions.Item("nameof.wsp").SolutionFile



          $file.SaveAs("c:wspnameof.wsp")




          • Rename the .wsp to a .cab format.

          • Accept the warning which advises you the file may become unusable

          • Extract the cab contents somewhere to your drive.

          • Browse to the directory and have a look at the extracted files

          SharePoint 2010: Reverse Engineering SharePoint WSP Packages






          share|improve this answer




















          • Thanks waqas, I will try and let you know
            – Fabio
            11 mins ago














          up vote
          1
          down vote



          accepted










          try below steps to get the files.



          • First of all, locate the WSP package that needs to be investigated.
            you can go to Central Application system settings > manage farm solutions and download the required wsp. Youc an use the following code to download it via powershell:


          $frm = Get-SPFarm



          $file = $frm.Solutions.Item("nameof.wsp").SolutionFile



          $file.SaveAs("c:wspnameof.wsp")




          • Rename the .wsp to a .cab format.

          • Accept the warning which advises you the file may become unusable

          • Extract the cab contents somewhere to your drive.

          • Browse to the directory and have a look at the extracted files

          SharePoint 2010: Reverse Engineering SharePoint WSP Packages






          share|improve this answer




















          • Thanks waqas, I will try and let you know
            – Fabio
            11 mins ago












          up vote
          1
          down vote



          accepted







          up vote
          1
          down vote



          accepted






          try below steps to get the files.



          • First of all, locate the WSP package that needs to be investigated.
            you can go to Central Application system settings > manage farm solutions and download the required wsp. Youc an use the following code to download it via powershell:


          $frm = Get-SPFarm



          $file = $frm.Solutions.Item("nameof.wsp").SolutionFile



          $file.SaveAs("c:wspnameof.wsp")




          • Rename the .wsp to a .cab format.

          • Accept the warning which advises you the file may become unusable

          • Extract the cab contents somewhere to your drive.

          • Browse to the directory and have a look at the extracted files

          SharePoint 2010: Reverse Engineering SharePoint WSP Packages






          share|improve this answer












          try below steps to get the files.



          • First of all, locate the WSP package that needs to be investigated.
            you can go to Central Application system settings > manage farm solutions and download the required wsp. Youc an use the following code to download it via powershell:


          $frm = Get-SPFarm



          $file = $frm.Solutions.Item("nameof.wsp").SolutionFile



          $file.SaveAs("c:wspnameof.wsp")




          • Rename the .wsp to a .cab format.

          • Accept the warning which advises you the file may become unusable

          • Extract the cab contents somewhere to your drive.

          • Browse to the directory and have a look at the extracted files

          SharePoint 2010: Reverse Engineering SharePoint WSP Packages







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 1 hour ago









          Waqas Sarwar MVP♦

          50.1k112864




          50.1k112864











          • Thanks waqas, I will try and let you know
            – Fabio
            11 mins ago
















          • Thanks waqas, I will try and let you know
            – Fabio
            11 mins ago















          Thanks waqas, I will try and let you know
          – Fabio
          11 mins ago




          Thanks waqas, I will try and let you know
          – Fabio
          11 mins ago












          up vote
          2
          down vote













          Unfortunately, WSPs contain compiled code, not source code. Of course, if the code in question is javascript, then that is easily obtaintable. For c#, there are a variety of tools, such as ILSpy to decompile the code. Here is a similar question with answers that recommend different tools.



          For future reference, both visualstudio.com and github have source code control, and both offer it for free.



          edit: as Helb commented, the wsp file is really just a cab file. Change the extention of the wsp to .cab, and then open it with windows explorer. This will give you access to the files that are being deployed, including any js, css, html, etc., files, plus the dll. I'll assume that the decompilers don't know how to read wsp files, so go through this process, and copy the dll to another location, and then use the decompiler from there.






          share|improve this answer






















          • Thanks Mike for your help
            – Fabio
            10 mins ago














          up vote
          2
          down vote













          Unfortunately, WSPs contain compiled code, not source code. Of course, if the code in question is javascript, then that is easily obtaintable. For c#, there are a variety of tools, such as ILSpy to decompile the code. Here is a similar question with answers that recommend different tools.



          For future reference, both visualstudio.com and github have source code control, and both offer it for free.



          edit: as Helb commented, the wsp file is really just a cab file. Change the extention of the wsp to .cab, and then open it with windows explorer. This will give you access to the files that are being deployed, including any js, css, html, etc., files, plus the dll. I'll assume that the decompilers don't know how to read wsp files, so go through this process, and copy the dll to another location, and then use the decompiler from there.






          share|improve this answer






















          • Thanks Mike for your help
            – Fabio
            10 mins ago












          up vote
          2
          down vote










          up vote
          2
          down vote









          Unfortunately, WSPs contain compiled code, not source code. Of course, if the code in question is javascript, then that is easily obtaintable. For c#, there are a variety of tools, such as ILSpy to decompile the code. Here is a similar question with answers that recommend different tools.



          For future reference, both visualstudio.com and github have source code control, and both offer it for free.



          edit: as Helb commented, the wsp file is really just a cab file. Change the extention of the wsp to .cab, and then open it with windows explorer. This will give you access to the files that are being deployed, including any js, css, html, etc., files, plus the dll. I'll assume that the decompilers don't know how to read wsp files, so go through this process, and copy the dll to another location, and then use the decompiler from there.






          share|improve this answer














          Unfortunately, WSPs contain compiled code, not source code. Of course, if the code in question is javascript, then that is easily obtaintable. For c#, there are a variety of tools, such as ILSpy to decompile the code. Here is a similar question with answers that recommend different tools.



          For future reference, both visualstudio.com and github have source code control, and both offer it for free.



          edit: as Helb commented, the wsp file is really just a cab file. Change the extention of the wsp to .cab, and then open it with windows explorer. This will give you access to the files that are being deployed, including any js, css, html, etc., files, plus the dll. I'll assume that the decompilers don't know how to read wsp files, so go through this process, and copy the dll to another location, and then use the decompiler from there.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 1 hour ago

























          answered 1 hour ago









          Mike2500

          4,20131327




          4,20131327











          • Thanks Mike for your help
            – Fabio
            10 mins ago
















          • Thanks Mike for your help
            – Fabio
            10 mins ago















          Thanks Mike for your help
          – Fabio
          10 mins ago




          Thanks Mike for your help
          – Fabio
          10 mins ago

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsharepoint.stackexchange.com%2fquestions%2f250594%2fextract-wsp-solutions%23new-answer', 'question_page');

          );

          Post as a guest













































































          Comments

          Popular posts from this blog

          Long meetings (6-7 hours a day): Being “babysat” by supervisor

          Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

          Confectionery