Replies: 1 comment
|
Hi |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe
Yes, this request is related to a problem. The problem is that I have several C# scripts that require the compiler path and compiler options settings when using TE2. These scripts work as is in TE3. The problem is when running a script in DevOps, you have to jump through several hoops to manually add a Preferences.json file to the right location, update the ScriptCompilerDirectoryPath and ScriptCompilerOptions properties within the json and then run the CLI to get the compiler options to take effect.
Describe the solution you'd like
Since the only CLI that currently exists is based on TE2, it would be nice to either have a TE3 CLI that uses the most up to date Roslyn compiler or to have CLI parameters. This would allow the values for ScriptCompilerDirectoryPath and ScriptCompilerOptions to be passed in which would override what is in the Preferences.json file or be used when the Preferences.json file doesn't exist, such as when using the portable version (which works great for DevOps).
Even with a TE3 CLI, these parameters could be very useful for users who are using the free TE2 version.
Goals
To simplify the running of similar scripts in TE2, TE3 and DevOps. The problem is mostly related to the CLI and not being able to easily set properties.
Background
No response
Additional context
No response
All reactions