Support for a Windows PowerShell platform #70
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
adamretter
force-pushed
the
platform-windows-powershell
branch
from
8fc4dc5 to
88a7aa1
Compare
|
Can we have a consistent commit message like: |
|
@khmarbaise Well this PR is just a work in progress. I mostly wanted feedback from you and the team as to whether this was even desirable? I don't actually need it myself anymore... |
|
I think this is an improvement so If you want continue and ping if you are ready I appreciate to merge this... |
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.
See #79
This adds support for generating scripts for Windows PowerShell.
NOTE: This is not yet fully tested and I suspect some quoting issues in the generated PowerShell scripts, but I am opening this PR to see if there is any interest in adding PowerShell support to AppAssembler before I do further work on this...