Convert PowerShell Scripts to C#
Budget: $750 – $1,500 USD
I have a collection of mature Windows automation scripts written in PowerShell and I want every bit of that logic rewritten in clean, production-ready C#. The end result should be a head-less Windows service/agent—no GUI—capable of handling all existing task-scheduling duties without requiring user interaction once installed.
What you’ll be touching:
• Windows internals: services, scheduled tasks, processes, file system, event logs
• Registry read/write with safe rollback logic
• WMI and other system-management APIs for device and OS-level operations
• Packaging and deployment strategies that avoid common antivirus false positives; signed binaries are strongly preferred
Scope of work
1. Analyse the current automation scripts and design an equivalent C# implementation, maintaining functional parity.
2. Build a robust Windows background service that performs the same task-scheduling operations the scripts handle today.
3. Implement structured logging, configurable via file or Windows Event Log.
4. Provide an installer (MSI or similar) plus clear deployment and rollback instructions.
5. Deliver thoroughly documented, clean C# code that compiles under the latest LTS .NET release.
Acceptance criteria
• All original automation tasks run successfully from the installed service without manual triggers.
• No antivirus flags during a standard Defender scan on default settings.
• Registry, file system, and scheduled-task interactions perform with proper error handling and automatic rollback.
• Source compiles with zero warnings under Release build, and code passes a simple peer review for readability.
Please include links or brief summaries of past Windows utilities, background agents, or PowerShell-to-C# migrations you’ve shipped—especially those that manipulate the registry, services, WMI, or other endpoint-automation facets.
What you’ll be touching:
• Windows internals: services, scheduled tasks, processes, file system, event logs
• Registry read/write with safe rollback logic
• WMI and other system-management APIs for device and OS-level operations
• Packaging and deployment strategies that avoid common antivirus false positives; signed binaries are strongly preferred
Scope of work
1. Analyse the current automation scripts and design an equivalent C# implementation, maintaining functional parity.
2. Build a robust Windows background service that performs the same task-scheduling operations the scripts handle today.
3. Implement structured logging, configurable via file or Windows Event Log.
4. Provide an installer (MSI or similar) plus clear deployment and rollback instructions.
5. Deliver thoroughly documented, clean C# code that compiles under the latest LTS .NET release.
Acceptance criteria
• All original automation tasks run successfully from the installed service without manual triggers.
• No antivirus flags during a standard Defender scan on default settings.
• Registry, file system, and scheduled-task interactions perform with proper error handling and automatic rollback.
• Source compiles with zero warnings under Release build, and code passes a simple peer review for readability.
Please include links or brief summaries of past Windows utilities, background agents, or PowerShell-to-C# migrations you’ve shipped—especially those that manipulate the registry, services, WMI, or other endpoint-automation facets.