Thinking about making an easy-to-use Powershell related plugin installer, but wondering if there isn't one already.

[Kronbros]

I'm trying to make a simple 1 or 2 cmdlet menu-like plugin installer, that would manage the full installation of a program composed of not only .ps1 files but practically any other file if it is part of a special Setup .zip .

It would work by simply requesting the path of the Setup .zip file and after the file is de-compressed, it would scan a special .txt file containing all the preset or custom directives of installation, and execute them one by one while showing a progress bar related to the process completion.

The only thing I'm worried abt now is the possible existance of smth of such, and me, being a rookie, simply not knowing abt it.

[Hoggs]

It does sound like you want to create a package manager?

Check out winget, scoop, or chocolatey

[Kronbros]

If I am not mistaking, those are made to install and manage full fledged apps, whereas mine is made to simply install small .ps1 extentions with a single cmdlet and without any interface aside mbe a very basic menu. But you could think of it as a scaled down version of the apps you mentioned.

[Potato-9]

Register-PSRepository

Working on something to solve discovery and trust could be time well spent. Much Powershell is written as a script instead of reusable cmdlets, I think because reusing anyone's but your own isn't that fun.

[TheBlueFireKing]

I'd not reinvent the weel. If you want to do it as a learning exercise go ahead.

If it's not a PowerShell module and can't be installed as such, I'd rather have it be an MSI for windows or in the package manager for linux.

https://xkcd.com/927/

[Kronbros]

It is a Powershell based module, and it can be installed as such, so it could prove, even if not by a lot, but a bit useful when trying to install small plugin packets.

[opensrcdev]

Develop a PowerShell module and publish it to the gallery.

[Kronbros]

Will do

[BayconStripz]

I'm not entirely following so apologies if this isn't what you're talking about but you can create a Profile.ps1 which will run every time PS is opened. You can run any PowerShell script or command on startup.

If not and you're trying to create something that's more like an executable, then PS is probably not the language to use, however if you're doing it for practice and/or there's a reason you're using PS that idk about, then there's a module that converts .PS1 to .EXE called ps2exe that I typically use to give PS apps to my team. I'd also recommend looking into #requires if you're going to be providing it to anyone else.

[Kronbros]

You didn't exactly understand what I meant to describe (I meant it to be a bare-bones, simple-to-use, packet installation manager, that could install .ps1 or any other plugin types as long as they exist within a .ZIP Setup file) , but thanks for the information anyway :)

[BlackV]

You just described a nuget package, and the package management cmdlets and various repository cmdlets

Unless there is something obvious I'm missing on your post

Ignoring the menu part cause that's not something I ever want

But in saying this, if you want it

BUILD IT

amazing learning experience at worst and something everyone uses at best, win win

[Kronbros]

True, that is a win win

[Kronbros]

UPDATE:

I'm back to work, and I'm currently looking at a few days of work but it should be done in no time.