Migration to powershell
TylersComputersKC opened this issue · comments
Does this project have any plans to begin moving to PowerShell? I believe that this project would be awesome in PowerShell and have a lot more flexibility.
With basic PowerShell being released to windows 7, and majority of the market being windows 10/11 right now, either starting a second project for PowerShell to streamline and use a better native codebase on windows 10/11 would be nice.
One of the things that would be better if this was written in PowerShell, is that you could download only the tools for the system architecture you have and could call only the tools you want to run. It would save bandwidth and make the process of deploying the script much faster.
If you wanted to get super fancy you could even implement a GUI. and you would get a lot more verbose logging to troubleshoot error messages.
I would be thrilled to contribute to this project for this, as most of my scripting experience is in PowerShell.
One downside is, for corporate IT departments some disable PowerShell. so I think building this out into a second project would be wise, or creating a different stack for the release.
One downside is, for corporate IT departments some disable PowerShell. so I think building this out into a second project would be wise, or creating a different stack for the release.
I agree with everything except this, You shouldn't be using this tool on a Corporate-Owned Machine. Either as IT (If it is infected just wipe and rebuild) or as a end-user (Could break a lot of stuff and if you think you are infected tell your IT)
This is answered in the CQ:
There was an effort to do a community port of Tron to PowerShell years ago, but it appears the repo is stagnant and the project is dead.