Closed Griefed closed 3 months ago
Unfortunately, I haven't had the time to tackle this issue myself. Help from the community would be greatly appreciated.
Just make a batch that fires the PowerShell script, PowerShell will run from dos if invoked.
Better late than never. This appears to work just fine, though I don't particularly like it:
@ECHO OFF
CD /d %~dp0
powershell.exe -ExecutionPolicy Bypass -File "start.ps1"
The reason for me not liking is is the fact this is more of a hack than a standalone Batch-template. It requires the PowerShell-script to be present and depends on PowerShell allowing this behaviour.
I'll continue looking into providing an honest Batch-template, maybe even ask for the BisectHosting services on the server.
Better late than never. This appears to work just fine, though I don't particularly like it:
@ECHO OFF CD /d %~dp0 powershell.exe -ExecutionPolicy Bypass -File "start.ps1"
The reason for me not liking is is the fact this is more of a hack than a standalone Batch-template. It requires the PowerShell-script to be present and depends on PowerShell allowing this behaviour.
I'll continue looking into providing an honest Batch-template, maybe even ask for the BisectHosting services on the server.
You should, they would gladly grant you one. You're popular enough, I'd say go for a VPS.
Maybe my phrasing was bad. I was talking about the service-request section in the Developer Market :D
Whats the feature you would like to be improved?
This is open for anyone interested.
The task at hand is to convert the PowerShell start-script template to Batch, as PowerShell continues to cause trouble on many systems.
Requirements:
In short: Translate the PowerShell template to Batch. Don't loose features, don't add features.
Anything else you would like to add?
If you feel up to the task, comment on this issue!
Code of Conduct