Hi,

Would appreciate if anyone could help me on this. I'm packaging Microsoft Visio Viewer 2007 and since it has one MSI and one MSP, i created an MSI out of a snapshot. By right, PC's that doesn't have Ms Visio installed, all Visio files can be opened by default in IE if the Visio Viewer is installed. My problem is that the MSI i generated doesn't open automatically with IE. I have to manually choose IE. I tried playing around with File Association and some registries but failes. It's been a few days that this is bugging me. Appreicate any help on how can i associate these VSD and other visio files to open with IE by default. Thanks in advance

Harjinder
WHO Packager.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi Harjinder Singh,

To associate .vsd with IE , create an entry in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.vsd\OpenWithList
Name:a
Type: String
Value: iexplorer.exe
MRUList:a
Answered 08/05/2008 by: rakesh.kumar
Senior Yellow Belt

Please log in to comment
0
Thanks Rakesh, but this application is to be deployed to All Workstation on a machine based installation. Can we add this HKLM instead?
Answered 08/05/2008 by: PackageExpert
Blue Belt

Please log in to comment
0
Do not re-package office products.
Apply the patch (MSP) to an AIP (Administrative Installation Point) so they will be merge instead.
msiexec /a for creating the AIP
msiexec /a /p for the "merge"
Answered 08/05/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: AngelD
Do not re-package office products.
Come on, Kim. Don't be coy! What you should have said was 'Do not re-package ANY application which comes delivered as an MSI or whose Setup.EXE extracts and executes an MSI. There may be scenarios when it is unavoidable but, in x years of doing this stuff, I have yet to come across one.
Answered 08/06/2008 by: VBScab
Red Belt

Please log in to comment
0
There may be scenarios when it is unavoidable but, in x years of doing this stuff, I have yet to come across one.
Ian, are you saying that you have never had to re-package a vendor MSI?

I have done a few due to the deployment solution used couldn't handle the default MSI or EXE wrapped MSIs.
(Most of the time I've re-package non-vendor MSIs due to less-good quality.)

Don not re-package ANY application which comes delivered as an MSI
Sounds more like a law then a recommendation to me [;)]
Answered 08/06/2008 by: AngelD
Red Belt

Please log in to comment
0
In a word, no.
Answered 08/06/2008 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: harjind

Thanks Rakesh, but this application is to be deployed to All Workstation on a machine based installation. Can we add this HKLM instead?


No, Don,t add this in HKLM
Add this Registries in your package
Answered 08/06/2008 by: rakesh.kumar
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: rakesh.kumar
No, Don,t add this in HKLM
Add this Registries in your package
What?!? I appreciate that English isn't your first language but this doesn't make sense at all. What I *think* you're saying is to add the entries to the Registry. Even if that were the right way to do that, - which it isn't - one would still have to specify which hive the entry would go into, i.e. HKCR (using value '0' for the 'Root' column), HKCU (1), HKLM (2)

There's no reason whatsoever why it can't go into HKLM, if that's what the OP wants.
Answered 08/06/2008 by: VBScab
Red Belt

Please log in to comment
0
Bonjour,

Okkay... lets make life simple here.

Do the following:

1. In your pacakge / computer (if you want to test) open the HKCR and search for the .vsd file extention.
2. Mention the ProgID for InternetExplorer.Application in HKCR under the default.
3. Create a new key under HKCR\.vsd named InternetExplorer.Application
4. Create another key HKCR\.vsd\InternetExplorer.Application\ShellNew

This will enable the .vsd files to open using the internet explorer. That is how you build file associations on computers.

regards,
Tushar singh
Answered 08/06/2008 by: matrixtushar
Purple Belt

Please log in to comment
0
Installing Visio Viewer will by default associate VSD files to be open with IE.
So it you intend to install this package to alot of computers I would suggest you do it the right way from beginning.
Answered 08/06/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

ORIGINAL: rakesh.kumar
No, Don,t add this in HKLM
Add this Registries in your package
What?!? I appreciate that English isn't your first language but this doesn't make sense at all. What I *think* you're saying is to add the entries to the Registry. Even if that were the right way to do that, - which it isn't - one would still have to specify which hive the entry would go into, i.e. HKCR (using value '0' for the 'Root' column), HKCU (1), HKLM (2)

There's no reason whatsoever why it can't go into HKLM, if that's what the OP wants.



Ian
Instead of concentrating of on What is my First Language, if you had gone the series of Replies, better you could understood what i am Reffering
Answered 08/06/2008 by: rakesh.kumar
Senior Yellow Belt

Please log in to comment
0
Hello everyone, thanks for the input. I had problems because i repackaged the MSI. The reason I repackaged was because there is Visio Viewer SP1 MSP. I tried to merge the MSP using msiexec /a MSI /p Patch but it was unsuccessful. Had i merge it, it would be much easier to deploy it as a single package. So what I did was to take the original Microsoft MSI, include the patch in one of the directory and create a Run Command to install the patch after the MSI installation. It worked.

The input about the file association will be of good knowledge to me. Thanks for the recommendations.

Regards
Harjinder
Answered 08/06/2008 by: PackageExpert
Blue Belt

Please log in to comment
0
ORIGINAL: rakesh.kumar
Instead of concentrating of on What is my First Language, if you had gone the series of Replies, better you could understood what i am [strikethrough]Reffering[/strikethrough] referring
...which was...what? Was my guess wrong? Do share with us.
Answered 08/07/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi folks,
like Kim suggested, this should be done with admin install an the application of the patch to it.
However, i can understand Harjinder's temptation to repackage this, because the patching does not work out of the box.

The problem is, that "vviewer.msi" lacks the 'AdminExecuteSequence' table. Because of this, a admin install isn't possible.
To deploy Visio Viewer 2007 with SP1 injected, we have to do the following steps:
1. We need to append the 'AdminExecuteSequence' table to vviewer.msi.
In the Installer SDK, search for 'Sequence.msi' and open it in ORCA.
export the 'AdminExecuteSequence' table to your work directory.
Now open 'vviewer.msi' in ORCA and import the 'AdminExecuteSequence.idt' file from your work directory.
Save it and exit.
in C:\workdir\ type:
msiexec /a vviewer.msi TARGETDIR=C:\workdir\admin
This write an admin installation point.
Extract the patch: visioviewer2007sp1-kb937160-fullfile-en-us.exe /extract:C:\workdir\admin
now cd to C:\workdir\admin, make a copy of "vviewer.msi" and then type:
msiexec /a vviewer.msi /p VViewersp1-en-us.msp TARGETDIR=C:\workdir\admin
This applies the SP1 to the install point.
If you need to distribute the package, you can do the following:
We generate a new CAB-file for the SP1-version. You need WiMakCab.vbs from the SDK to do this.
Make sure it lies in the path or copy it to C:\workdir\admin.
cd to C:\workdir\admin and type:
cscript WiMakCab.vbs vviewer.msi vviewer /L /C
After this you have the SP1-version of vviewer.msi and vviewer.CAB in your C:\workdir\admin.
If you need a single file distribution, do it like this:
cscript WiMakCab.vbs vviewer.msi vviewer /L /C /U /E

Regards, Nick
Answered 08/07/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Could you please give the steps in details?
Answered 08/28/2008 by: nrkres
Senior Yellow Belt

Please log in to comment
0
Hi Vamsi,
what do you consider my previous post to be?
I thought it was a step by step guide...
What is missing?
Regards, Nick
Answered 08/28/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Here is how I did it all in one execution step without editing the MSI:

1 - Run visioviewer.exe /extract:c:\visioviewer to extract the MSI
2 - Run visioviewer2007sp1-kb937160-fullfile-en-us.exe /extract:c:\visioviewer to extract the MSP
3 - From the c:\visioviewer folder execute the command line below to install the viewer and the patch at the same time:
msiexec -i vviewer.msi PATCH="%CD%\VViewersp1-en-us.msp" /qb!

Note in step three the %CD% which represents the current directory. This appears to be necessary for some reason, although you could hard code the path by substituting c:\visioviewer\ instead. I tried not specifying the path to the MSP and it generates the error "This patch package could not be opened." Using PATCH=.\VViewersp1-en-us.msp also does not work, even though the period is supposed to represent the current directory. Go figure. [8|]

Also, I beleive the PATCH parameter requires at least Windows Installer 3.
Answered 01/14/2009 by: MicrosoftBob
Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share