Hi,
Hi,
Hi,
From now on, the version history will be handled in the standard way as all other products, i.e. via: https://www.tmssoftware.com/site/tmsvcluipack.asp?s=history
- The https://www.tmssoftware.com/site/productquery.asp feed to know when a new update is released.
- The https://www.tmssoftware.com/site/versionquery.asp feed to know the content of the update for a specific product and a specific version.
- Other than the Count=N parameters for the productquery, is there other filters that could help us getting information easier about new version of VCL UI PACK?
I tried to use ?id=tmsvcluipack but it doesn't filter the sent XML.
- Other than the ?id=XXXX&version=N.N.N.N for the version query, is there other filters?
I tried to, for exemple, remove the version filtering to obtain all version of a product, but it didn't seems to work.
- What is the maximum number of simultaneous product updates that has occured or "may" occured in a single day?
I imagine the "May" might as well be all 396 currents products in the feed plus any other new, but realistically, will ?count=10 be safe to assume that if the VCL UI PACK is updated, there will no more than 9 other product and thus avoid hiding this product update?
- Is it possible for a product to be updated twice in the same day?
The Product feed only have the date in <channel\item\pubDate> and the <channel\pubdate> updates every minutes regardless of if there's been an update to a product or not.
- Check in productquery.asp?count=10 if there is an item with <id>tmsvcluipack</id> (count=10 to avoid unnecessary bandwidth use);
- If so get the <version> of this item;
- If the version is different of the last time it was checked, use versionquery.asp?id=tmsvcluipack&id=<version> to obtain the version info and send an email about it;
- Download the VclUiPack, extract it, and send it to the server for installation.
It will be very rare that there are over 10 releases a day.
We are not aware of this shortcoming. Can this be reproduced?
Are you referring to running a new version of TMS VCL UI Pack? Do you do this from the same Windows user account as you did the previous time?
I Bruno,
Such keys do exists but are left blank.
Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Software\tmssoftware\TMS VCL UI Pack]"Username"="""Code"="""InstallDir"="C:\tfs\Composants\TMS VCL UI Pack""Version"="10.0.2.0""Date"="06/08/2019"
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\tmssoftware\TMS Component Pack]"Username"="[redacted]@[redacted].ca""Code"="[redacted]"
That is strange. We will investigate.
Really sorry to write you again so soon,
I've some questions/suggestions about the new setup.exe for the VCL UI Pack vs Component Pack.
Also, at the end of the install, there is three checkboxes to uncheck if we just want to start coding right away without being bombarded with Notepad&Explorer windows. (View [...] documentation, View [...] migration and Open [...] Demos). It is a bit tedious.
Thanks again for your time.
We will consider these feature requests for the installer when new work on installer scripts is scheduled.
When you are looking into the installer, can you please confirm that the essential option to install WITHOUT building and installing into selected compiler registries will be retained? I was alarmed to read that is is now described as 'deprecated' in the new UI Pack. Maybe this is a translation issue, but to me this word gives the clear implication that it is one step away from being dropped, which would make difficulties for us. If you say instead 'not recommended' then that is fine (and correct for new users), but we need to be absolutely sure that no subtle changes creep in, so (for all the libraries we use) we always check sources (in a special folder only for installs) against our production source code, and only build the BPL/DCP and registry entries with a Finalbuilder project which we can document and control.
it will be retained
- We got no time yet to review the installer script (we work with 1/2 staff due to summer vacations)2) You cannot assume the version history to be immediately updated after the version nr. is updated. This can take a few minutes.
Thanks for the informations!
As explained, as soon as we can we will review the installer script & update.