MSi made in Visual Studio
Hi
This might not be the best forum for this question but....
I have an application made by some local distibutor in Norway, TiPS FM.
They make this software in MS Visual Studio .NET. The project/program is then saved as MSI.
When I try to make a MST to this MSI I am not alowed, get an error message : Error retrieving Property for table.
Have anyone seen this before?
When I edit the MSI and looks inside Directory Table all folders have names like
"ProgramFilesFolder.3643236F_FC70_11D3_A536_0090278A1BB8"
And all components have names like "C__01CAB465EDDF425E966F2EA369359EA7"
It looks like a mess :-)
I'm no developer and haven't programmed anything part from vbscripts and batch since my education as computer engineer back in -92.
Is this due to Visual Studios way of making the MSI or is it the developer who don't know better?
Could he make some configurations inside Visual Studio to make his MSI's better and easier to handle?
My solution to the problem so far is to do a repackage of the software.
Hope someone have some experience in this.
br,
andler
This might not be the best forum for this question but....
I have an application made by some local distibutor in Norway, TiPS FM.
They make this software in MS Visual Studio .NET. The project/program is then saved as MSI.
When I try to make a MST to this MSI I am not alowed, get an error message : Error retrieving Property for table.
Have anyone seen this before?
When I edit the MSI and looks inside Directory Table all folders have names like
"ProgramFilesFolder.3643236F_FC70_11D3_A536_0090278A1BB8"
And all components have names like "C__01CAB465EDDF425E966F2EA369359EA7"
It looks like a mess :-)
I'm no developer and haven't programmed anything part from vbscripts and batch since my education as computer engineer back in -92.
Is this due to Visual Studios way of making the MSI or is it the developer who don't know better?
Could he make some configurations inside Visual Studio to make his MSI's better and easier to handle?
My solution to the problem so far is to do a repackage of the software.
Hope someone have some experience in this.
br,
andler
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Ledge
18 years ago
Andler,
I've seen this with other vendor msi's. The component name is inherited from the component code.
It doesn't make any difference to the package. It just doesn't look very pleasant!
Vendors are not worried how pretty their packages appear and in most cases these are badly written msi's.
I've seen this with other vendor msi's. The component name is inherited from the component code.
It doesn't make any difference to the package. It just doesn't look very pleasant!
Vendors are not worried how pretty their packages appear and in most cases these are badly written msi's.
Posted by:
brenthunter2005
18 years ago
Yeah, I gree with Ledge.
But I'm more interested in the issue with creating a MST against this MSI.
@andler - have you been able to successfully create your MST yet?
But I'm more interested in the issue with creating a MST against this MSI.
@andler - have you been able to successfully create your MST yet?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
