The msi should install under HKEY_LOCAL_MACHINE if you are the administrator and if you use the command line option specified. It won't install under HKLM in any other circumstance.
If it's not working, you'll have to wait for NUnit 3.0 to see a fix, since there are no more planned releases of NUnit 2.x after 2.6.2, which is the current release. -- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/638289 Title: Install uses CURRENT_USER instead of LOCAL_MACHINE for AssemblyFoldersEx Status in NUnit V2 Test Framework: Fix Released 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
