a use the v3 many years, building many many Packages.
Now v4 is here… i used the XXX.Template_v4.zip.
My first start was to build up my functions (extensions) 40 functions check
config check
Some other thinks…
Package works. Nice.
But now i have to understand how to strip down the unnessary stuff.
Don‘t need so many languages (strings)
Template files and so on.
Never use the online possibility to download or create a template!
This is not cool in large environments. (More the 2000 packages)
Also i have to add some logging for more Information, but i can‘t find it, like the old xxxMain.ps1
Alas, many of the strings must stay or it won’t work.
You might be able to clear out some of them in \Strings\ but not the ones in \PSAppDeployToolkit\Strings\
You can remove string translation folders if you really must, but we’re talking about kilobytes of savings here. It’s 2025, boss; you’re not running PSADT from a 1.44MB floppy drive so I’d just not bother.
You’ll probably find no one’s replied in 5 days one, because it’s been Easter, but also two, that people expect you to do your own research. Documentation almost never comes with open source projects, yet we’ve provided so much rich information on a proper website for you. Please do your own research. We’re here to help with any problems you encounter, but we’re not ChatGPT/Copilot, either.
The Website doesn‘t help at all. But let me say, a already found how to modify what i want and need. The function you explain, are not the secret.
May be, thats one of the point why many people don‘t use the new Kit anymore…
The toolkit shouldn’t have needed any modification to do what you’re after. There’s also tonnes of people using the new version, many of which wouldn’t even look at going back to 3.x. This number will only increase with 4.1.0 when it’s released.
It doesn’t though, there’s a whole callback system where you can run custom code from your extension every single time a deployment session starts. I will fully admit how that system and setup works is inappropriately documented though.
I’m sure you haven’t needed to modify the toolkit to do whatever it is you’ve done though. We’ve added so many places where you can add your own callback hooks for code to run. Modifying the toolkit to stick some extra logging lines in is equivilent to putting a hole in your wall because it’s hot and you need ventilation. You’ve also destroyed the digital signature on the module by doing this which weakens its security and trust.
