Hey everyone, I'm looking for some serious guidance on my HelpDesk tool that I've developed over the years using Visual Studio and PowerShell. Initially, it was just for my personal use to consolidate various scripts I kept looking up, but now it's become a robust tool that I'd like to share with others in similar roles. My main questions are: 1) What are the next steps I should take to make this tool available for wider use? 2) I created an EXE that references a PS1 file to keep the source code safe. Is there a more professional way to handle deployments and updates? 3) Should I consider hiring someone to help me move forward, or what are some other options? I'm really eager to keep this project alive!
5 Answers
If I were you, I’d keep it simple for now. Focus on improving what you have without overcomplicating. Upload your project on GitHub, keeping in mind to remove any sensitive data. As for distribution, think about how to do updates efficiently, maybe through a server. Selling this might not be ideal unless it’s a groundbreaking tool—maybe just let your coworkers use it first and see where it goes from there.
It sounds like you're embarking on something huge! Before anything, check your employment contract—sometimes, tools developed at work are owned by the company. If you decide to move forward with selling it, consider utilizing the WiX Toolset for creating an installer. Listening to feedback is crucial, too; sharing your project on GitHub can help you improve it while also potentially getting you connections with others who might need similar tools.
I used to have a similar setup where I wrapped PowerShell scripts in an HTA interface. Eventually, I transitioned to an ASP.NET web application, rewriting the PowerShell scripts as C# classes. It's not as intimidating as it sounds; you'll find many direct C# equivalents for your PowerShell commands. This would allow you to make the tool more accessible and potentially easier to maintain in the long run.
Thanks for sharing! That gives me a lot to think about.
Converting to a full C# solution is an option, but it requires a lot of time. A quicker win might be using a PowerShell Universal approach, allowing you to keep the updates centralized and maintain security. This way, you're also minimizing the risks associated with running scripts with elevated rights. It could be a good compromise that utilizes your existing knowledge while also introducing you to new skills.
Thanks! This sounds like a practical route to explore.
You should definitely set up a Git repository for version control. Break your tool into modular parts based on functionality; this will make it easier to manage. Ensure everything works properly with and without the GUI. Then, consider turning your code into proper PowerShell modules, which could make it easier to distribute and update. I'm not into the selling side, but you could incorporate a license check if you plan to monetize it.
That's solid advice! Modularizing the functionality will really help in the long run.
Good point about checking the contract. I hadn’t thought of that!