VS 2005 setup, .NET 2 and PIAs, merge module available? RickH 22.02.2006 17:59:29 I have an Office 2003 automation package created in VSTO 2005. It needs to contain .Net 2 and Office 2003 PIAs. I have three separate installs now, but the users often screw it up. Support is difficult, because locations are worldwide and English is often a second or third language for the users...

RE: VS 2005 setup, .NET 2 and PIAs, merge module available? D. 22.02.2006 18:19:27 Emmm ... you did not actually ask a question, but rather made a statement. Abort/Retry/Fail "RickH" wrote: [Quoted Text] > I have an Office 2003 automation package created in VSTO 2005. It needs to > contain .Net 2 and Office 2003 PIAs. > I have three separate installs now, but the users often screw it up. Support > is difficult, because locations are worldwide and English is often a second > or third language for the users...

RE: VS 2005 setup, .NET 2 and PIAs, merge module available? RickH 22.02.2006 18:34:26 Are there merge modules available for .Net 2 framework and Office 2003 PIAs?? Three separate setups to install one Office automation process is costing a huge amount of support costs and ill will from users and IT support people. The standard client has Office installed, no .NET framework.

RE: VS 2005 setup, .NET 2 and PIAs, merge module available? D. 22.02.2006 19:31:36 Well, I might end-up with 2 responses to your message - not sure what happened, but my "last" response to this did not seem to "make it" ... so I'll try again. Currently, from what I've read, "The only supported redistribution method is to use the Office 2003 Update: Redistributable Primary Interop Assemblies. Located here: http://www.microsoft.com/downloads/details.aspx?FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad&DisplayLang=en There is an MSDN write-up about this topic located here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dno2k3ta/html/OfficePrimaryInteropAssembliesFAQ.asp I see no reason why you couldn't write a custom installer that (1) checks what version you need to install and (2) install it. Anyway, read the MSDN article, you might find it helpful. D. "RickH" wrote: [Quoted Text] > Are there merge modules available for .Net 2 framework and Office 2003 PIAs?? > Three separate setups to install one Office automation process is costing a > huge amount of support costs and ill will from users and IT support people. > > The standard client has Office installed, no .NET framework.

RE: VS 2005 setup, .NET 2 and PIAs, merge module available? RickH 22.02.2006 19:46:18 I had read that one. I had heard its not allowed by the license to distribute the PIAs as part of your application setup. I'm distributing internally to a company that has a corporate MS lic for all its software. Why should they make it very difficult to install custom applications? In earlier versions, I could simply add merge modules for the PIAs, and be done with it. It's become a support nightmare.

RE: VS 2005 setup, .NET 2 and PIAs, merge module available? D. 22.02.2006 20:03:35 RickH wrote: "I had heard its not allowed by the license to distribute the PIAs as part of your application setup" I have read nothing indicating this ... the PIA installation has a EULA in it, and scanning over it, I see nothing that indicates as such. The end-user must have a valid license for Microsoft Office product, but they should have that anyway ... From what you've said, it appears the work is going to be put back on you, if you want to improve the installation process for your end-users. But that's software development for ya ... "RickH" wrote: [Quoted Text] > I had read that one. I had heard its not allowed by the license to distribute > the PIAs as part of your application setup. > I'm distributing internally to a company that has a corporate MS lic for all > its software. > Why should they make it very difficult to install custom applications? > In earlier versions, I could simply add merge modules for the PIAs, and be > done with it. > It's become a support nightmare.

RE: VS 2005 setup, .NET 2 and PIAs, merge module available? RickH 23.02.2006 18:18:32 on Peter's blog, I found links to bootstrapper code and a msi installer class that allows you to detect and install VSTO runtime, PIAs, and the msi class sets the CAS policy to Full Trust to the install folder. Absolutely wonderful code samples. Should have been included with VSTO and been a default part of a setup project. Without this, its a real nightmare getting a VSTO project deployed.

RE: VS 2005 setup, .NET 2 and PIAs, merge module available? D. 23.02.2006 18:48:31 You should post the URL here for others that might need this information. ;) "RickH" wrote: [Quoted Text] > on Peter's blog, I found links to bootstrapper code and a msi installer class > that allows you to detect and install VSTO runtime, PIAs, and the msi class > sets the CAS policy to Full Trust to the install folder. > Absolutely wonderful code samples. > Should have been included with VSTO and been a default part of a setup > project. > > Without this, its a real nightmare getting a VSTO project deployed.

Re: VS 2005 setup, .NET 2 and PIAs, merge module available? "Onawole, Clement Oladapo" <dapo[ at ]splasherstech.com> 24.02.2006 12:52:10 I am interested in the URL too. "D." <D[ at ]discussions.microsoft.com> wrote in message news:D1534CC6-11BA-4D4B-BBCC-49C25AB914DB[ at ]microsoft.com... [Quoted Text] > You should post the URL here for others that might need this information. > > ;) > > "RickH" wrote: > >> on Peter's blog, I found links to bootstrapper code and a msi installer >> class >> that allows you to detect and install VSTO runtime, PIAs, and the msi >> class >> sets the CAS policy to Full Trust to the install folder. >> Absolutely wonderful code samples. >> Should have been included with VSTO and been a default part of a setup >> project. >> >> Without this, its a real nightmare getting a VSTO project deployed.