I need to set dynamically InstallUrl of .NET 3.5 setup file.
For example, when I set a hardcore path like: file:///C:/temp/dotNetFx35Setup.exe it works, but my setup file is inside source folder where is the msi installation file.
I know that I can set property of prerequisite from same location and from vendor's site, but don't ask, this is my task.
Thanks in advance.
If I understood your question correctly, you should use your MSI instead of Setup.exe because setup.exe will check for prerequisites before installing where MSI just installs with the assumption that you got all prerequisites.
Related
I have created installer using install-shield 2013. Installer deploys the file and there is one executable file. I did some changes in executable file and created installer again.
When I upgraded using installer then I found my executable is not replaced with new one.
In Install-shield, I went to "Releases", go to the "Setup.exe" section and there's a field called "MSI Command Line Arguments" and provided REINSTALLMODE=emus REINSTALL=ALL but it did not work.
Please suggest for same.
Regards,
Rashi
I'm using a Visual Studio Installer Project (.vdproj) to create an installer. When built, it outputs an .msi file and a setup.exe file. When I run the setup.exe, it downloads the .msi from the location specified in the "Installation URL" field in project build properties, and runs it. However, if the PC is offline, the download fails and the install is aborted, although the .msi file is present in the same directory as the .exe file. Is it possible to configure the setup.exe to use the local .msi file if present?
In the Visual Studio Prerequisites you should be able to use the "Download Prerequisites from the same location as my application". This generates a directory (a CD image if you like) that will be used to install the prerequisites. It won't install anything from there unless you build the prerequisites that way. Also, you can't just add a framework with the right name because there's a hash check to ensure that the actual prerequisite redistributable is the correct one.
I have an installshield msi project that produces CD-ROM files.
I know how to set a custom action in order to launch an exe file stored in binary table.
What i want to do is to launch an exe file that is at the source media root directory and it is not copied at the installation directory.
I do not want to add it at the binary table because i want to be able to change the file without building again the installer.
any ideas?
Thanks
For first time installation, you can reference a property that indicates the location of the installation files. Common ones to consider include:
SETUPEXEDIR
SOURCEDIR
OriginalDatabase - watch out for the .msi filename being included here.
For InstallScript installations (instead of Windows Installer based ones), there is also PACKAGE_LOCATION.
I have an application (C#, .Net4) which I'm publishing with ClickOnce. I need to verify that the machines installing it have 2 prerequisites, one is an msi file and the other is exe. I've tried the following solutions:
Use the prerequisites option in the project's properties (under Publish) while putting the msi and the exe in the installation directory - no good.
Install Bootstrapper Manifest Generator and following this tutorial, where I have a problem - the build succeeds but with Attempted to access a path that is not on the disk. warnings. It does generate the package.xml and `product.xml files, but the installation size didn't change and it does not install the prerequisites (I've also removed the app and tried to install rather than update).
I'm using VS2010, I'm not sure i this is the reason that BMG does not work.
I'd appreciate your help in solving this issue.
Thanks.
there is no Bootstrapper Manifest Generator for vs 2010 but,
you can use Bootstrapper Manifest Generator for vs 2008 follow this link
http://archive.msdn.microsoft.com/Release/ProjectReleases.aspx?ProjectName=bmg&ReleaseId=1567
after Boot strapper Generate your installation Package you need to copy Package
from Document(your Package)
manual to this location "Program Files\Microsoft SDKs\Windows\v7.0A\Bootstrapper"
for more information
http://msdn.microsoft.com/en-us/library/ms165429%28v=vs.80%29.aspx
if i want to install a MSI, created by Visual Studio 2005, via Active Directory Group Policy:
What requirements must be met by the Setup Project?
How can I specify the installation path? Is this a part of the Group Policy setting? Or do I have to create a special "silent install" version of the MSI?
Thanks!
I found out that it is possible to specify the installation path with a custom property called "TARGETDIR". The unattended installation can be tested with:
setup.msi /passive TARGETDIR="C:\whatever"
There is a command MSIExec that installs MSI installers automatically. This command is what you would use with the Policy. Any MSI should be compatible with it.
You have a number of options for building installers going with Microsofts default setup projects or something more verbose like Wix.