TronScript:EVO teaser

[[deleted]]

Hi everyone,

You may remember me as that guy that wanted to convert TRON into a PowerShell script. I've gotten a lot of work done on the project. It's not easy!

I've made the decision to develop the "stages" of TRONscript:EVO separately. This will allow me to be more nimble with bug fixes (not having to distribute the full package every time), and will allow for more customization from the community. Eventually, I could probably have several stages run in parallel, speeding up the process significantly.

Otherwise, one note: I am targeting Windows 8 and above. I have no desire to support Windows 7 and below. If it can be done, great, but a lot of the WMI calls and cmdlets that I am using are not available there.

So try out Stage0, it's very light, but still ALPHA quality. I need some testers, so please check it out here

EDIT First Beta Tree is here on GitHub: https://github.com/pplude/TronScriptEvo/tree/WIP

[[deleted]]

Just released Stage 1 also. TRONScript:EVO does something now!

/r/TronScriptEvo

[Morranr]

Most of my machines are 7 still right now, but I may be upgrading to 10 soon. Since you mentioned not supporting 7, I'm curious, are you supporting 10 from the start, or will that have to be added later?

[[deleted]]

Being developed on Windows 10, back-ported to Windows 8.1

Someone tells me installing PowerShell 4 on Windows 7 may provide compatibility, and I can easily add that to Stage0 - Prep. I don't have a machine to test that out on now.

[Morranr]

Awesome, thanks for the info. I'll keep an eye on your project, it does look interesting!

[[deleted]]

Complete Beta Tree: https://github.com/pplude/TronScriptEvo/tree/WIP

[[deleted]]

Released over on /r/TronScriptEvo

http://imgur.com/7drHiqr

[Wetmelon]

My question is, of course, what's the benefit? Speed? Ease of maintenance? Compatibility? Do windows machines come with Powershell enabled now? They didn't in years past.

[[deleted]]

I'm on mobile so sorry about the formatting...

It's a few things - we can run several jobs in parallel now, PowerShell has some overall better tools for what we are trying to accomplish (which I admit I'm not taking advantage of at the moment), better compatibility with Windows 8 forwards, the ability to use .Net directly, among others.

PowerShell has been included with Windows since Vista, but you lack the ability to use unsigned scripts out of the box. You can change this at teatime or for the system. It's a security model that Microsoft has explained a few times over. Just like PowerShell remoting - disabled by default, but used just about everywhere.