← Back to team overview

nunit-core team mailing list archive

[Bug 638289] Re: Install uses CURRENT_USER instead of LOCAL_MACHINE for AssemblyFoldersEx

 

I want the Nunit to be use by different account. So i am using this
version of nunit(2.6.0 onward). But when i installed the Nunit(with
administrator rights). It put the Nunit under  HKEY_CURRENT_USER instead
of HKEY_LOCAL_MACHINE.

I tried in both Win7 64bit and window XP 32bit, but its the same.
I tried in command prompt with   "msiexec /i <C:\Users\gpagrut\Downloads\NUnit-2.6.0.12035.msi> ALLUSERS=1" , but doesnot work in both Operating system.

Can you please give me some tips to installed or is it the case that
this issues is partially fixed?

Thank You.

Regards
Gopal

-- 
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


References