![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
![]()
Hi,
I have an issue with VSTO deployment. Instead of using ClickOnce deployment, I create the installer from the traditional windows installer. I had issues to add the setup project under the same Solution because the configuration of my registry always got changed from "app.manifest|vstolocal" to "app.manifest". Therefore I did some research on Google and someone said it was a known VS2008 bug. They suggested creating a setup project outside the existing VSTO solution and then add files and assemblies one by one. That solution works and it correctly installed the VSTO addin. However, as soon as I opened up Outlook, I got an exception saying that "the app.manifest may not be valid or the file could not be opened." Does anyone know what might be wrong? Thanks in advance Kyle Huang |
#2
|
|||
|
|||
![]()
Since this is a specific VSTO deployment issue and not an Outlook issue I'd
suggest posting in the VSTO forum on MSDN, where members of the VSTO team hang out and answer questions. They'd have a far better idea of what's going on than anyone here. -- Ken Slovak [MVP - Outlook] http://www.slovaktech.com Author: Professional Programming Outlook 2007. Reminder Manager, Extended Reminders, Attachment Options. http://www.slovaktech.com/products.htm "Mark B" wrote in message ... Hi, I have an issue with VSTO deployment. Instead of using ClickOnce deployment, I create the installer from the traditional windows installer. I had issues to add the setup project under the same Solution because the configuration of my registry always got changed from "app.manifest|vstolocal" to "app.manifest". Therefore I did some research on Google and someone said it was a known VS2008 bug. They suggested creating a setup project outside the existing VSTO solution and then add files and assemblies one by one. That solution works and it correctly installed the VSTO addin. However, as soon as I opened up Outlook, I got an exception saying that "the app.manifest may not be valid or the file could not be opened." Does anyone know what might be wrong? Thanks in advance Kyle Huang |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
VSTO Add-In Deployment | Paulem0071 | Add-ins for Outlook | 3 | October 10th 08 04:58 PM |
Deployment Planning | kdbwtg | Outlook - Installation | 3 | October 12th 07 09:00 PM |
HELP: None of the vsto add-ins load on dev/deployment machines | Rajesh Deshpande | Add-ins for Outlook | 0 | May 4th 07 05:03 PM |
Com AddIns deployment | DavidE | Add-ins for Outlook | 4 | November 5th 06 07:57 AM |
Outlook 2003 shared add-in (NOT VSTO!) deployment problems build with VS2005 | Ken Slovak - [MVP - Outlook] | Add-ins for Outlook | 1 | August 2nd 06 03:29 PM |