tag:blogger.com,1999:blog-9537945.post3705752752127255709..comments2008-04-15T16:57:09.636-05:00Comments on DeploymentEngineering.com - The Blog: Learning To Deploy VTSO 3 AddInsChristopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-9537945.post-17996916610511755212008-04-15T16:57:00.000-05:002008-04-15T16:57:00.000-05:00This post is a few months old and I need to replac...This post is a few months old and I need to replace it with a new one ( and a white paper / sample project ) detailing what I learned on deploying VSTO Addins.<BR/><BR/>I was all over the blog posts and forum topics mentioned by others and a summary of what I learned can be found here:<BR/><BR/>http://community.acresso.com/showpost.php?p=413400&postcount=5Christopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comtag:blogger.com,1999:blog-9537945.post-18857660081574427592008-04-15T16:52:00.000-05:002008-04-15T16:52:00.000-05:00These links might be of help for people struggling...These links might be of help for people struggling with VSTO deployment:<BR/>http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2543533&SiteID=1<BR/>http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2837356&SiteID=1<BR/><BR/>They use the '|vstolocal' postfix on the manifest key to disable ClickOnce installation of the .vsto file and 'proper' authenticode certificate to avoid trust prompts. You could also do a custom action to add the add-in to the 'Inclusion List'<BR/><BR/>It is still only a per-user solution, but I believe you might be able to use registry value propagation to get the hkcu bits in the right places for each user. A link I found about propagation:<BR/>http://blogs.msdn.com/mshneer/archive/2007/09/04/deploying-your-vsto-add-in-to-all-users-part-i.aspx<BR/><BR/>Hope these help.Ishmaelnoreply@blogger.comtag:blogger.com,1999:blog-9537945.post-72320586801803836602008-03-31T03:43:00.000-05:002008-03-31T03:43:00.000-05:00You can deploy outlook addin with setup, that writ...You can deploy outlook addin with setup, that write to register all that need. but Visual Studio can help to create setup to your project with all that "write to register". For that you need to create addin in VS2008 with addinn 2003 outlook project (need to install VSTO SE).<BR/>But for addinn 2007 outlook project, VS could not create setup project that bad.<BR/>You can read book "Visual Studio Tools for Office Using C with Excel Word Outlook and InfoPath" for understand more.kadkazhttp://www.blogger.com/profile/17077255892197168277noreply@blogger.com