Hi Valeri, I think my message must have been a bit unclear. > I am sure I already own what Ms supplies with DevStudio, > Very this gives me the strong reason to write what I wrote > above. > > From what you said one may conclude you yourself never try what > is included with MS Developer Studioto to create ROOT distribution. Indeed, I never claimed to have tried to create a Root distribution. Naturally I would not distribute someone else's software product as my own! I was only saying that I thought some version of InstallShield comes with Visual Studio. It may be my memory is faulty, and it was a previous version of VStudio(97) and not 6.0. Since I have VStudio Installer, I would not have installed InstallShield in addition to it. But I know I once had InstallShield, and it came with Visual Studio. > I did not get "what you do think". Do ROOT distribution lacks of > options to "deinstall ROOT" ? What is better from your experience > "MS Installer" or "Install Shield". MS Installer is more integrated with Windows, and it is easier to create a basic installation package which modifies the Registry and gives options for custom installation of the full package. It works like the installer for Office2K or Windows2K, which I'm sure you have seen. I haven't used InstallShield in a long time, but I didn't find it particularly convenient to use as a developer. Uninstall is not so critical for Root, but I think MS Installer makes it easier and more automated (from the standpoint of the developer). > If "Install Shield" is included into the Developer Studio what are > the reasons to download the "Installer" All else being equal, I generally prefer to use Microsoft products in preference to 3rd party tools, especially when dealing with system-related tasks like installation, and especially when the Microsoft products are free. It is easier to use than InstallShield, in my opinion. As you know the present version of Visual Studio is several years old, so I believe the Visual Studio Installer package was created after Visual Studio 6.0 was originally released. The first commerical product to use the Windows Installer (which VStudio Installer is based on) was Office 2000, I believe, which came out after the present version of Visual Studio. > > I recently figured out how to append to the PATH environment > > variable using VStudio Installer, > > To append PATH environment variable one needs NO special tool. > Just the well-known MS DOS "PATH" command makes this job. > Of course one can use "My Computer" property GUI interface > "Registry editor" as well. [...] Yes, of course I know how to *interactively* modify the path. But I was talking about how to modify the path during installation, such that it is restored to its previous state when the package is uninstalled. This was the improvement which someone requested, I thought. > But in general the end-user should not bother about this variable. > It must be set by the distribution package by automatic. Exactly! > The original question was about some problem with ROOT installation > on Windows platforms. One said it should be improved. I don't think it was a "problem", just that someone wished the environment variables and path were set as part of the package (i.e. a desired new feature rather than a problem). > I am sorry, very likely I missed the improved version you have > provided. > Please let me know where can I pick your version of ROOT distribution > for Windows. I have not provided anything except advice which was intended to be helpful and suggest to you that it is probably not necessary to obtain a commercial license for InstallShield (or any other product) in order to make an installation kit for Root which automatically sets path and environment variables. If you would like me to try to create a Root distribution (with path and environment set automatically), I can try to do it, although that wasn't the point of my message. Dave dcasper@uci.edu
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:34 MET