Fast one for you guys:
building some resources./modules in DSC. Run into a bug, make a fix then try again. What I’ve noticed is that if you modify a resource after it’s been dropped into the modules directory and effectively “live”, Windows will continue to use what’s in memory. Running a get-module and it’s kin seem to all work in the current session … so how do I force Windows to re-read it’s modules folder and try the new module without going as far as a reboot?
As an extension to this question: updating via a pull server.
As it stands I understand I need to bump up the version number on the zip filename and manifest to make sure clients know to download a newer version … but should I also update the GUID or does that stay consistent? Documentation seems unclear here.