Darryn Lavery -- MSFT

I am pleased to annouce that we have released an updated to the Windows Installer deployment article for Visual Studio 2005 Tool for Office Second Edition.

The article is available at:

http://go.microsoft.com/fwlink/ LinkID=57779

We will be updated the article for Vista in the near future.

If you have any questions, please feel free to open a new thread.

Thanks and regards,

Darryn Lavery [Microsoft]



Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Siddhu

great work. Thanks.

But is there any way by which we can create single setup file (which have all prerequisites included in it), because whenever we select bootstraps for prerequisites an extra Setup.exe is also created.

And if we select "Download prerequisites from the same location as my location" then for prerequisites one more folder is created.

Such kind of scenarios are not suitable for download from website, as we cant tell clients to download all files one by one (or in a zip file).

Regards
Sid







Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Bill Coan

Darryl,

Is there any chance you could add a little more information to your article, to clarify the Windows SDK that you have in mind, and perhaps to explain the compilation procedure a bit more for the benefit of Office vba developers





Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Bill Coan

Darryn,

Wow, even when you don't have time to reply in this forum, it looks as though you have time to get your article updated. That was fast! Thanks.

Is there any chance that other users of your article will be working on WinXPSP2 If so, do you still want them to download the WinVista SDK Will the WinVista SDK components all run on WinXPSP2

You're probably wondering why I would try to develop software on a WinXPSP2 machine at this point As it happens, it is the only machine I have that has Office 2003 on it, and as you know, I can't install VSTO2005 on a machine that lacks Office 2003.

Thanks for any clarity you can provide. I'll keep checking the article to see if it changes from day to day. Also, if you happen to have time to drop in and reply, that would be cool, too. Thanks again.





Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Darryn Lavery -- MSFT

Hi Siddhu,

As you found out ther are two components to the instller: setup.exe checks for installs and the pre-requisites and the MSI installs the solution & sets the security policy. Unfortuneately you will need both and there is no way to produce just one file. Alternatively you could package the installer into a single zip and distribute it that way.

Thanks

Darryn





Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Darryn Lavery -- MSFT

Hi Bill,

Regarding the Vista SDK.

Setup.exe checks for and installs .NET, VSTO runtime, VSTO language pack and the Office Primary Interop Assemblies. The checks for these packages are stored in the bootstrapper packages (product.xml, package.xml). In most cases the bootstrapper package does a registry or product code check. But in some cases like the PIAs we need to run code to detect if Office is present (this is ComponentCheck.cpp). This code must be written in C++ as it is not guanteed that .NET 2.0 is present when the user runs setup.

VSTS, VS Pro have a C++ compiler but the original VSTO SKU did not. However, the Platform SDK does have a C++ compiler. Each version of the Platform SDK after the latest operating system. For compiling this code on XP SP2 you can use the Vista SDK.

Hope that helps.

Thanks and regards,

Darryn Lavery [MSFT]





Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Bill Coan

Darryn,

Thanks for this helpful added detail. I realize that all of this probably would have been obvious to, say, a C++ programmer, but it wasn't obvious from an Office vba perspective, so I'm especially grateful for the extra orientation.

One further question: Why make us compile our own copy of ComponentCheck.exe Why not provide it as part of the download Were you trying to enable us to modify the source code before compiling it, or was their some other reason





Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Mike Walker

Hi Bill

I think the code work around Componentcheck.cpp is distributed to ease the internal release issues of Microsoft and to allow us to use the code to add further functionality that maybe required.

I agree and have seen this been sent precompiled so would hope the MS guys hear this and move towards removing this burdon from the non C++ programmers.

Regards






Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

LastHope

Hi,
maybe I'm the only one who hasn't seen much differences between this article and the same article for the first edition of VSTO
I believe it'd be rather important if you could add a link in order to explain to a "simple user" how to understand Group Policy and publishing of an msi between LUA: it's quite sad to discover that Office 2007 won't permit to install add-ins which aren't deployed in HKLM (as many people has done following advices in this forum)...

I have got users with Limited User Account: how can I explain to them how to switch to Administrator, open Group Policy and publish mi add-in to the LUA

Thank you

LastHope





Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Pierre Savard

Thanks this new article.

I try to making working my outlook 2003 plugin to another computer without success from 1 week now.

I followup your tutorial and I still have som problem. I add all my satellite DLL in the GAC with the setup projet, but I have security issue again...

Do I need to add a trust on each satellite DLL ethier if I put it in the GAC IF so how I can use the SetSecurity projet to add this satellite DLL

DO I have something to do with the minifest file if I use my setup program to deploy my addins

Thanks...





Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

Shinjae

I also have the same problems...

I even tried old version and new version but both version is not working at all.
I tried manually add CASPOL but it seems that doesn't help me.

I'm using VS2005 w/ VSTO 2005 SE for deployment of my Outlook add-in.

PLEASE HELP US....




Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

whihathac

hey hi all,

is there any way to check if outlook(or any process) is running b4 statring the installation,

is there any property in Launch Conditions, i need to specify






Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

BenDowling

The article is excellent, and has helped me to build an installer that works for both Outlook 2003 and Outlook 2007. However, I have run into an issue where the user has both Office 2003 and Office 2007 installed, but only one version of Outlook.

The problem could be avoided by changing my "Office2003Exists" and "Office2007Exists" checks to Outlook, rather than Office, checks. Is it possible to check for Outlook using ComponentCheck.exe Presumably all I need is the GUID for Outlook, which can be passed to ComponentCheck as an argument. Where can I find the GUID for Outlook 2003 and 2007

Or, is there an alternative approach to checking for Outlook rather than Office

Many thanks in advance, Ben







Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

davidMartin

Hi Ben,

Outlook 2003 componentID : {14D3E42A-A318-4D77-9895-A7EE585EFC3B}
Outlook 2007 componentID : {ED569DB3-58C4-4463-971F-4AAABB6440BD}

I found them using the orca tool provided with the Windows SDK.

Hope its help...

David




Re: Visual Studio Tools for Office New Deployment Article for VSTO2005 SE

mkmike

davidMartin wrote:
Hi Ben,

Outlook 2003 componentID : {14D3E42A-A318-4D77-9895-A7EE585EFC3B}
Outlook 2007 componentID : {ED569DB3-58C4-4463-971F-4AAABB6440BD}

I found them using the orca tool provided with the Windows SDK.

Hope its help...

David

That information is just what I was looking for but I am curious as to how you used Orca to get that information.