FlexCel VCL Build Fails on RAD Studio 13 (BRCC32 / MSB4061 Error)

FLX TMS FlexCel for VCL & FMX
1

Hello TMS Support Team,

We are experiencing a build issue with FlexCel VCL on a RAD Studio 13 environment.

The build fails with the following errors:

  • MSB4061: The "BRCC32" task could not be instantiated

  • MSB4060: The "BRCC32" task has been declared or used incorrectly, or failed during construction

  • System.TypeLoadException: Could not load type 'System.Collections.Hashtable' from assembly 'mscorlib'

The complete build log is attached for your review.

Could you please advise whether this is a known issue and suggest possible solutions?

Thank you.

Best regards

tms.log (32.6 KB)

2

Hi,
We hadn't seen this error before, I am not sure what could be causing it. The weird thing is that debug compilations worked fine, it is only failing when trying to compile the release packages.

Just to confirm, is this something happening every time you install, or it was a single time? If you retry, does the error still show?

3

Hi,

I had successfully installed it before. However, I recently needed to change my development environment and I am now trying to perform the installation again.

Unfortunately, I am consistently getting the same error, so I am unable to complete the installation. I have retried multiple times and the issue persists.

Best regards

4

Just to confirm, which version of FlexCel is the one you are installing?

5

Hi,

Of Course,
It’s FlexCel v7.26

6

I've been checking, but I have not many ideas. The really strange thing is why it is compiling for debug, but failing to compile in Release. If there is something wrong with the Delphi install, it should fail both in debug and release.

Can you check installing directly with smartsetup?

  1. Get smartsetup from here: https://github.com/tmssoftware/smartsetup/releases/download/3.4/tmssmartsetup.zip
  2. Unzip it in some folder
  3. open cmd.exe and cd to that folder.
  4. tms credentials
  5. tms install tms.flexcel.vcl

Do you see the same error? This might help me isolate where the error is coming from