Great work, enjoying your videos. 46:32 Recently had a requirement to keep the “settings” outside of my script, hoping to keep sticky fingers from touching the code.. opted to read in an ini and parse the content. What would your suggestion be, ini/xml/json? Are there any benefits between the different formats?
Depending on the situation, my first goto for bringing in settings would probably be json. I can bring it into powershell as objects, which can then be more easily manipulated. Parsing a text based ini file would not be my idea of a fun time at all!
Thanks for this, loved this video - found it super useful for my script.
Great work, enjoying your videos.
46:32 Recently had a requirement to keep the “settings” outside of my script, hoping to keep sticky fingers from touching the code.. opted to read in an ini and parse the content. What would your suggestion be, ini/xml/json? Are there any benefits between the different formats?
Depending on the situation, my first goto for bringing in settings would probably be json. I can bring it into powershell as objects, which can then be more easily manipulated. Parsing a text based ini file would not be my idea of a fun time at all!