.net Repackaging
Hi Guys
[font="microsoft sans serif"]i am doing .net frame work 2.0 packaging ,during dry run i found out One msi named netfx.msi and an exe install.exe,so when i try to install msi it gives an error that it requires install.exe to be present .i created mst using wise and added the property ISSETUPDRIVEN =1,but still it shows same error ...do i have to repackage entire .net exe r any other solution please do reply ,
[font="microsoft sans serif"]
[font="microsoft sans serif"]i am doing .net frame work 2.0 packaging ,during dry run i found out One msi named netfx.msi and an exe install.exe,so when i try to install msi it gives an error that it requires install.exe to be present .i created mst using wise and added the property ISSETUPDRIVEN =1,but still it shows same error ...do i have to repackage entire .net exe r any other solution please do reply ,
[font="microsoft sans serif"]
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
neo2000
16 years ago
I do think you're mixing a few things up.. That is, you're confusing Installshield msi's with the dotnet framework.. My suggestion; read up on both, using the search on this site..
Posted by:
cygan
16 years ago
this should be very straight forward. have a look at your launch conditions with any refs to setup.exe and also you can check your customs actions remembering to delete from the installexecutesequence table if that is necessary
Posted by:
anonymous_9363
16 years ago
It is *generally* considered to be A Bad Thing to re-package any app which is supplied in MSI form.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
