I can't figure it out: do the files which are referenced in the Binary element of .wxs file get copied to the target machine, or are they resources of the install package?
They are definitely the resources of the install package. This means that they don't get installed to your application folder, but Windows Installer is supposed to extract it internally to some temporary location to address the functionality in it. And it is supposed to clean after itself. But this is definitely not visible to the end users of your installation.
At least, this is how I understand it.
Related
I have the 4.0.3 Octave version on my machine.
and I would like to upgrade my version using windows.
Can someone tell me please the steps to follow?
Thanks.
If you want to remove v4.0.3, the complete answer will depend on how you installed that version in the first place.
If you used an executable installer, then there should be an 'uninstall' option available. On Windows 10, you can sometimes right click on the shortcut in the startmenu and an Uninstall option will appear. Otherwise you can follow the directions at this link to navigate through the Settings to the Apps & Features window, which lists everything installed and will provide an Uninstall option.
If you used a zip package to 'install' Octave 4.0.3 just by unzipping it to a folder on your hard drive, then no uninstall process is necessary. you can just delete the folder and shortcuts manually.
You can have multiple octave versions installed next to each other, the folders will have version numbers to prevent them from overwriting themselves.
To install the latest version (5.1.0 as of this answer, although 5.2.0 will be released very soon):
You can find the installation files for Windows by going to the Octave download page and clicking 'Windows'. There will be several file options there. Most people choose the first one (octave-5.1.0-w64-installer.exe) for 64bit systems. You can just download that or one of the other .exe versions, execute that program, and follow the prompts. If for some reason you would rather download a zip package and do a manual setup, I suggest you follow the instructions at the Octave for Microsoft Windows Wiki page to make sure everything is configured correctly.
I have installed gulp-imagemin on my Windows 7 laptop using
npm install --save-dev gulp-imagemin
and after a lengthy process ended up with a folder with well over 10,000 files and some very deep folder structures. Has anyone else seen this? Is it likely to be correct or would I be right in suspecting an issue?
Yes it is correct. I've installed it too on my Windows machine and I saw the same thing as you describe here.
The reason it has over 10,000 files and an even more lengthier directory structure is the nature of node modules.
Each and every node module is self containing and has a sub directory node_modules with all it's dependencies. Those dependencies have dependencies as well, resulting in a very deep directory structure.
When I try to remove gulp-imagemin, Windows is even complaining that the directory structure is too large and that it cannot remove certain files. This is because of the MAX_PATH length of 260 characters; see msdn.microsoft.com.
Nevertheless I really, really like this node module and I'm using it in every front end project I work on. Sometimes it takes 2 tries to install it, but I think it's definitely worth it.
On GitHub I have a starter application for working with single page applications; skeletonSPA in which I use it too.
I have made a VS2010 project which installs MySQL by calling MySQLInstallerConsole.exe with necessary arguments. This works perfectly however, when I try to run this project's exe as a custom action it executes the exe but MySQL is not installed.
I checked the log file for MySQL exe and it had the following error:
Error 50: Package Name State change request failed.
What does this really mean, any solutions?
There are at least a couple of things that have something to do with this:
I believe the MySQL installer is an MSI file according to this:
http://dev.mysql.com/downloads/installer
You cannot install an MSI from a custom action of a Visual Studio setup because recursive calls to MSI installs are not allowed.
In a Everyone install custom actions run with the SYSTEM account, and installs are not often expecting this if they want to install files in user-profile folders because the SYSTEM account doesn't have any.
You need to bootstrap this somehow, and I think people are often using the WiX Burn bootstrapper for that. You define the ProductCode, name etc of the product and define how to install it.
I tried building recutils version 1.7 downloaded from the home page, using the standard configure, make, sudo make install sequence, but when trying to run the resulting binaries. like recinf, I get the error:
recinf: error while loading shared libraries: librec.so.1: cannot open shared object file: No such file or directory
Does this mean I made a mistake during the build or is the package itself in error?
As Etan Reisner said the problem was that the shared object libraries were installed but not loaded into the cache, hence the need to run ldconfig. After running
sudo ldconfig
the binaries ran properly. If I had looked in /usr/local/lib, I would have seen the libs there.
I'm refactoring some msbuild scripts for a project, that uses ClickOnce to package the application. The project packages both an install and an update version and puts then in seperate folders on the webserver. Any reason for this? The only difference when publishing the ClickOnce package, the the publish url (e.g. somesite.com/update and somesite.com/install).
I'm not an ClickOnce expert, but would it not be enough with just a single folder og both installing the client and updating it?
Thanks in advance.
NB. The update url always points towards the update folder.
Yes, it is enough to have single folder for installing and updating application. ClickOnce will do everything automatically. The only thing is that when publishing the application, you have to specify what will be the update url (and it can be exactly the same as install url)...so basically, you can give your clients that "update" url as a location from where they can install the application.