I need the Add-In to be available to all users on a machine.
I'm working from MSDN documents "Deploying Visual Studio 2005 Tools for Office Solution Using Windows Installer (Part 1 of 2) & (Part 2 of 2).
I'm using the example in (Part 2 of 2), page 11 verbatim.
/assemblyName="OutlookAddin.dll" /targetDir="[TARGETDIR]\"
/solutionCodeGroupName="MyCompanyName.OutlookAddin"
/solutionCodeGroupDescription="Code group for OutlookAddin"
/assemblyCodeGroupName="OutlookAddin"
/assemblyCodeGroupDescription="Code group for OutlookAddin"
/allUsers=[ALLUSERS]
I've tried changing to /allUsers=[1] but to no avail. Can someone help me determine what I'm doing wrong
Thanks in advance,
Ron |<:^)
Installed OutLook 2003 Add-in not available to "All Users"
Sasky02
I understand your problem and I agree with you that multi-account deployment is something that would be useful.
A common deployment method however, especially in Enterprise environments, is to deploy software when the user logs on to the Enterprise domain.
Again... I agree with your point of view, the scope should not be limited to one user. I guess that would be another request for VSTO 'v3'
-= Maarten =-
RKN_India
1)If I change my registry keys from HKCU to HKLM, the Add-in will load in Office 2003, but it won't appear as a COM Add-in
2)In Office 2007, it won't even load
Just a curiosity...has anyone ever thought how much this will break previuos add-ins
Now I really don't know what to do:
1)Should I change to HKLM, in order to let Outlook 2003 limited user accounts (not administrators) to install my add in on their computers
2)Or should I stick with HKCU, so I will be "almost sure" that Outlook 2007 users might be able to use it
And finally, has anyone considered the problem of limited user accounts and Outlook 2007 How is it possible for a LUA to install and use a VSTO add in with these conditions
I believed VSTO SE would have been a bridge between Office 2003 and Office 2007...not a river to cross without a bridge!
Sorry for the post, but users are asking for solutions, without ME changing EVERY time the registry...
ChandlerDeng
Thank you Maarten,
I just tried changing the [] to "" and it still doesn't work. The .NET 2.0 framework, PIA, and VSTOR install for all users but the Add-In doesn't. I assume that the [ALLUSERS] macro should be working as should the machine policy "1". Neither seem to be. Am I missing something with the command syntax /allUsers="1" The Add-In builds and deploys with no errors. This is very hard to trouble shoot.
What else can I check or test
Thanks,
Ron |<:^)
Blaine
I second this!!
Before using VSTO, I made my plugin that could be installed for All Users...and today I found that this has gone away AGAIN
Please tell me there is any solution for this...
Bye
LastHope
John Walker
But note that if you do this (put the keys in HKLM instead of HKCU to get a "All User" install) , then the add-in will not load in Office 2007, (at least with my Excel add-in) - Excel 2007 seems to require the key to be in HKCU, (and possibly require that it is not in HKLM need to verify that) Did anyone have different experience
John F
tswaters
I do not understand this part... "Hence the addin is deployed only to the current user. This is how it has been designed in VSTO 2005."
How are we to make practical use of VSTO Outlook 2003 Add-ins with the deployment scope limited to the logged in user
Please help,
Ron |<:^)
BladeWise
Yes, you are right. That issue is covered in one of the other threads a couple of days ago...
Here is the thread with an explanation from Andrew Cherry (MSFT)
http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1480248&SiteID=1
-= Maarten =-
Abbasi
I've got VSTO through my MSDNA...VSTO v3 will be available too Will work with VS 2005
VSTO 'v3' is currently in a very very early status. The first CTP (Community Technical Preview) version is available.
Here you can find the information on how to get the preview version. Remember there are prereqs, one of them is that you have Office 2007 TR1 installed. And yes, it works with VS 2005 (at least, the CTP does...)
Keep in mind that the CTP is subject to a huge amount of changes and is only intended to serve as a preview!
Repeting the Registry entries also for the Local Machine wouldn't be enough No Hacks at all available
What was the purpose of taking away this chance When I made my plugin with the template of VS 2003, I had the chance to choose between "All Users" and "Only who's installing"...
Thread continued here
-= Maarten =-
PS:
To avoid threads to grow huge I will mark this thread as answered. Please start new threads for additional questions.
PS2:
Thanks for YOUR patience, I do this for fun ...
jlandheer
I believe you have to set the tag like this:
/allUsers="1"
If you use the [...] brackets it is going to try to replace it with the installation macro. [TARGETDIR] is replaced with the target directory, [ALLUSERS] with the All users setting at install time. [1] is a non existing macro.
Here is the explanation from part 1:
This parameter determines whether the policy is created at the machine level (value = "1") or user level (value = ""). You can use the [ALLUSERS] installation macro defined at install time from the Windows Installer.
-= Maarten =-
John Gossman - MSFT
Hi Maarten,
just a few questions:
- Repeting the Registry entries also for the Local Machine wouldn't be enough No Hacks at all available
- What was the purpose of taking away this chance When I made my plugin with the template of VS 2003, I had the chance to choose between "All Users" and "Only who's installing"...
- I've got VSTO through my MSDNA...VSTO v3 will be available too Will work with VS 2005
Thank you very much for your patienceBye
LastHope
juan carlos ceresola
Hello Pallavi,
Is there a simple method we can use to allow the Add-In to be trusted by all Users A Registry modification or VSTO Setup project modification
It is important that the Outlook 2003 Add-In be deployed in large numbers to stations with multiple users.
Can this be accomplished without having each user install the Add-In themselves
Thanks,
Ron |<:^)
Vishwanatha Nagur
The issue is solved on the following thread.
http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=357677&SiteID=1
The defaults in the examples from document "Deploying Visual Studio Tools for Office Soulutions Using Windows Installer (Part 1 of 2) and (Part 2 of 2)" cause the Add-in to be registerd in a way that makes the Add-in only available to the user doing the install. You will need to change the Registery entries to go under HKEY_LOCAL_MACHINE instead of HKEY_CURRENT_USER.
To do this, select in the Solutions Explorer the "OutlookAddinSetup" object. Next, at the top of the Solutions Explorer select the "Registery Editor". Open HKEY_CURRENT_USER/Software and "cut" both "Classes" and "Microsoft" keys and paste them to HKEY_CURRENT_USER/Software.
Re-build the OutlookAddinSetup project, or re-build the entire project and test the deployment. Log in as another user to verify that the Add-In is available to another user besides the one who installed the Add-in.
Thanks,
Ron Blood |<:^)
John M 37373737
The VSTO Outlook addin's setup project creates registry entries under HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins and not under HKLM. Hence the addin is deployed only to the current user. This is how it has been designed in VSTO 2005.
Thanks,
Pallavi