I decided to install new version of TMS BIZ library. I launched Subscription manager and started
with Business Core Library because this need to be reinstalled first.
When chosing destination folder, I selected the folder where I have this library installed for many
years and which is accessed from build scripts used in several accounts on my PC.
Subscription manager complained a bit, but then allowed me to install BCL in that folder.
Next I wanted to proceed with the rest of the BIZ libraries, but Subscription manager complained
that Business Core Library is not installed. HUH! I did not found the way to persuade the Manager that BCL is already there.
So I checked web and found that there is new tool for installing libraries - smart setup.
I ran it, and though it complained I have a conflict with version TMS Scripter, I managed to
install BIZ products (after unchecking TMS Scripter in the instalation list)
Now I am left with this layout:
I have older versions of BIZ library in previous location, and new version of BIZ library
burried somewhere in a folder that is local to the account I ran the installation from.
In the browsing paths, I have entries both to the previous old version and to the
new version. At the same time, I am unable to access source folders from Windows
accounts other than the one I performed the install from.
Is there any way to have the libraries installed FOR ALL Windows accounts?
Hi,
Mixing old and new setups isn't a good idea, they are just not designed to work together. It might work, but you are likely to run into issues.
The smartsetup version can be used everywhere, it doesn't need to go deep into your user account, even if that is the default.
My advise would be:
Go to "Installed Apps" into the start menu, and uninstall any "old setup" you have installed there. Of course, if the versions you need too old, you will need to keep them, but you can't install new and old versions at the same time in Delphi anyway.
Also uninstall everything you installed with smartsetup, and uninstall smartsetup itself if you installed it with the setup.
Create a new folder where you want to install the components. Say you want to install at c:\tms. Then create that folder, and unzip the zip file you got at step 3 there.
Launch tmsgui and install the products you want.
Some notes:
which is accessed from build scripts used in several accounts on my PC
If you are using build scripts, you might want to explore using tms.exe directly, instead of tmsgui.exe. tmsgui is just a wrapper that calls tms.exe, but you can automate a lot of stuff by calling tms.exe directly. There is information here on how to use tms.exe to automate your builds
While you won't be able to go too far back, smartsetup already allows to install older versions of the components, but you need to build it from source (we haven't released the new version that allows this, but it will be very soon and it is stable today). Just in case, the versions available are:
If those versions are old enough, I would suggest to just uninstall everything installed with the old installer, and install any of those versions with smartsetup. If you need an older version, you will need to install indeed with the older installed, but do not mix them: If you install some version of BCL, you should install compatible versions of the components that depend on BCL.
Put tms.exe wherever you want, then click in the gear and select that folder.
The main issue here is if you installed smartsetup with the setup.exe, it installs at %localappdata%. What you need to do is to download the portable version, and put tms.exe wherever you want
hmm, I see. Given that the folder with tms.exe is D:\TMS,
the libraries are installed into the common root “D:\TMS\Products”
with subfolders (separate for each library) are named the way
I have no control of. For example
My old name: TMS BIZ Core Library (BTW, this name was suggested by old installer)
New name now: tms.biz.bcl so it yields D:\TMS\Products\tms.biz.bcl
Not 100% satisfactory (requires lot of scripts rewrites), but at least it can reside
in PC publicly accessible folder. Thanks