I'm doing a software that requires from OpenVPN to work, so I'm expecting that when I launch the installer checks if OpenVPN is installed and if not launch it's installer. If the install is successful then continue with the install, if not, exits.
Also, I'd like to check if O.S is 32 or 64bits in order to launch the correct installer from openvpn.
How would be the best way to do that? I've readed about custom actions, nested installations, chainers, etc... but I'm newbie in this and I don't know where to start.
I'm working with Visual Studio 2012 with Installshild plugin.
Create "BootStrap" application (.exe) and add as prerequisite, what is running before you install starts. You also can check box ( not show in prerequisite list) and you Bootstrap app will be not in PreReq,. dialog
Related
I know this isnt a dev question per se, but is there a timeline on a 5.2 build that can be installed on Win 10?
I think the issue i am seeing is just with the installer so an in place upgrade to Win 10 might work fine, but a clean install fails as it doesnt acknowledge IIS 10 or whatever version comes with Win 10.
Thanks!
Official answer - Windows 10 is not yet supported by the currently available Acumatica ERP installers, however the issue has already been fixed internally (AC-56069 - fixed in 4.20.2262, 5.10.0785, 5.20.1012 and newer). Following workaround can be used in the meantime:
Download the Orca tool to edit the MSI file: http://adriank.org/wp-content/uploads/2015/01/Orca.zip
Open the
MSI file using this tool (might be able to right click on MSI and
open with Orca)
Go to the LaunchCondition table
Drop/delete the IIS version condition (inside MSI, the LaunchCondition entry is IISVERSION >="#7"; system does a string comparison and "10" is
smaller than "7")
Save and close Orca
Run the setup
I can't give you an "official" answer but I can give you a work around.
If you download a utility called LessMSI you can extract the installation files. They will come out in a folder called "SourceDir". Simply take these and replace the files in your default installation folder or run them from another location.
Then you can proceed as normal.
The installer only checks if pre-reqs are installed and then copy's the files to the output location. If you have IIS already setup with dotnet support then the rest will be fine.
I do this frequently if I have to install a site with a specific version in order to upgrade or test a client's snapshot.
I have 4.1,4.2,5.1,5.2 running on my Windows 10 workstation as I type
I created a Windows form setup using install shield.
Is it possible to stop other services (ex: .exe's) in my system while uninstalling setup created using install shield.
Is this possible while creating setup using Install shield or I want any scripts in my app to stop certain services while uninstalling my setup.
Service installation settings are found in the "Advanced Settings" view of each individual component if you have the right version of Installshield - I am not sure what features "light versions" have.
If you don't have an appropriate version of Installshield you can always use a VBScript or similar to stop any service you want.
I am trying to install Remote Tools on a Surface RT running Windows 8.1 preview. I downloaded update 2 of remote tools from Microsoft's site and when I try to run it I get the error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
This is confusing because I downloaded the file directly from MS website and when I look at the .exe properties it says digital signatures by Microsoft Corporation.
Any insight would be greatly appreciated.
Thanks!
Update: It seems like my Microsoft Root Authority certificate is "not valid for the selected purposes" I've tried exporting a "good" certificate from another machine and importing it into the Surface machine but it still gives the same issue.
This is because your downloading the 2012 tools. You can download the 2013 preview tools here at the following link! (Be sure to choose ARM)
http://www.microsoft.com/en-us/download/details.aspx?id=40781
Would have been nice if Microsoft had given us a heads up.
Also, when I go to the 2013 download on my Surface RT running 8.1 preview, and I click on Download, no matter which option I pick (x86, x64, or ARM) it downloads the x86 version, which obviously won't work. I had to download it on a PC and copy it over using a USB drive.
This problem exists on the released version of 8.1 too.
If you previously had the vs2012 tools installed, they appear to be uninstalled during the upgrade.
Attempting to reinstall gives the above error.
That means, it's now impossible to connect to the 8.1 Surface RT from VS2012 Pro to debug an 8.0 app running on 8.1. Instead, you need to connect with the VS2013 tools and remote debugger.
For anyone who is just trying to test their App updates a surface device running Windows 8.1 RTM, I have at least found a workaround.
You can manually deploy your package to your device by coping the package content to a USB memory stick and running a already defined powershell deployment script.
Basically you need to run the normal package creation process you would do to deploy to the app store to create a package, then copy the contents of the package folder (Not the compress package itself) to your USB stick. There should be a file named Add-AppDevPackage.ps1 in this folder.
Open your USB device from your Surface RT system, right click the Add-AppDevPackage.ps1 file and select "Run with powershell". You will receive several confirmation prompts at the command line and a popup window prompting you to run with admin privileges.
This is by no means a convenient or speedy process but it worked for my purposes.
This link has more detailed information on manually deploying your app package.
I'm using a C# setup project which includes some pre-requisite software. These pre-req's appear to only get installed by the EXE and not the MSI (both EXE and MSI are created when I build my setup project.)
I can't always trust that my users will bother running the EXE as opposed to the MSI, so is there a way to force it? Perhaps some options:
My app needs Sql CE 3.5 SP2 - Is there a way that I can have the MSI install this instead of it only being installed in the EXE?
Is there a way to make my MSI detect when it's launched by the user instead of launched by the EXE?
Can I have my MSI launch the EXE installer as part of it's install process?
This is not supported by Visual Studio setup project. However, commercial setup authoring tools offer multiple solutions:
handle prerequisites from the MSI installation UI instead of using an EXE
embed the MSI into the EXE so you have only one setup file
configure the EXE to set a custom MSI property and create a launch condition based on that property; this way the MSI will stop if the property was not set by the EXE
If you want to continue using Visual Studio, a solution would be to create a launch condition for Sql CE 3.5 SP2. This way the installation will stop if Sql CE 3.5 SP2 is not installed.
Using Windows 7 Ultimate on 64bits. Why isn't it showing? I can find tortoise svn in the start menu and when I launch it it says the application is a shell extension but it doesn't show.
I just installed this at work this morning and now I want to install it at home. Any help? Why won't it show? I have already rebooted my machine.
Did you install the 64-bit version?
You need 64 bit TortoiseSVN on 64 bit Windows because otherwise, its Explorer won't "see" Tortoise.
The best thing is actually to install both to make sure Tortoise works in the folder views of 32-Bit applications like IDE's, too.
Note that x64 users can install both the 32 and 64-bit versions side by side. This will enable the TortoiseSVN features also for 32-bit applications.
If you get the TortoiseSVN specific commands when right-clicking a file or folder in Explorer, it works.
Did you reboot? You need to restart explorer.exe
TortoiseSVN is a shell extension and not a regular desktop application like WinCVS. All commands are available from the Context menu. I suggest be first familiar with svn commands and how they work and then try to use the same commands through TortoiseSVN.