Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I have created a Configuration Parameter in TC's 'Parameters' area: That can work, but from the rest of the question I think that what you actually want to do here is create an Environment Var...
Answer
#2: Post edited
by
Peter Taylor
·
2023-01-30T09:20:09Z (almost 2 years ago)
- > I have created a Configuration Parameter in TC's 'Parameters' area:
- That can work, but from the rest of the question I think that what you actually want to do here is create an *Environment Variable*. The *Parameters* area has three sections: *Configuration Parameters*, *System Properties*, *Environment Variables*. Try using the latter.
- ----
- Alternatively, taking a more literal interpretation of the question, `PowerShell /?` lists the supported flags as
- > PowerShell[.exe] [-PSConsoleFile <file> | -Version <version>]
- > [-NoLogo] [-NoExit] [-Sta] [-Mta] [-NoProfile] [-NonInteractive]
- > [-InputFormat {Text | XML}] [-OutputFormat {Text | XML}]
- > [-WindowStyle <style>] [-EncodedCommand <Base64EncodedCommand>]
- > [-ConfigurationName <string>]
- > [-File <filePath> <args>] [-ExecutionPolicy <ExecutionPolicy>]
- > [-Command { - | <script-block> [-args <arg-array>]
- > | <string> [<CommandParameters>] } ]
Maybe you have a different version to me, but I don't see a `-environment:<var>` flag.
- > I have created a Configuration Parameter in TC's 'Parameters' area:
- That can work, but from the rest of the question I think that what you actually want to do here is create an *Environment Variable*. The *Parameters* area has three sections: *Configuration Parameters*, *System Properties*, *Environment Variables*. Try using the latter.
- ----
- Alternatively, taking a more literal interpretation of the question, `PowerShell /?` lists the supported flags as
- > PowerShell[.exe] [-PSConsoleFile <file> | -Version <version>]
- > [-NoLogo] [-NoExit] [-Sta] [-Mta] [-NoProfile] [-NonInteractive]
- > [-InputFormat {Text | XML}] [-OutputFormat {Text | XML}]
- > [-WindowStyle <style>] [-EncodedCommand <Base64EncodedCommand>]
- > [-ConfigurationName <string>]
- > [-File <filePath> <args>] [-ExecutionPolicy <ExecutionPolicy>]
- > [-Command { - | <script-block> [-args <arg-array>]
- > | <string> [<CommandParameters>] } ]
- Maybe you have a different version to me, but I don't see a `-environment:<var>` flag. You'd probably have to compose something with `-Command` and a `set` command.
#1: Initial revision
by
Peter Taylor
·
2023-01-30T09:19:03Z (almost 2 years ago)
> I have created a Configuration Parameter in TC's 'Parameters' area:
That can work, but from the rest of the question I think that what you actually want to do here is create an *Environment Variable*. The *Parameters* area has three sections: *Configuration Parameters*, *System Properties*, *Environment Variables*. Try using the latter.
----
Alternatively, taking a more literal interpretation of the question, `PowerShell /?` lists the supported flags as
> PowerShell[.exe] [-PSConsoleFile <file> | -Version <version>]
> [-NoLogo] [-NoExit] [-Sta] [-Mta] [-NoProfile] [-NonInteractive]
> [-InputFormat {Text | XML}] [-OutputFormat {Text | XML}]
> [-WindowStyle <style>] [-EncodedCommand <Base64EncodedCommand>]
> [-ConfigurationName <string>]
> [-File <filePath> <args>] [-ExecutionPolicy <ExecutionPolicy>]
> [-Command { - | <script-block> [-args <arg-array>]
> | <string> [<CommandParameters>] } ]
Maybe you have a different version to me, but I don't see a `-environment:<var>` flag.