Closed fmms closed 1 year ago
Thx I'll check this tonight.
The issue is related to this part of the doc regarding environment variables
If there is no parent process, per-machine and per-user environment variables are used instead. For example, a new console window has all per-machine and per-user environment variables defined at the time it was launched.
In the case of NUnit there is a parent process, so per-user environment variables are not pushed in the process scope.
I Can't figure out why the test is not working on AppVeyor when it works on Visual Studio. I took the time to review some details in the setup of the test environment on AppVeyor (QA related) but it's just to be sure that we are not blocked further. Will probably give another try tonight.
thank you so much for fixing this @Seddryck . You will be part of my presentation at SQL Konferenz. ;) When will 1.24 be released?
thank you so much for fixing this @Seddryck .
Just find out the issue with tests running in parallel and adding/removing the same variables.
You will be part of my presentation at SQL Konferenz. ;)
I saw that ... FYI I presented NBi 6-7 years ago at SQL Konferenz :-D
When will 1.24 be released?
I'll do some dependencies bump and then will release 1.24
i was in your audience at SQL Konferenz back then... ;)
Adjust to expected behavior and easier use in build systems.
Documentation of the different scopes of environment variables is at https://learn.microsoft.com/en-us/dotnet/api/system.environment.getenvironmentvariable?view=net-7.0#system-environment-getenvironmentvariable(system-string) .
Solves #717
I have not tested this myself as I have no corresponding build environment, but this should solve it ...