wise package folder locate
Created: 23 Apr 2009 | Updated: 22 May 2010 | 4 comments
HI,ALL
i have a question about wise package folder locate,i have 100+ msi package in file server,i want to know,what 's the best practices for msi folder,
all msi packages locate same folder,such as
softwarepackage
1.msi
2.msi
3.msi
4.msi
5.msi
or each msi at on folder ,such adboe photoshop
adboe photoshop
setup.msi
test app
setup.msi
Discussion Filed Under:
Comments 4 Comments • Jump to latest comment
You don't give much information about your environment, but as a general rule, I would strongly recommend that you use a separate folder for each MSI, and use a standardised naming convention for the folders (and for the MSI files) that gives you an immediate indication of what version of the application you are dealing with.
Your example of adobe photoshop, would recommend a folder name of Adobe_Photoshop_CS3 (or whatever version it is) and the same for the MSI name.
Otherwise, if you just use numbered MSI files, you will find it impossible to check quickly, which one is which application. At the same time, if you have two MSI's with an external CAB file, called data1.cab (this is quite a common name for an external CAB), how will you manage the conflict if the MSI files are all in the same folder?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
I usually use a folder structure like:
Vendor
ProductName
ProductVersion_LanguageCulture_InternalRevisionNumber
ex.
Microsoft
Office Professional Plus 2007
12.0.4518.1014_enUS_01
thanks ,guys
en,i think use First Char is a good method.
ex.
0-9
7ZIP
A
Adobe reader 9
adobe photoshop cs4
B
big A
big B
C
creator9
citrix
I strongly agree with one of Kim's points of the internal revision number.
This is often ommitted and only become important when you need to release another instance of the same product and version.
For example you deploy Office 2003 and forget to add important keys / settings etc. You then rerelease that same version of Office 2003. I have seen in the past people just put the new release into the same folders which can be problematic.
the internal revision number allows for a much more forgiving folder structure. However if you always plan to get it perfect on the first attempt you will have no problems. In practice that is not always the case.
Would you like to reply?
Login or Register to post your comment.