none
Problem creating MSI for VS2008 Outlook addin RRS feed

  • Question

  • Okay....following this (http://msdn.microsoft.com/en-us/library/cc563937.aspx) example, I tried generating an MSI from this (http://social.msdn.microsoft.com/Forums/en-US/vsto/thread/f98edb98-d0f1-4270-a87e-dbcb5cd23b6d) project. I'm trying to create an all-users addon.

    • I got the 2007 PIA's to show up as a prerequisite.
    • I added in the reg key for 64-bit windows (the only OS this is getting deployed to) running 32-bit Office 2007 and put the key in Local Machine only.
    • The code is signed via a deployed code signing certificate in both of the certificate folders.
    • The prerequisites are set to download from the same location as my application, and I have .NET 3.5, 2007 PIA, VSTO 3.0, and Installer 3.1 checked for the MSI.

    Whenever I run the MSI, it is listed in Add/Remove Programs and in the Outlook addin area, but it is disabled for all users. If I try to run Outlook as admin, I can enable it, but it goes back to disabled, and the code is not executed. I can never get the code to execute.

    Anybody have an idea?

    Monday, March 18, 2013 3:15 PM

Answers

  • ok, next try: on machine where it does not Work, navigate to folder where you installed your add-in and double click vsto file - it should bring install window as i recall, then open up Outlook and verify that you get confirmation window that you want to run this add-in.
    • Marked as answer by VulturEMaN Monday, March 25, 2013 1:40 PM
    Friday, March 22, 2013 7:37 AM
  • Ok, your add-in runs fine but needs 2 Things:

    1. You are missing EnableLocalmachineVSTO entry in registry in proper place (http://support.microsoft.com/kb/976811)

    2. manifest entry must be without file:/// and in normal path like c:\..\ with |vstolocal at the end

    • Marked as answer by VulturEMaN Monday, March 25, 2013 1:39 PM
    Monday, March 25, 2013 1:05 PM
  • ok, next try: on machine where it does not Work, navigate to folder where you installed your add-in and double click vsto file - it should bring install window as i recall, then open up Outlook and verify that you get confirmation window that you want to run this add-in.

    Aha! I think we hit something!

    Firstly, I realized that I had the MSI portion of the project pointing at the old clickOnce vsto directory I had done. So it was using an old version. Derp. So I updated it to look at the current rebuild directory for the VSTO stuff:

    U:\Visual Studio 2008\Projects\High Importance Notify\High Importance Notify\bin\Release

    Another thing I noticed...when I run the rebuild process, it seems to try and install the VSTO into my Outlook after recompiling it? Is this normal? Maybe this is another problem?

    And triple aha! When I clicked the VSTO in Program Files (after fixing the first problem from this post), it installed properly and ran properly. It lists the location as "file:///C:/Program Files (x86)/Allegheny County/High Importance Notify/High Importance Notify.vsto" and the name as "High Importance Notify".

    My Setup installer version lists the location as "C:/Program Files (x86)/Allegheny County/High Importance Notify/High Importance Notify.vsto|vstolocal" and the name as "High Importance Beep in Outlook 2007 - Allegheny County".

    So there is definitely something weird going on in the msi creation process.

    • Edited by VulturEMaN Friday, March 22, 2013 11:56 AM
    • Marked as answer by VulturEMaN Monday, March 25, 2013 1:40 PM
    Friday, March 22, 2013 11:54 AM

All replies

  • i assume you are deploying add-in for office 2007 - what service pack for that office is installed? for entries in local machine to Work, it should be SP3 and your add-in should also add registry entry EnableLocalMachineVSTO as described here http://support.microsoft.com/kb/976811

    Tuesday, March 19, 2013 8:02 AM
  • i assume you are deploying add-in for office 2007 - what service pack for that office is installed? for entries in local machine to Work, it should be SP3 and your add-in should also add registry entry EnableLocalMachineVSTO as described here http://support.microsoft.com/kb/976811

    All computers have SP3, and the EnableLocalMachineVSTO reg key is deployed via group policy.
    Tuesday, March 19, 2013 12:33 PM
  • add  VSTO_SUPPRESSDISPLAYALERTS enviroment variable with value 0, restart office app and enable your add-in. Do you see any message box with errors?
    Tuesday, March 19, 2013 1:33 PM
  • Also, if the addin gets disabled before any display alerts are shown Fusion logging may be needed to see what is missing or not loading correctly, causing the addin to become disabled. See http://blogs.msdn.com/b/vsod/archive/2008/04/22/troubleshooting-com-add-in-load-failures.aspx and also http://www.hanselman.com/blog/BackToBasicsUsingFusionLogViewerToDebugObscureLoaderErrors.aspx

    --
    Ken Slovak
    [MVP-Outlook]
    http://www.slovaktech.com
    Author: Professional Programming Outlook 2007
    "DamianD" <=?utf-8?B?RGFtaWFuRA==?=> wrote in message news:ec1e4b8b-25f6-475f-b303-40e7f412df17...
    add  VSTO_SUPPRESSDISPLAYALERTS enviroment variable with value 0, restart office app and enable your add-in. Do you see any message box with errors?

    Ken Slovak MVP - Outlook
    Tuesday, March 19, 2013 3:43 PM
  • add  VSTO_SUPPRESSDISPLAYALERTS enviroment variable with value 0, restart office app and enable your add-in. Do you see any message box with errors?
    No box with errors.
    Tuesday, March 19, 2013 4:12 PM
  • Also, if the addin gets disabled before any display alerts are shown Fusion logging may be needed to see what is missing or not loading correctly, causing the addin to become disabled. See http://blogs.msdn.com/b/vsod/archive/2008/04/22/troubleshooting-com-add-in-load-failures.aspx and also http://www.hanselman.com/blog/BackToBasicsUsingFusionLogViewerToDebugObscureLoaderErrors.aspx

    I've got zero errors being throw, and load behavior keeps getting changed from 3 to 0.

    I haven't tried the Fusion stuff yet, as it looks a little daunting, but I will soon.


    • Edited by VulturEMaN Tuesday, March 19, 2013 4:16 PM
    Tuesday, March 19, 2013 4:15 PM
  • after checking what Ken proposed, use process monitor to see if your add-in dlls are actually read by Outlook process and deploy some test exe app (console) with same .net requirements, etc. to see if computer is actually capable of running such code.

    Tuesday, March 19, 2013 8:18 PM
  • after checking what Ken proposed, use process monitor to see if your add-in dlls are actually read by Outlook process and deploy some test exe app (console) with same .net requirements, etc. to see if computer is actually capable of running such code.

    dll is sitting there in the background.

    Code was already tested and working outside of the MSI. Getting the code running as an all-users addin in an msi is what's broken.

    My instincts tell me it's maybe a prerequisite or something related to the registry keys, but I have no idea.

    Tuesday, March 19, 2013 10:12 PM
  • please check if your add-in's dll is actually loaded into Outlook process by using process monitor or other means. you can also try to manually install all prerequisites and see if something fails. 
    Wednesday, March 20, 2013 6:04 AM
  • please check if your add-in's dll is actually loaded into Outlook process by using process monitor or other means. you can also try to manually install all prerequisites and see if something fails. 

    below are 2 tries...run as normal user, then run as admin

    10:57:15.4519935 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM	SUCCESS	Query: HandleTags, HandleTags: 0x0
    10:57:15.4520050 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\Software\Wow6432Node\Microsoft\Office\Outlook\Addins	ACCESS DENIED	Desired Access: Read/Write
    10:57:15.4520358 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM	SUCCESS	Query: HandleTags, HandleTags: 0x0
    10:57:15.4520451 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\Software\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Desired Access: Read
    10:57:15.4520548 AM	OUTLOOK.EXE	39124	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    10:57:15.4520669 AM	OUTLOOK.EXE	39124	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Index: 0, Name: Allegheny County.High Importance Notify
    10:57:15.4520774 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:15.4520853 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	ACCESS DENIED	Desired Access: Read/Write
    10:57:15.4520974 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:15.4521040 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	Desired Access: Read
    10:57:15.4521176 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\LoadBehavior	SUCCESS	Type: REG_DWORD, Length: 4, Data: 0
    10:57:15.4521266 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\FriendlyName	SUCCESS	Type: REG_SZ, Length: 112, Data: High Importance Beep in Outlook 2007 - Allegheny County
    10:57:15.4521342 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	BUFFER OVERFLOW	Length: 144
    10:57:15.4521408 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	SUCCESS	Type: REG_SZ, Length: 202, Data: C:\Program Files (x86)\Allegheny County\High Importance Notify\High Importance Notify.vsto|vstolocal
    10:57:15.4521478 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Description	SUCCESS	Type: REG_SZ, Length: 116, Data: Plays Pager.wav when a high importance email is received.
    10:57:15.4521553 AM	OUTLOOK.EXE	39124	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	
    10:57:15.4521623 AM	OUTLOOK.EXE	39124	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	
    10:57:15.4521813 AM	OUTLOOK.EXE	39124	RegQueryKey	HKCU\Software\Microsoft\Office\12.0\Outlook	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:15.4521882 AM	OUTLOOK.EXE	39124	RegOpenKey	HKCU\Software\Microsoft\Office\12.0\Outlook\Addins	SUCCESS	Desired Access: Read/Write
    10:57:15.4521994 AM	OUTLOOK.EXE	39124	RegCloseKey	HKCU\Software\Microsoft\Office\12.0\Common\LanguageResources	SUCCESS	
    10:57:15.4522069 AM	OUTLOOK.EXE	39124	RegQueryValue	HKCU\Software\Microsoft\Office\12.0\Outlook\Addins\SearchToolbarsDisabled	SUCCESS	Type: REG_DWORD, Length: 4, Data: 1
    

    and

    10:57:15.4538086 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM	SUCCESS	Query: HandleTags, HandleTags: 0x0
    10:57:15.4538215 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\Software\Wow6432Node\Microsoft\Office\Outlook\Addins	ACCESS DENIED	Desired Access: Read/Write
    10:57:15.4538357 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM	SUCCESS	Query: HandleTags, HandleTags: 0x0
    10:57:15.4538445 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\Software\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Desired Access: Read
    10:57:15.4538550 AM	OUTLOOK.EXE	39124	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    10:57:15.4538722 AM	OUTLOOK.EXE	39124	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Index: 0, Name: Allegheny County.High Importance Notify
    10:57:15.4538834 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:15.4538919 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	ACCESS DENIED	Desired Access: Read/Write
    10:57:15.4539042 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:15.4539124 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	Desired Access: Read
    10:57:15.4539236 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\LoadBehavior	SUCCESS	Type: REG_DWORD, Length: 4, Data: 0
    10:57:15.4539359 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\FriendlyName	SUCCESS	Type: REG_SZ, Length: 112, Data: High Importance Beep in Outlook 2007 - Allegheny County
    10:57:15.4539444 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	BUFFER OVERFLOW	Length: 144
    10:57:15.4539513 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	SUCCESS	Type: REG_SZ, Length: 202, Data: C:\Program Files (x86)\Allegheny County\High Importance Notify\High Importance Notify.vsto|vstolocal
    10:57:15.4539580 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Description	SUCCESS	Type: REG_SZ, Length: 116, Data: Plays Pager.wav when a high importance email is received.
    10:57:15.4539658 AM	OUTLOOK.EXE	39124	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	
    


    and

    10:57:16.7330351 AM	OUTLOOK.EXE	39124	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    10:57:16.7330448 AM	OUTLOOK.EXE	39124	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Index: 0, Name: Allegheny County.High Importance Notify
    10:57:16.7330647 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:16.7330762 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	ACCESS DENIED	Desired Access: Read/Write
    10:57:16.7330892 AM	OUTLOOK.EXE	39124	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:16.7330973 AM	OUTLOOK.EXE	39124	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	Desired Access: Read
    10:57:16.7331088 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\LoadBehavior	SUCCESS	Type: REG_DWORD, Length: 4, Data: 0
    10:57:16.7331094 AM	OUTLOOK.EXE	39124	RegQueryKey	HKCU	SUCCESS	Query: HandleTags, HandleTags: 0x0
    10:57:16.7331194 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\FriendlyName	SUCCESS	Type: REG_SZ, Length: 112, Data: High Importance Beep in Outlook 2007 - Allegheny County
    10:57:16.7331224 AM	OUTLOOK.EXE	39124	RegOpenKey	HKCU\Software\Policies\Microsoft\Office\12.0\Outlook\Security	NAME NOT FOUND	Desired Access: Read/Write
    10:57:16.7331272 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	BUFFER OVERFLOW	Length: 144
    10:57:16.7331329 AM	OUTLOOK.EXE	39124	RegQueryValue	HKCU\Software\Microsoft\Office\12.0\Outlook\Security\EnableRememberPwd	NAME NOT FOUND	Length: 144
    10:57:16.7331345 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	SUCCESS	Type: REG_SZ, Length: 202, Data: C:\Program Files (x86)\Allegheny County\High Importance Notify\High Importance Notify.vsto|vstolocal
    10:57:16.7331420 AM	OUTLOOK.EXE	39124	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Description	SUCCESS	Type: REG_SZ, Length: 116, Data: Plays Pager.wav when a high importance email is received.
    10:57:16.7331505 AM	OUTLOOK.EXE	39124	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	
    

    and below is from when I ran as admin.

    10:57:25.1634759 AM	OUTLOOK.EXE	39540	RegQueryKey	HKLM	SUCCESS	Query: HandleTags, HandleTags: 0x0
    10:57:25.1634871 AM	OUTLOOK.EXE	39540	RegOpenKey	HKLM\Software\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Desired Access: Read/Write
    10:57:25.1635016 AM	OUTLOOK.EXE	39540	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    10:57:25.1635134 AM	OUTLOOK.EXE	39540	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Index: 0, Name: Allegheny County.High Importance Notify
    10:57:25.1635242 AM	OUTLOOK.EXE	39540	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:25.1635315 AM	OUTLOOK.EXE	39540	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	Desired Access: Read/Write
    10:57:25.1635448 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\LoadBehavior	SUCCESS	Type: REG_DWORD, Length: 4, Data: 0
    10:57:25.1635520 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\FriendlyName	SUCCESS	Type: REG_SZ, Length: 112, Data: High Importance Beep in Outlook 2007 - Allegheny County
    10:57:25.1635596 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	BUFFER OVERFLOW	Length: 144
    10:57:25.1635668 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	SUCCESS	Type: REG_SZ, Length: 202, Data: C:\Program Files (x86)\Allegheny County\High Importance Notify\High Importance Notify.vsto|vstolocal
    10:57:25.1635734 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Description	SUCCESS	Type: REG_SZ, Length: 116, Data: Plays Pager.wav when a high importance email is received.
    10:57:25.1635810 AM	OUTLOOK.EXE	39540	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	
    10:57:25.1635873 AM	OUTLOOK.EXE	39540	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	
    

    and

    10:57:25.1649607 AM	OUTLOOK.EXE	39540	RegOpenKey	HKLM\Software\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Desired Access: Read/Write
    10:57:25.1649725 AM	OUTLOOK.EXE	39540	RegSetInfoKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    10:57:25.1649798 AM	OUTLOOK.EXE	39540	RegEnumKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Index: 0, Name: Allegheny County.High Importance Notify
    10:57:25.1649891 AM	OUTLOOK.EXE	39540	RegQueryKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins	SUCCESS	Query: HandleTags, HandleTags: 0x400
    10:57:25.1649964 AM	OUTLOOK.EXE	39540	RegOpenKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	Desired Access: Read/Write
    10:57:25.1650063 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\LoadBehavior	SUCCESS	Type: REG_DWORD, Length: 4, Data: 0
    10:57:25.1650148 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\FriendlyName	SUCCESS	Type: REG_SZ, Length: 112, Data: High Importance Beep in Outlook 2007 - Allegheny County
    10:57:25.1650220 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	BUFFER OVERFLOW	Length: 144
    10:57:25.1650284 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Manifest	SUCCESS	Type: REG_SZ, Length: 202, Data: C:\Program Files (x86)\Allegheny County\High Importance Notify\High Importance Notify.vsto|vstolocal
    10:57:25.1650377 AM	OUTLOOK.EXE	39540	RegQueryValue	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify\Description	SUCCESS	Type: REG_SZ, Length: 116, Data: Plays Pager.wav when a high importance email is received.
    10:57:25.1650468 AM	OUTLOOK.EXE	39540	RegCloseKey	HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify	SUCCESS	
    

    and then we hit this, which seems to be the problem:

    10:57:31.3512416 AM	OUTLOOK.EXE	39540	CreateFile	C:\Program Files (x86)\Allegheny County\High Importance Notify\High Importance Notify.vsto|vstolocal	NAME INVALID	Desired Access: Read Attributes, Dis, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
    10:57:31.3513216 AM	OUTLOOK.EXE	39540	CreateFile	C:\Program Files (x86)\Allegheny County\High Importance Notify\High Importance Notify.vsto|vstolocal	NAME INVALID	Desired Access: Read Attributes, Dis, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
    10:57:31.3514073 AM	OUTLOOK.EXE	39540	CreateFile	C:\Program Files (x86)\Allegheny County\High Importance Notify\High Importance Notify.vsto|vstolocal	NAME INVALID	Desired Access: Read Attributes, Dis, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
    

    I know that whatever my problem is...it's gotta be something boneheaded. I have slight experience in coding but nothing worth writing home about, and alot of this VSTO stuff is well above my head.





    Wednesday, March 20, 2013 8:04 PM
  • show us screenshots of your registry values in HKLM\SOFTWARE\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify
    Thursday, March 21, 2013 8:22 AM
  • show us screenshots of your registry values in HKLM\SOFTWARE\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify

    There's nothing there. I'm only deploying to 64-bit windows running 32-bit Office 2007, so I put all reg values in HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins\Allegheny County.High Importance Notify

    http://i.imgur.com/0t0V8k2.png

    The LoadBehavior keeps changing from 3 to 0 immediately on launch of Outlook ONLY when I run as admin. If I run as normal user, it stays at 3 but never actually runs.

    Thursday, March 21, 2013 1:13 PM
  • are you sure that VSTO runtime is actually installed on that machine? how did you check it?
    Thursday, March 21, 2013 2:56 PM
  • are you sure that VSTO runtime is actually installed on that machine? how did you check it?

    See, that's what I was concerned about myself. I tried adding prerequisite checking as per the tutorial, but I haven't a clue if its working properly.

    I manually ran installers from Office2007PIA and VSTOR30 to double check. VSTOR30 is installed and comes up with options to "remove" or "repair". Office2007PIA closes almost immediately after launching, and checking the error log shows that its already installed....uninstalling through add/remove and reinstalling results in the same thing. Everything appears to be okay with that install though :/

    Thursday, March 21, 2013 3:33 PM
  • ok, next try: on machine where it does not Work, navigate to folder where you installed your add-in and double click vsto file - it should bring install window as i recall, then open up Outlook and verify that you get confirmation window that you want to run this add-in.
    • Marked as answer by VulturEMaN Monday, March 25, 2013 1:40 PM
    Friday, March 22, 2013 7:37 AM
  • ok, next try: on machine where it does not Work, navigate to folder where you installed your add-in and double click vsto file - it should bring install window as i recall, then open up Outlook and verify that you get confirmation window that you want to run this add-in.

    Aha! I think we hit something!

    Firstly, I realized that I had the MSI portion of the project pointing at the old clickOnce vsto directory I had done. So it was using an old version. Derp. So I updated it to look at the current rebuild directory for the VSTO stuff:

    U:\Visual Studio 2008\Projects\High Importance Notify\High Importance Notify\bin\Release

    Another thing I noticed...when I run the rebuild process, it seems to try and install the VSTO into my Outlook after recompiling it? Is this normal? Maybe this is another problem?

    And triple aha! When I clicked the VSTO in Program Files (after fixing the first problem from this post), it installed properly and ran properly. It lists the location as "file:///C:/Program Files (x86)/Allegheny County/High Importance Notify/High Importance Notify.vsto" and the name as "High Importance Notify".

    My Setup installer version lists the location as "C:/Program Files (x86)/Allegheny County/High Importance Notify/High Importance Notify.vsto|vstolocal" and the name as "High Importance Beep in Outlook 2007 - Allegheny County".

    So there is definitely something weird going on in the msi creation process.

    • Edited by VulturEMaN Friday, March 22, 2013 11:56 AM
    • Marked as answer by VulturEMaN Monday, March 25, 2013 1:40 PM
    Friday, March 22, 2013 11:54 AM
  • during compilation VS will update registry entries so you have your add-in run automatically. Do not test deployment of msi on your dev machine because you can never be sure if those 2 processes will not interfere and produce results that can never be achieved on normal user machine.

    As for msi - |vstolocal is ok with msi installation type. Hard to tell what seems to be wrong without actually installing your add-in. Maybe try to install using msi and manually change ManifestLocation in registry to be of type file:///...|vstolocal and see if it Works.

    Friday, March 22, 2013 12:49 PM
  • As for msi - |vstolocal is ok with msi installation type. Hard to tell what seems to be wrong without actually installing your add-in. Maybe try to install using msi and manually change ManifestLocation in registry to be of type file:///...|vstolocal and see if it Works.

    I tried that....no dice. It still changes the LoadBehavior to 0 as soon as I launch as admin.
    Friday, March 22, 2013 3:21 PM
  • Hard to tell what seems to be wrong without actually installing your add-in.

    Do you want me to package up everything and send it on over? haha.

    Seriously though, you've been a huge help troubleshooting this with me so far.

    Friday, March 22, 2013 9:23 PM
  • upload your add-in to skydrive or somewhere else and give here link, i will try to see what is wrong on monday
    Saturday, March 23, 2013 8:10 AM
  • upload your add-in to skydrive or somewhere else and give here link, i will try to see what is wrong on monday

    http://www.mediafire.com/download.php?kqvfweaoza79ky8

    I cleared out all of the files from the DotNetFX35 folders.

    Not sure if you'd have to do the same stuff I did to get the O2007PIAs working.

    Saturday, March 23, 2013 1:59 PM
  • i checked your installer - it does not even install proper entries in registry. No Wonder it does not Work. Please fix it first - and test it on other machine then the dev one - your current problems clearly show how messy it gets when you test on Development machine.

    Monday, March 25, 2013 8:39 AM
  • i checked your installer - it does not even install proper entries in registry. No Wonder it does not Work. Please fix it first - and test it on other machine then the dev one - your current problems clearly show how messy it gets when you test on Development machine.

    I did test the installer on a different computer after you asked me to...it put the proper x64 entries in on that computer. You sure you looked in the Wow6432Node area of the registry?
    Monday, March 25, 2013 9:07 AM
  • no, i tested your add-in first on 32 bit Windows office 2007 machine. So your setup is only for 64 bit Windows? ok, I will test it on 64 bit one.
    Monday, March 25, 2013 10:25 AM
  • no, i tested your add-in first on 32 bit Windows office 2007 machine. So your setup is only for 64 bit Windows? ok, I will test it on 64 bit one.

    Yea, this addin is only going to be for Win7 x64 running Office 2007 (which only runs as x86). Since it's x86 running on x64, it'll install to "C:\Program Files (x86)\..." and throw the reg key in "HKLM\Software\Wow6432Node\Microsoft\..."

    The only computers that we have that run 32-bit in our office are training room desktops and always-out-of-office laptops, and neither need to hear any sort of beeping. Just normal office users need that. And anyways, a majority of our office are running nice Core-i7's and 8-16GB RAM....so x64 is definitely necessary.


    • Edited by VulturEMaN Monday, March 25, 2013 11:26 AM
    Monday, March 25, 2013 11:26 AM
  • Ok, your add-in runs fine but needs 2 Things:

    1. You are missing EnableLocalmachineVSTO entry in registry in proper place (http://support.microsoft.com/kb/976811)

    2. manifest entry must be without file:/// and in normal path like c:\..\ with |vstolocal at the end

    • Marked as answer by VulturEMaN Monday, March 25, 2013 1:39 PM
    Monday, March 25, 2013 1:05 PM
  • I was already pushing out that reg key via GPO in my environment, but I added it into the build. Additionally, I also unnecessarily added it into the Wow6432Node area as well.

    I removed the file:/// and will rebuild and test on a non-dev pc.

    Monday, March 25, 2013 1:33 PM
  • Everything works after removing file and adding that reg key into the actual project.

    You are the savior of our office, and I would give you a cold beer right now if it wasn't 9am. Maybe a cold glass of bourbon?

    Thank you so very much. I knew it was gonna be something stupid :P

    Monday, March 25, 2013 1:42 PM