Required rights to run TypeMock

Hi,
:idea: This is probrably due to the fact that TypeMock was installed for the admin only ('Just Me') which is the default for TypeMock.
You can ask the admin reinstall TypeMock and to check 'install for Everyone'.

The admin reinstalled typemock, but I get the same error. Starting the debugger it turned out that I have no access to some registry keys:

An unhandled exception of type 'System.UnauthorizedAccessException' occurred in mscorlib.dll

Additional information: Access to the registry key is denied.

Too bad the error doesn't indicate what key should be accessed :wink:

can you tell me what registry keys typemock needs to access to be able to run?

Many thx

:idea:

Using Regmon I found out that the keys in question are:

HKEY_CLASSES_ROOTCLSID{B146457E-9AED-4624-B1E5-968D274416EC}InprocServer32
HKEY_CLASSES_ROOTCLSID{B146457E-9AED-4624-B1E5-968D274416EC}InprocServer32ResetCLSID

The admin will update my access rights and I hope I won't run into any other security restriction (admins... :wink: ).

Thanks for pointing this out.
We must have access to these keys in order to perform code coverage.
We will put better messages for these errors in the future.

I(being "castrated" by admins as cdsys :wink: ) have the same problem. I now have full access to the two mentioned registry entries but I still get the following error when starting VS2005:

---------------------------
Microsoft Visual Studio
---------------------------
The Add-in 'TypeMock.NET' failed to load or caused an exception.
Would you like to remove this Add-in?
If you choose yes, the file it was loaded from, 'C:Documents and SettingsAll UsersApplication DataMicrosoftVisualStudio8.0\AddinsTypeMock.AddIn2005.AddIn', will be renamed.

Error Message: <Unknown Error>
Error number: 8013150a
---------------------------
Yes No
---------------------------

If we don't get around these admin-right-issues we have to drop TypeMock from our *Mock-eval-list. Which I would very much regret!
Thanks for any help
fx3000se

This has been taken offline, the answers should be posted soon

This issue should be fixed in version 3.0.3 :D
The security rights are lower although registery write rights are required for linking, we will change this in future releases