This topic contains 3 replies, has 3 voices, and was last updated by
November 21, 2016 at 12:08 pm #58279ParticipantPoints: 0Rank: Member
we have a requirement to port 250+ Unix Shell scripts to Windows. These scripts perform operations like file operation (validate header info), move files, encrypt/decrypt, e-mail notify, file watcher, archival etc. Need your help on two points:
a) Currently below 3 options have been suggested.
• Finalize on Tool Options
– Cygwin – open source; no support contract
– MKS Toolkit
– Windows PowerShell
b) Considering higher chance of PowerShell being chosen, Would you be able to provide any insights if any conversion tool can be used. If not, what is the complexity of porting the shell scripts to Windows.
Thanks in Advance.
November 21, 2016 at 7:52 pm #58352ParticipantPoints: 420Rank: Contributor
The most fitting answer to this question would be: 'It depends'. 😉 ... and I think it depends on several conditions.
I only have superficial knowledge about Linux or Unix but I would recommend NOT to port your scripts and especially not by a conversion tool or saomething like this. I think because of the completely different philosophies behind Powershell and Unix shell scripts it will be probably more reliable and much better maintainable to rewrite what you need in 'native' Powershell. Probably your scripts will be anyway less bulky in Powershell.
And ... probably you will not find that many Unix or Linux admins in this forum. 😉
November 21, 2016 at 8:16 pm #58355ParticipantPoints: 2Rank: Member
I can't imagine those 250+ scripts all perform unique tasks. Rewriting from scratch will give you a chance to reduce them to a manageable number. I'm just speculating, but I would guess there are many that perform the same task but on different machines, or directories, etc, things that could have been passed as parameters instead.
November 23, 2016 at 5:26 am #58484ParticipantPoints: 0Rank: Member
Thanks a ton Ron and Olaf for the clarification. One more doubt I have. Don't we have any COM object which may be used for this purpose?
The topic ‘Porting Unix Shell Script to PowerShell’ is closed to new replies.