Blog


Previous  |  Next  |  Index

Bug in Delphi 10.3 Rio / C++Builder 10.3 ISO affects TMS installers

Bookmarks: 

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
This variable is critical to set the path where to find the .NET MSBUILD tool. This setting that is in RSVARS.BAT is not correct as this directory is not used for the Microsoft .NET framework v4.5. For some reason, Microsoft decided to deploy the Microsoft .NET framework v4.5 in the folder C:\Windows\Microsoft.NET\Framework\v4.0.30319. So, the correct setting in RSVARS.BAT should be:
@SET FrameworkDir=C:\Windows\Microsoft.NET\Framework\v4.0.30319
We 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)\EmbarcaderoStudio\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


Bookmarks: 

This blog post has received 14 comments.


1. Friday, November 23, 2018 at 9:37:20 AM

This is a real pain again. Not the first time for Embarcadero.
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


2. Friday, November 23, 2018 at 9:39:49 AM

The installer is under
c:\users\USERNAME\AppData\local\tmssoftware\PRODUCTNAME\setup.exe

You could try to relaunch the installer from there.

Bruno Fierens


3. Friday, November 23, 2018 at 9:56:58 AM

Thanks, but I downloaded the software from the website and tried again. After installing again, there is still nothing in the subdirectories under TMS Component Pack\Delphi103Rio and there are no packages at all in c:\Users\Public\Documents\Embarcadero\Studio\20.0\Bpl. I doublechecked and I did change the rsvars.bat file correctly in the directory Studio\20.0\bin.

Ronald Janse


4. Friday, November 23, 2018 at 9:57:39 AM

I suggest to contact our support via email and include the installer generated log file. These blog post comments is not an ideal medium for support services.

Bruno Fierens


5. Friday, November 23, 2018 at 4:56:11 PM

I had the same issue with Rio installation and these steps seems to have resolved the issue.

Ragain Tim


6. Saturday, November 24, 2018 at 7:20:03 AM

I have to move the batch file from the Bin folder to the Desktop to edit it then move it back again. Access denied was the reason that I could not edit it while it was in the Bin folder.

Jackson Thomas


7. Saturday, November 24, 2018 at 1:45:48 PM

You could also start your editor with admin rights and then open it inside.

--
Roman Kassebaum


Roman Kassebaum


8. Saturday, December 15, 2018 at 9:04:57 PM

Sorry for this stupid question: But why the TMS installer uses the MSBuild instead of the previous internal build system?
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


9. Saturday, December 15, 2018 at 9:08:10 PM

Ever since Embarcadero introduced MSBUILD it recommended to use it for compiling projects outside the IDE. Delphi already comes for years with MSBUILD support. This is nothing new. It is a bug that slipped in the Rio ISO install as Embarcadero switched from depending on .NET 3.5 to now .NET 4.5.

Bruno Fierens


10. Saturday, December 15, 2018 at 10:14:35 PM

Thanks. Replacing
''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


11. Saturday, December 15, 2018 at 10:44:10 PM

However, there must be a similar bug in Delphi 10.1 Berlin, as these directories still remain EMPTY (!) when installing TMS component Pack in Delphi 10.1 Berlin:

...\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


12. Saturday, December 15, 2018 at 11:33:51 PM

HELP!!!
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


13. Saturday, December 15, 2018 at 11:55:36 PM

Just a note: The "native" native and "internal" build tool of Delhi 10.1. is MSBuild. Just open any delphi project with notepad (the .dproj file) and look at the first line of the project. It says:
<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


14. Sunday, December 16, 2018 at 8:48:55 AM

Adrian, thank you for the clarification. I will follow your kind advice.

Aschbacher Peter




Add a new comment:
Author:
Email:
  You will receive a confirmation mail with a link to validate your comment, so please use a valid email address.
Comment:
 
Change Image
Fill in the characters from the image above:
 

All fields are required.
 




Previous  |  Next  |  Index