Hi

I am trying to package up .net framework 2.0

I did an admin install and extracted the netfx.msi file along with several txt files and dlls. Using ORCA I created an mst file and created a property called ADDEPLOY and set this to 1. This takes care of the installer wanting installer.exe to install the app.

This works fine but all of the files I extracted from the original .exe are required by the install but these are not in a cab file and are just sitting in the source folder. I was able to put the extracted files into my own .cab file but am not sure how I go about telling the app where to find them. Should I just leave them where they are or is there a nice simple way of getting the msi to use my cab file ?

Thanks
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
There should be an entry in the Media table telling the MSI what the CAB file name is.
Answered 09/20/2007 by: VBScab
Red Belt

Please log in to comment
0
Thanks

I did add the entry into the media table but it told me it couldn't find the source files. I have decided just to leave them uncompressed in the source location for now and might do a bit more research into cab files.
Answered 09/20/2007 by: gtalboys
Purple Belt

Please log in to comment
0
In addition to what VBscab says, you should look at the package database. This subject has been covered. BTW, admin install and packaging this with the MSI/mst is not supported by msft. At my current client they ended up just deploying it the microsoft way instead of trying to shoehorn it into an msi/mst. IMHO, why do it if msft doesn't recommend it? That's like trying to repackage office....
Answered 09/20/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
I'm pretty new at this, but why repackage when dotnetfx.exe comes with cmd lines?
I use the following command to install dotnet 2.0:
dotnetfx.exe /q:a /C:"install.exe /q"

Best regards
KentK
Answered 09/20/2007 by: KentK
Yellow Belt

Please log in to comment
0
Hi Graeme,
use the SDK tools to do this.
Make a copy of 'netfx.msi', lets say '1.msi'
Load 'netfx.msi' into ORCA. Go to the file table and sort it after the 'Sequence' table.
Delete all rows from 1 to 10055.
The remaining lines should be the files to compress (excluding 'netfx.msi').
Now we need to get rid of the "NonCompressed" attribute '8192'.
You can do this by hand or export the table as an IDT file and "Search and replace" it in Notepad.
Change the '9216' attributes to '1024'.
Now you can create and embed the cabfile with this command:
cscript wimakcab.vbs netfx.msi instres /L /C /U /E
Now open the '1.msi' in ORCA. Go to the file table and sort it after the 'Sequence' table.
Select all rows from 1 to 10055. Press Ctrl-Shift-C
Go to the open 'netfx.msi' and paste this into the File table with Ctrl-Shift-V.
Go to the media table and copy the 'Cabinet' entry from line 1 to line 13.
Delete line 1 and copy it over from '1.msi'.
And last but not least, you could add the 'ADDEPLOY' property.
That should do the trick.
Regards, Nick
Answered 09/20/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
I decided to go with the switches that MS recommend for this one and it works fine. The info about including an external cab will come in handy on future apps though.

Thanks all.
Answered 09/24/2007 by: gtalboys
Purple Belt

Please log in to comment
0
Hi folks,
you could also try to delete this entries from the file table.
Because this files are helpers for the the exe bootstrapper.
Delete all rows with sequence 10055 and higher.
Regards, Nick
Answered 09/24/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
deleted because it works:

I was missing the :a
Answered 10/18/2007 by: rhyous
Senior Yellow Belt

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