Blog
All Blog Posts | Next Post | Previous PostBug in Delphi 10.3 Rio / C++Builder 10.3 ISO affects TMS installers
Friday, November 23, 2018
We had detected that on some machines here there was an erratic setting in the RSVARS.BAT file in the \bin subfolder for the installed Delphi 10.3 Rio / C++Builder 10.3. It concerns the setting for .NET FrameworkDir:@SET FrameworkDir=C:\Windows\Microsoft.NET\Framework\v4.5
@SET FrameworkDir=C:\Windows\Microsoft.NET\Framework\v4.0.30319We had similar problem reports from several customers and we have been in touch with Embarcadero. We got confirmation from Marco Cantu that this issue is only for the ISO based installs of Delphi 10.3 Rio, C++Builder 10.3 Rio and RAD Studio 10.3 Rio.
So, until a solution comes from Embarcadero, we recommend to edit: C:\Program Files (x86)\Embarcadero\Studio\20.0\bin\RSVARS.BAT and replace the erratic FrameworkDir setting by the correct one.
After patching this, our installers will be able to invoke the MSBUILD tool to build our component package files.
The developers having installed Delphi 10.3 Rio, C++Builder 10.3 Rio and RAD Studio 10.3 Rio via the web installer are not affected.
Bruno Fierens
This blog post has received 27 comments.
c:\users\USERNAME\AppData\local\tmssoftware\PRODUCTNAME\setup.exe
You could try to relaunch the installer from there.
Bruno Fierens
Ronald Janse
Bruno Fierens
Ragain Tim
Jackson Thomas
--
Roman Kassebaum
Roman Kassebaum
And wouldn''t it be nice if the installer let the user CHOSE whether he wants to install using MSBuild or the native Embarcadero Build tool?
And why building other projects in Rio does work if Rio now generally uses the MS Build tool?
Aschbacher Peter
Bruno Fierens
''C:\Windows\Microsoft.NET\Framework\v4.5''
with
''C:\Windows\Microsoft.NET\Framework\v4.0.30319''
in RIO fixed the bug and installing TMS Component Pack with the Subscription Manager 2.0.1.1 did work and now these directories which were previously empty now are filled with the built install files:
...\TMS\TMS Component Pack\Delphi103Rio\Win32\Release
...\TMS\TMS Component Pack\Delphi103Rio\Win64\Release
So, thanks again.
Aschbacher Peter
...\TMS\TMS Component Pack\Delphi101Berlin\Win32\Release
...\TMS\TMS Component Pack\Delphi101Berlin\Win64\Release
So I hoped that replacing the analog line in:
C:\Program Files (x86)\Embarcadero\Studio\18.0\bin\rsvars.bat
would solve that problem in Delphi 10.1 Berlin too, i.e. replacing:
@SET FrameworkDir=C:\Windows\Microsoft.NET\Framework\v3.5
by:
@SET FrameworkDir=C:\Windows\Microsoft.NET\Framework\v4.0.30319
But that, unfortunately, did not work, so I set the line back to:
@SET FrameworkDir=C:\Windows\Microsoft.NET\Framework\v3.5
So I would be ETERNALLY THANKFUL to anybody who could show me how to solve this similar problem in Delphi 10.1 Berlin!
Aschbacher Peter
So how can I MANUALLY install TMS Component Pack in Delphi 10.1 Berlin, as I have only a setup.exe from TMS and the installer does not work for Delphi 10.1 because the TMS installer does not support the internal Build Tool of Delphi 10.1???
This is strange: All other external automatic install tools from other vendors work without problems in Delphi 10.1. Why the TMS installer is the only one which does not??
Aschbacher Peter
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
Delphi projects are MSBuild files, and are expected to compile with MSBuild, since Delphi introduced the .dproj files in Delphi 2007. (before that, the native build tool wasn''t indeed msbuild).
The reason why tms installers use MSBuild is because it is the only supported way to compile dproj files from the command line. Some installers from other vendors might call directly the dcc32/64/etc compilers, mostly those who have to support Delphi older than 2007 where MSBuild wasn''t supported, but that is wrong, and only works for win32 and win64.
If you need to support other platforms than win32 and win64, (and we do), then the only way is the official way, which is to use MSBuild.
About your issue, the rsvars problem happens only and only in Rio. All previous installers are ok, and you shouldn''t touch the rsvars from Delphi 10.1.
The problem you have with 10.1 is completely unrelated to the RIO problem and MSBuild, and the best way to fix this is to send a support email to info@tmssoftware.com or open an issue in the forums, providing the install log so they can figure out what is wrong. And whatever is wrong, it is not related with the problem described in this post, since that only happens in RIO.
Adrian Gallero
Aschbacher Peter
Craggs David
Bruno Fierens
Fixed the bat file and Presto! All OK for installing all components in Tokyo and Rio.
Salgado Eduardo A
It''s OK for me after the change
BUSSONNAIS Olivier
Another solution which works nicely is to create a directory junction for the folder ''v4.5'' that points to the folder ''v4.0.30319''.
mklink /J C:\Windows\Microsoft.NET\Framework\v4.5 C:\Windows\Microsoft.NET\Framework\v4.0.30319
James LeMmon
Bruno Fierens
Pereira Hamilton E
From: @SET FrameworkDir = C: \ Windows \ Microsoft.NET \ Framework \ v4.5
To: @SET FrameworkDir = C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319
Installed, can I return the file '''' RSVARS.BAT "to what was ??
Is there any problem ??
Pereira Hamilton E
Bruno Fierens
Best regards
Ali Sadik
Bruno Fierens
Ali Sadik
remercement
All Blog Posts | Next Post | Previous Post
After installing the Componentpack I end up with some sort of deadlock. The Subscription Manager thinks I installed the software, but I can''t uninstall it and it''s gone from my disc. So I can''t install it again. And I don''t know where the downloaded exe is.
Ronald Janse