Updating C# scripts and references from ScriptCS to dotnet script #2035
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
IsaacCalligeros95
changed the title
|
@IsaacCalligeros95 I've merged in changes to resolve conflicts with our new spelling checks, which occur for each PR. Please merge when you're ready (I guess this is waiting for a release?) |
|
@steve-fenton-octopus Thanks Steve, this one will probably be sitting for a while longer, there's a couple of changes to go out and there will be a transition period between the old C# scripting and the new. I'm planning on merging this when most customers have migrated to the newer version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates references to ScriptCS and example usage to bring the docs in line with the dotnet-script changes. As this is a 2023.4 change it may make more sense to call out each of the individual scripting libraries rather than just update in place as I've done here. The migration is highlighted in the blog post with recent changes here OctopusDeploy/blog#1077