John_Sheridan
July 22nd, 2003, 02:50 AM
Hallo!
With the new DOT NET Framework I create a setup project (MSI packet) which contains deployment project (MSM packetes).<br />
<b>The problem:</b>
The compiling of the MSI packet and installation worked fine but after starting my application the first time the windows installer performs an installation which do not look very professional or makes problems on a server installtion.
In the old Visual Installer 1.1 the installation of such MSI packetes worked correctly.<br />
<b>The bad work around</b>
If made following settings in the new DOT NET installer, the msi packet performed no installation, but this work arounds are not very fine:
<ul>
<li>Setting the default location of the application folder to the msi folder
<li>Copy the msi packet to following local folder: C\Programms\CompanyName\ProductName<br />
</ul>
<b>But this work around has following disadvantages:</b>
It seems, that the installer could not found the msm packetes inside the msi file.<ul>
<li>Case setting applicaton folder: the user who installes the packet can never set another folder.
<li>Case copy msi folder: This could never the meaning of a msi packet!!!
</ul>
<br />
<b>The question:</b>
Do you know, how to install a msi packet from any place with out perforimg an installation after launching the application the first time?
I have experience with the old installer but in the new one it seems that I have overlook some settings or something else althoug I think it must be enough to set the output file of the msi packet in the project properties.
Thanks in advance for your help
With the new DOT NET Framework I create a setup project (MSI packet) which contains deployment project (MSM packetes).<br />
<b>The problem:</b>
The compiling of the MSI packet and installation worked fine but after starting my application the first time the windows installer performs an installation which do not look very professional or makes problems on a server installtion.
In the old Visual Installer 1.1 the installation of such MSI packetes worked correctly.<br />
<b>The bad work around</b>
If made following settings in the new DOT NET installer, the msi packet performed no installation, but this work arounds are not very fine:
<ul>
<li>Setting the default location of the application folder to the msi folder
<li>Copy the msi packet to following local folder: C\Programms\CompanyName\ProductName<br />
</ul>
<b>But this work around has following disadvantages:</b>
It seems, that the installer could not found the msm packetes inside the msi file.<ul>
<li>Case setting applicaton folder: the user who installes the packet can never set another folder.
<li>Case copy msi folder: This could never the meaning of a msi packet!!!
</ul>
<br />
<b>The question:</b>
Do you know, how to install a msi packet from any place with out perforimg an installation after launching the application the first time?
I have experience with the old installer but in the new one it seems that I have overlook some settings or something else althoug I think it must be enough to set the output file of the msi packet in the project properties.
Thanks in advance for your help