Microsoft Visual Studio .NET 2005 Professional
Hi,
I'm trying to create a MSI of Micosoft Visual Studio .NET 2005 Professional which I can distribute without using the executable.
I removed 2 CA_Launchconditions which the if the msi is called from the executable and if the prereq. are installed.
The MSI is installing without any error as far I can see, but I want to know if this is the right way to do it.
Does anyone have any experience with this method?
Dennis
I'm trying to create a MSI of Micosoft Visual Studio .NET 2005 Professional which I can distribute without using the executable.
I removed 2 CA_Launchconditions which the if the msi is called from the executable and if the prereq. are installed.
The MSI is installing without any error as far I can see, but I want to know if this is the right way to do it.
Does anyone have any experience with this method?
Dennis
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
shogun_ro
18 years ago
I don't know if I understood what you wanted to say.
So, you have a vendor MSI for Visual Studio 2005 and you removed 2 Custom Actions that prevented the installation of the MSI without using setup.exe?
If this is what you did then I think you did well - this is the usual approach I take and most of the time it works.
There are some cases where the setup.exe does much more than just launch the vendor msi with the correct parameters. In these situations you need to figure out what are the additional things done by the setup.exe and include them in your transform.
If you install the Vendor MSI + your MST and the application seems to work fine and the size of the installation is the same as if you installed Visual Studio using the setup.exe then everything is ok - Your approach is correct.
So, you have a vendor MSI for Visual Studio 2005 and you removed 2 Custom Actions that prevented the installation of the MSI without using setup.exe?
If this is what you did then I think you did well - this is the usual approach I take and most of the time it works.
There are some cases where the setup.exe does much more than just launch the vendor msi with the correct parameters. In these situations you need to figure out what are the additional things done by the setup.exe and include them in your transform.
If you install the Vendor MSI + your MST and the application seems to work fine and the size of the installation is the same as if you installed Visual Studio using the setup.exe then everything is ok - Your approach is correct.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
