Powershell - Using Config Files for Variables












0















I need to build a set of scripts in PowerShell for SharePoint Deployments, and I'd like to use the same idea I've been using in BAT files.



The idea is having ONE .ps1 to configure "session" variables, example: [string] $SiteUrl,
and then call first this config script in each .ps1 file I have, so I just need to edit one.



Config.ps1



[string] $SiteUrl = "www.google.com"
[string] $WspPath = "C:pathtowsp.wsp"


Deploy.ps1



INVOKE Config.ps1 --> ?????????????
STSADM -o addsolution $SiteUrl


How can I manage that in PowerShell?



Thanks!










share|improve this question





























    0















    I need to build a set of scripts in PowerShell for SharePoint Deployments, and I'd like to use the same idea I've been using in BAT files.



    The idea is having ONE .ps1 to configure "session" variables, example: [string] $SiteUrl,
    and then call first this config script in each .ps1 file I have, so I just need to edit one.



    Config.ps1



    [string] $SiteUrl = "www.google.com"
    [string] $WspPath = "C:pathtowsp.wsp"


    Deploy.ps1



    INVOKE Config.ps1 --> ?????????????
    STSADM -o addsolution $SiteUrl


    How can I manage that in PowerShell?



    Thanks!










    share|improve this question



























      0












      0








      0








      I need to build a set of scripts in PowerShell for SharePoint Deployments, and I'd like to use the same idea I've been using in BAT files.



      The idea is having ONE .ps1 to configure "session" variables, example: [string] $SiteUrl,
      and then call first this config script in each .ps1 file I have, so I just need to edit one.



      Config.ps1



      [string] $SiteUrl = "www.google.com"
      [string] $WspPath = "C:pathtowsp.wsp"


      Deploy.ps1



      INVOKE Config.ps1 --> ?????????????
      STSADM -o addsolution $SiteUrl


      How can I manage that in PowerShell?



      Thanks!










      share|improve this question
















      I need to build a set of scripts in PowerShell for SharePoint Deployments, and I'd like to use the same idea I've been using in BAT files.



      The idea is having ONE .ps1 to configure "session" variables, example: [string] $SiteUrl,
      and then call first this config script in each .ps1 file I have, so I just need to edit one.



      Config.ps1



      [string] $SiteUrl = "www.google.com"
      [string] $WspPath = "C:pathtowsp.wsp"


      Deploy.ps1



      INVOKE Config.ps1 --> ?????????????
      STSADM -o addsolution $SiteUrl


      How can I manage that in PowerShell?



      Thanks!







      command-line powershell






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 28 '14 at 18:22







      user304064

















      asked May 28 '14 at 18:18









      TznTzn

      104




      104






















          2 Answers
          2






          active

          oldest

          votes


















          1














          You can just dot source the config.ps1 script:



          . .Config.ps1


          And then you can just call the variables when you need them.



          $SiteUrl
          $WspPath





          share|improve this answer

































            -1














            Please consider, that if an attacker can modify the external ps1 file, he can make really mess. for example what happens if he changes this:



            [string] $SiteUrl = "www.google.com"
            [string] $WspPath = "C:pathtowsp.wsp"



            to this:
            [string] $SiteUrl = "www.google.com"
            [string] $WspPath = "C:pathtowsp.wsp"
            format c:






            share|improve this answer























              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "3"
              };
              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',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f759870%2fpowershell-using-config-files-for-variables%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              1














              You can just dot source the config.ps1 script:



              . .Config.ps1


              And then you can just call the variables when you need them.



              $SiteUrl
              $WspPath





              share|improve this answer






























                1














                You can just dot source the config.ps1 script:



                . .Config.ps1


                And then you can just call the variables when you need them.



                $SiteUrl
                $WspPath





                share|improve this answer




























                  1












                  1








                  1







                  You can just dot source the config.ps1 script:



                  . .Config.ps1


                  And then you can just call the variables when you need them.



                  $SiteUrl
                  $WspPath





                  share|improve this answer















                  You can just dot source the config.ps1 script:



                  . .Config.ps1


                  And then you can just call the variables when you need them.



                  $SiteUrl
                  $WspPath






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited May 28 '14 at 19:02

























                  answered May 28 '14 at 18:23









                  Tim FerrillTim Ferrill

                  57839




                  57839

























                      -1














                      Please consider, that if an attacker can modify the external ps1 file, he can make really mess. for example what happens if he changes this:



                      [string] $SiteUrl = "www.google.com"
                      [string] $WspPath = "C:pathtowsp.wsp"



                      to this:
                      [string] $SiteUrl = "www.google.com"
                      [string] $WspPath = "C:pathtowsp.wsp"
                      format c:






                      share|improve this answer




























                        -1














                        Please consider, that if an attacker can modify the external ps1 file, he can make really mess. for example what happens if he changes this:



                        [string] $SiteUrl = "www.google.com"
                        [string] $WspPath = "C:pathtowsp.wsp"



                        to this:
                        [string] $SiteUrl = "www.google.com"
                        [string] $WspPath = "C:pathtowsp.wsp"
                        format c:






                        share|improve this answer


























                          -1












                          -1








                          -1







                          Please consider, that if an attacker can modify the external ps1 file, he can make really mess. for example what happens if he changes this:



                          [string] $SiteUrl = "www.google.com"
                          [string] $WspPath = "C:pathtowsp.wsp"



                          to this:
                          [string] $SiteUrl = "www.google.com"
                          [string] $WspPath = "C:pathtowsp.wsp"
                          format c:






                          share|improve this answer













                          Please consider, that if an attacker can modify the external ps1 file, he can make really mess. for example what happens if he changes this:



                          [string] $SiteUrl = "www.google.com"
                          [string] $WspPath = "C:pathtowsp.wsp"



                          to this:
                          [string] $SiteUrl = "www.google.com"
                          [string] $WspPath = "C:pathtowsp.wsp"
                          format c:







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jan 23 at 10:26









                          Tolvaj PéterTolvaj Péter

                          1




                          1






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Super User!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f759870%2fpowershell-using-config-files-for-variables%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                              Alcedinidae

                              Origin of the phrase “under your belt”?