Yah, that's going to break ChocoProcess. The first commands we run are A) Get Sources and B) get locally installed packages.
If config is carrying over, that's gonna break everything.
Well, actually, that's somewhat of a lie. But it will cause some really weird behaviors
Now you understand what I'm saying. If you keep the same Lets.GetChocolatey and reuse it after calling Run or List, it is a bug
Without resetting the config. But beware, there is still some issue here as it doesn't appear this fixed the problem yet
We do a fresh Lets.GetChocolatey() for every call, so it's persisting the config between those?
No, it should not be
that's what I'm investigating
Cool, I think we're on the same page now haha
Good luck! Let me know if you have any further questions.
I'm also available on Skype/Other if necessary
So low down on Licensed code - it changes from ChocolateyConfiguration to LicensedChocolateyConfiguration (a subclass of ChocolateyConfiguration), then it sets that on the container. For Licensed code to run, it needs a valid license and the configuration to be an instance of LicensedChocolateyConfiguration
So I switched it to use the container to get the Configuration, which should pull back the right one. I was thinking there may be some side effects to this, so I'm trying to go through and fix those items.