It looks like this bug was erroneously filed against NUnit 3.0, which doesn't have an installer yet. As a result, it has been passed over for more than a year. I'm changing it to the NUnit V2 project so we can decide how to resolve it.
** Project changed: nunit-3.0 => nunitv2 -- You received this bug notification because you are a member of NUnit Core Developers, which is the registrant for NUnit Framework. https://bugs.launchpad.net/bugs/638289 Title: Install uses CURRENT_USER instead of LOCAL_MACHINE for AssemblyFoldersEx Status in NUnit V2 Test Framework: Confirmed Bug description: When using the .msi installer the registry entry for SOFTWARE\Microsoft\.NETFramework\v2.0.50727\AssemblyFoldersEx\NUnit 2.5.7.10213 (or whatever version) is placed into HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE. This means that msbuild will not find the nunit.framework.dll when running in a different account than that which installed nunit (like on a build server). To manage notifications about this bug go to: https://bugs.launchpad.net/nunitv2/+bug/638289/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
