Registry entry for all the users

[rashwini]

Hi,

After following the basic steps, given in below link
http://www.sparxsystems.com/uml_tool_guide/sdk_for_enterprise_architect/deployingaddins.html

I have create the Add-in, deployed on remote machin. It works fine only for my user.

As i have created the registry entry at
HKEY_CURRENT_USER\Software\Sparx Systems\EAAddins\EATestAddin

But this addin is not available to other user who logged-in on remote machine.

What registry entry is required to be created so that addin will be avilable to all the user?

I have tried placing entry at HKEY_LOCAL_MACHINE, but did not work

Please reply.

[«Midnight»]

Has the add-in been registered in Windows. By this I mean has Windows registered the dll file itself. I think that you need to 'tell' Windows about the file, as well as letting EA know it is there. You seem to have done only the latter step.

Search the EA help, or the forum, for RegSvr32. You need to register the add-in with this Windows application - there is an older, more common, method that does not work with EA add-ins - for it to work. This step is commonly done in the background on machines you use to develop the add-in, and might be done as part of a 'full' installation of the add-in. It is entirely possible you have to add a step to do this on remote machines when you deploy the add-in.

HTH, David

[Frank Horn]

David,

I don't think that's the problem. If the dll were not registered for COM, the AddIn wouldn't be available for any user at all. EA would try to load it and change it's menu text or pop up a message box or whatever.

So I think it's registered for COM, but indeed EA only checks the HKEY_CURRENT_USER\Software\Sparx Systems\EAAddins branch of the registry to see which AddIns to load, and if an EA installation is being used by several people, they will all need an entry there.

[«Midnight»]

I see your point Frank, but that's not the impression I got. I note that the original post referred to users on "remote machine." In such a case the add-in might be distributed via something other than a full install or development environment available to the first user.

[rashwini]

Hi Frank and Midnight,

Thank you for inputs,

But yes Frank is right, Addin is availble for the user whoes registry entry is avilable.

Now i have to create and Installation Package which will create the registry entry under HKEY_CURRENT_USER\Software\Sparx Systems\EAAddins.

and the user have to run this installation package.

only problem is that when installation package is installed by USER1,
USER2 wont be able to run it as it is already been installed.  

Please guide me if anyone who has installed the Addin for all the users (default users) who loggs-in to the machine.

[Frank Horn]

Please guide me if anyone who has installed the Addin for all the users (default users) who loggs-in to the machine.

I don't think it's possible. Maybe you could use an MSI based installation package to write the registry entry for every user on the machine, but even then it would not be there for new user accounts created after your installation.

The only thing I can think of at the moment is to put the entry into a reg file and tell all users who are missing the AddIn to double click it and restart EA. Not nice, but I wouldn't know what else to do.

[rashwini]

I understand

But when i looked at addin provided by sparx "MDG Link for DOORS"

it creates registry entry "DOORS" with value "DoorsInterface.EADoors"
for all the users.

and it is created by installation package "MGD Links for DOORS" as i have noticed it in "Add/ Remove Programs"

I would like to know how it has been implemented