Support

Issues with winapifamily.h and other header files after installin...

Written by David Millington on . Posted in RAD Studio

There is a known issue where occasionally, after the C++Builder and RAD Studio 10.1 Berlin Update 2 installer has run, eight header files may be missing from C++Builder’s include\windows\sdk folder.

The bug manifests as trying to build a Windows C++ application, and getting a compiler error at the top of windows.h stating that winapifamily.h was not found.


Upgrading from Delphi or C++Builder Berlin Starter edition to hig...

Written by Sarina D on . Posted in Installation / Registration

This post was updated on November 16th, 2016.

The Feature Installer (also known as the GetIt Installer) for Berlin Update 2 Anniversary Edition includes license detection support for detecting existing Berlin licenses. If an existing license of the same version of the product is found on your system, you will see a version of this screen during the install process. You can proceed with the installation using an existing license or enter a new license. Please note that this screen is only shown when an existing Berlin license is found on your system.

The Update 2 installer should automatically trigger the uninstall process prior to installing Update 2 system. The steps outlined below are only necessary should you run into issues during the uninstall/reinstall process.

Note: It is recommended that you use the same installer (offline installer or web installer) to re-install or install an update since the registry settings will not be compatible.

 


 

This post outlines the steps for upgrading from Starter to higher editions of the same version on the same machine. Please note that Delphi Starter and C++Builder Starter cannot be installed on the same machine. Installing higher editions of the same version alongside Starter on the same machine is not supported and will not work.

 

Related links:

 

Upgrading from Starter to Pro/Enterprise/Architect

The following covers the steps required to install Delphi, C++Builder or RAD Studio Pro/Enterprise/Architect if you currently have Delphi or C++Builder Starter installed. The steps below assume that you are intending to install the higher edition on the same machine.

 

Step 1: Launch LicenseManager.exe

The License Manager can be found in C:\Program Files\Embarcadero\Studio\18.0\bin

 

Step 2: Add and register your higher edition license

Select Register to launch the registration wizard. Next, enter and register your new license. After successfully registering your higher edition license, it is recommended to remove the Starter license (although it’s not required).

 

Step 3: Uninstall Starter

Double-click on the Update 1 executable to launch the installer. This will uninstall the Starter edition. Alternatively, you can kick off the uninstall process by going to your Windows Control Panel and selecting Apps & Features.

 

Step 4: Install Update 1

After the uninstall is complete, the install will proceed. The Update 1 installer will now automatically pick the higher edition license you previously registered in Step 2.

 


 

Note: If you have already uninstalled Starter, and are looking to install a higher edition of the same version on the same machine, there are two options:

 

  1. Reinstall the Starter edition, then follow the steps outlined above

  2. Manually remove the Starter license key. To remove the individual license, you can delete/rename the C:\ProgramData\Embarcadero directory.  This is the local license storage and removing it will remove license information for *all* recent versions on your machine (please use with care). After removing the Starter key and uninstalling Starter, the Update installer will prompt you to enter your new license.

 


InterBase and Windows 10 Anniversary Update

Written by Steve A416 on . Posted in Support

We are getting reports from customers who are unable to connect to InterBase after applying the Windows 10 Anniversary Update. The error could be:

"Cannot attach to password database"

or

I/O error for file "C:\ProgramData\Application Data\Embarcadero\InterBase\gds_db\admin.ib"
Error while trying to open file
The system cannot find the file specified."

Since the release of InterBase XE3, the location of the password database, admin.ib has been determined by the IBCONFIG setting, APPDATA_DIRECTORY. The default value for this is

APPDATA_DIRECTORY         "C:\ProgramData\Application Data\Embarcadero\InterBase\<instance name>"

It turns out that Application Data is not a real directory but is what is known as a junction point that just points back to c:\programdata. When the Windows 10 update is run, this junction point is deleted. The way around the problem is to do the following:

  1. Run Notepad or your favourite text editor as Administrator.
  2. Open IBCONFIG. This is located in the InterBase installation directory
  3. Locate the APPDATA_DIRECTORY setting.
  4. Change this to APPDATA_DIRECTORY         "C:\ProgramData\Embarcadero\InterBase\<instance name>"
  5. Save the file and restart InterBase.

 


Get the new Powered By, Built With and Built For Logos

Written by Jim McKeeth on . Posted in RAD Studio

Embarcadero Cool App ContestThe Embarcadero Cool App contest is showing a lot of very cool apps that are built with Delphi, C++Builder, RAD Studio, InterBase and FireMonkey. So we've created some new graphics you can use to proudly show off your favorite development tool.

You can use the Built With or Powered By logos to highlight apps that use one of our products. Then the Built For ones are for those amazing tools, apps or libraries that are designed to work with our products. 

Let me know if there are other variations of these images that you need and enter your cool apps in the contest so you can win $2000 credit towards your next purchase. A new winner is announced every month!

DataSnap

  

RAD Server

  

VCL

  

C++Builder

  

Delphi

  

FireMonkey

  

InterBase

  

RAD Studio

  

 


“This version of the product does not support command line comp...

Written by Borja on . Posted in Installation / Registration

Some customers have reported that the Delphi compiler (dcc32.exe) that they have in their installation having a correct Professional, Enterprise or Architect edition of the product is not the correct one. This compiler is used if you perform builds outside of the IDE (for instance during the installation of several 3rd party components).

The first step of the installation of the IDE using the new feature installer installs a basic IDE with very limited functionality. This mini-IDE has the “trial” Delphi compiler that cannot be used to compile any program (trial licenses don’t include the final command line compilers). Afterwards, once you install the 32-bit Windows platform, the real “dcc32.exe” has to be copied to the “bin” folder of the product. Under some circumstances (an antivirus accessing the “trial” dcc32.exe file, for instance) the compiler is not correctly overwritten and you could still have the “trial” version on your “bin” folder.

If you have this problem please copy the correct dcc32 compiler from:

C:\Users\Public\Documents\Embarcadero\Studio\18.0\CatalogRepository\Core_Common_Files_Enterprise-18.0.Build.22858.6822\TARGETDIR\bin

Or

C:\Users\Public\Documents\Embarcadero\Studio\18.0\CatalogRepository\Core_Common_Files_Professional-18.0.Build.22858.6822\TARGETDIR\bin

To the “bin” folder of your installation (by default C:\Program Files (x86)\Embarcadero\Studio\18.0\bin) and the issue will disappear.


Manual uninstall of Rad Studio/Delphi/C++Builder 10.1 Berlin

Written by Borja on . Posted in Installation / Registration

Launch the License Manager from the bin folder (by default "C:\Program Files (x86)\Embarcadero\Studio\18.0\bin\LicenseManager.exe") and delete any trial or beta (Test Field) license that you can find. Check it under “License Details” in the center column.

 

Under your Control Panel's Program and Features Add/Remove Program uninstall the following entries:

 

  • RAD Studio 10.1 Berlin 18.0

 

Please follow these instructions to remove any leftover files:  

 

  1. If Windows 32-bit, remove the C:\Program Files\Embarcadero\Studio\18.0 directory (or the custom folder you had used).
  2. If Windows 64-bit, remove the C:\Program Files (x86)\Embarcadero\Studio\18.0 directory (or the custom folder you had used).
  3. Remove the C:\Users\Public\Documents\Embarcadero\Studio\18.0 directory
  4. Remove the C:\ProgramData\Embarcadero\Studio\18.0 directory.
  5. Remove the %APPDATA%\Embarcadero\BDS\18.0 directory.
  6. Remove the following hidden folders with a GUID name in C:\ProgramData\
    1. {FE8BEBBE-9A66-4252-9271-3B862ED0CA94}temp (Win 10 SDK files to copy to the product)
  7. Remove the HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\18.0 registry key
  8. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Embarcadero\BDS\18.0 registry key
  9. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{F4A93EC9-7AD8-4874-853D-02C09A51B141}_is1 or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90E8837E-3E59-444F-B83F-39BAB9B5336D} registry keys if they exist.
  10. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Embarcadero RAD Studio 10.1 Berlin registry key if it exists.
  11. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Embarcadero\BDS\18.0
  12. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{F4A93EC9-7AD8-4874-853D-02C09A51B141}_is1 or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{90E8837E-3E59-444F-B83F-39BAB9B5336D} registry keys if they exist.
  13. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Embarcadero RAD Studio 10.1 Berlin registry key if it exists.
  14. If Windows 32-bit, remove the following files from C:\Windows\System32\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL
  15. If Windows 64-bit, remove the following files from C:\Windows\SysWOW64\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL

 

Field testers should also do the following (and others may want to as well):

 

  1. Delete the BigBen license from License manager before uninstalling it or during the installation of RAD Studio 10.1 Berlin

 

If you had problems in the second step (uninstalling from Windows Control Panel), try this Microsoft tool to solve uninstallation problems:

 

http://go.microsoft.com/?linkid=9779673


How to report a C++ Compiler or Linker problem and workarounds

Written by Juan Antonio Ruzafa on . Posted in RAD Studio

This is a guide with some hints on how to report Rad Studio C++ Compiler and Linker issues to Embarcadero's Quality Portal. If you follow these advices, R&D team will have more chances to reproduce and fix the issue you've found. Besides, you'll find some workarounds for common problems.

 

How to report a C++ Compiler problem

 

Enable "Diagnostic" Verbosity 

  • Go to Tools | Options | Environment OptionsCompiling
  • Change the "Verbosity" drop down to "Diagnostic":

 diagnostic

  • Do a build of the project
  • Save the messages from the "Output" tab of the Messages Pane to a text file:

output

  • Attach the text file to your bug report

 

Include Preprocessed files

When reporting a compiler crash, the report should contain a narrowed down testcase that illustrates the crash. If that is not possible, then include a Preprocessed copy of the source file that causes the crash. To create a 'Preprocessed' file, right click on the source file that crashes in the Project Manager and select "Preprocess". The IDE will create a .i file. Save that file and include it with the report.


preprocesed

 

 

You must add the compiler command line to your report, as shown in the Output tab of the Message View:


copy_output

Command Line: Build vs Output Tab

It is easier to copy the Command Line from the "Build" tab but it's preferable to copy the Command Line included with your report from from the"Output" tab because the "Build" tab wraps long command lines.

 

 

How to report a Linker problem

With the case of the linker crashes, R&D team usually needs the whole linkset to reproduce the issue. IMPORTANT: We do not need source: just objs and libraries, so if you can't provide us the source code is generally fine for linker issues.

Get Linker Team to Lookup XXX#### Code

If it's a "Fatal: Error detected (XXX####)", the linker team can look up the error (the 3 letter represent a linker source file and the numbers the line number) and maybe provide some guidelines about what might be happening. In some cases these point to the compiler having generated a bad object file.

 

 

Posible workarounds for Linker problems

Turn Off Incremental Linking

Turn off Incremental linking; Clean the Project and Rebuild. This can help with ilink32 but does not help with ilink64 as "-Gn" is hardcoded in the IDE for WIN64.

Bump Heap Sizes (For 'Out of memory')

For ilink64, if the error is "Fatal: Out of memory", the -GH switch can help. First you need to make ilink64 LARGE ADDRESS AWARE. To do that use the "editbin" utility provided with Visual Studio:

editbin.exe /LARGEADDRESSAWARE $BDS/bin/ilink64.exe

Then you use the -GH switch to increase the heap that was overflowed. For example, a typical failure might report:


Turbo Incremental Link64 6.72 Copyright (c) 1997-2015 Embarcadero Technologies,
Inc.
Overrun on linker heap: dwarf_info
...
dwarf_info 0x06039000 0x06000000
...
Fatal: Out of memory

 

The "dwarf_info" heap overflowed. To remedy we ask the linker to allocate a bigger size via: "-GHdwarf_info=0x0E000000".
You might find that after increasing one heap, another one overflows. So the final command line might read:

-GHinfo=0x24000000 -GHdwarf_info=0x0E000000 -GHbss=0x0E000000 -GHdwarf_str=0x0A000000 -GHdwarf_line=0x06000000 -GHcode=0x0E000000

Out of Memory and Unknown Heap error

Sometimes ilink32 raises an OOM and then "Unknown Heap" error (normally that unknown heap is "tds"). This workaround may help:

In the IDE:

  1. Go Project | Options | C++ Linker | Advanced | Additional options
  2. Add "-GHtds=0x0A000000" without the quotes.
  3. Try to link again.

 


Manual uninstall of Rad Studio/Delphi/C++Builder 10 Seattle

Written by Borja on . Posted in Installation / Registration

 Launch the License Manager from the bin folder (by default "C:\Program Files (x86)\Embarcadero\Studio\17.0\bin\LicenseManager.exe") and delete the licenses that activate your RAD Studio 10 Seattle product (XE8 or 10 Seattle licenses). Check it under “License Details” in the center column.

Under your Control Panel's Program and Features Add/Remove Program uninstall the following entries:

  • Embarcadero RAD Studio 10 Seattle

Please follow these instructions to remove any leftover files:  

  1. Remove the %USERPROFILE%\Documents\Rad_Studio_10_Seattle_Downloads folder
  2. If Windows 32-bit, remove the C:\Program Files\Embarcadero\Studio\17.0 directory.
  3. If Windows 64-bit, remove the C:\Program Files (x86)\Embarcadero\Studio\17.0 directory.
  4. Remove the C:\Users\Public\Documents\Embarcadero\Studio\17.0 directory
  5. Remove the C:\ProgramData\Embarcadero\Studio\17.0 directory.
  6. Remove the %APPDATA%\Embarcadero\BDS\17.0 directory.
  7. Remove the following hidden folders with a GUID name in C:\ProgramData\
    1. {09FECC13-2950-4AE6-BB23-05C206979F18} or {5D50B637-4756-435A-816E-68ABFE86FC69} (main installer)
  8. Remove the HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\17.0 registry key
  9. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Embarcadero\BDS\17.0 registry key
  10. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{25059B3C-FFC7-41B6-80A9-80E4A2ED5564} registry key.
  11. If Windows 32-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Embarcadero RAD Studio 10 Seattle registry key.
  12. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Embarcadero\BDS\17.0
  13. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{25059B3C-FFC7-41B6-80A9-80E4A2ED5564} registry key.
  14. If Windows 64-bit, remove the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Embarcadero RAD Studio 10 Seattle registry key.
  15. If Windows 32-bit, remove the following files from C:\Windows\System32\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL
  16. If Windows 64-bit, remove the following files from C:\Windows\SysWOW64\:
    1. BDEAdmin.*
    2. CC32*.DLL
    3. Midas.*
    4. Xerces*.DLL

Field testers should also do the following (and others may want to as well):

  1. Delete sample files from %PUBLIC%\Public Documents\Embarcadero\Studio\17.0
  2. Delete DBExpress connection files from %PUBLIC%\Public Documents\Embarcadero\Studio\dbExpress\17.0
  3. Delete the Aitana license from License manager before uninstalling it or during the installation of RAD Studio 10

If you had problems in the second step (uninstalling from Windows Control Panel), try this Microsoft tool to solve uninstallation problems:

http://go.microsoft.com/?linkid=9779673

 

 


Rad Studio Quality Portal user guide

Written by Juan Antonio Ruzafa on . Posted in RAD Studio

Embarcadero’s Quality Portal provides a community process for resolving, clarifying, and tracking quality issues regarding Embarcadero's products and services. Embarcadero Developer Network (EDN) members can create bug reports and feature requests, view other members' reports, and comment and vote on the reports most important to them. Embarcadero personnel also participate in Quality Portal, providing a permanent link between Embarcadero customers and the teams who produce Embarcadero's products. This guide is here to help you to report issues about Rad Studio product.

Using Embarcadero’s Quality Portal

Before using Quality Portal (QP), you must create your EDN user account. Go to https://members.embarcadero.com to create your account, or login if you already have an existing account.

EDN membership is free, and gives you access to the services offered on the Embarcadero Developer Network, including Quality Portal.

Community process

Quality Portal is a peer-supported application, where other members of the community can comment or vote on existing reports, or make their own. With Quality Portal, the community has a great impact in helping Embarcadero prioritize the request our customers make. You can "Watch" other users issues, to get notified when they are updated.

Maximizing your Quality Portal benefits

You can get the most benefit from QP by using it "properly." This section of the user guide is describes effective techniques for posting bug reports, making feature requests and suggestions, and actually getting the bugs, features and suggestions worked on. After all, you're using QP because you want Embarcadero to address issues you care about. This section of the user guide describes the various ways you can maximize your positive impact with Quality Portal.

Reporting bugs guide

For many people, the initial interest in QP will be bug reports. The principles discussed in this section discuss both obvious and subtle ways to effectively create and process bug reports.

You will see a form similar to:

image2015-9-4_17-31-18

 

Be specific

Write effective bug reports. Be as complete as possible when describing the bug and what happens. Include steps. The most efficient way to get a bug fixed is to provide a reproducible test case. If you can't readily reproduce it, describe as completely as you can what happened before you saw the bug. Bug reports must provide all the required information in one place.

Golden rule: include just one issue into one report.

Issue Type

  • bug Bug: An issue with the product
  • documentation Documentation bug: An issue with help or product documentation.

Summary

Give the report a short, but descriptive summary. “TButton is not working” is not a good title, but “[Android] An error is raised when TButton is invoked by double tapping” is better.

When appropriate, use tags in the title to help whoever reads it understand the context better.

A good summary helps to quickly identify what’s going on and help to reduce duplicate issues. Avoid describing generic problems in the summary. You should never use:

  • I have an issue with XYZ
  • XYZ doesn’t work properly

A few examples of poor summaries and their good equivalents:

Poor: Access violation in IDE

Better: Opening an empty .pas file raises an access violation

Poor: Push notification bug

Better: Push notification count adds one extra notification

Component

Identify which sub-part of the software is affected by this bug.

Description

All the information generated by the issue. Where available, include:

  • Full error message
  • Full call stack
  • If you think it is relevant, include info about your environment (e.g. Android version or Windows locale settings)
  • For bugs that manifest themselves visually (e.g. Controls not being displayed properly or IDE layout issues) include a screenshot to help whoever reads your report to evaluate it.
  • If relevant add device logs, like logcat output for Android.
  • For error messages or call stacks use either {code} or {quote} tags.
  • If you base your report on an external source of info (e.g. MSDN page for an API call), include a link to that info
  • If your bug report contains code, either attach it to the project or add it to the Steps section. If you add code as text to your report, make sure to use {code} tags. This stops JIRA from interpreting your code and messing it up and also helps with the readability of the report (avoids scrolling a few pages to get to relevant fields).
  • Keep the size of the attachment to the minimum. ZIP your files and never include binaries that are generated by compiling them (e.g., DCU’s or EXE’s). Only use ZIP format, never use other formats that require a 3rd party program.
  • Don't include more than one issue into one report. Report separately, and link each other as needed.

Steps

The goal is to show how to reproduce the bug. Keep it concise and easy to read, you should describe it as a recipe to reproduce the bug. Try to achieve the objective with the minimum number of steps.

Note: Error messages or Call stacks go in the Description, not Steps. For example, Description should say “The following error is raised when invoking TButton by double tapping it on my Android device: [error message]” and the Steps should just provide instruction as to how to reproduce the issue.

Expected and Actual Results

At the end of your step-by-step description, you must describe what should be the expected result and what actually happens.

Example of a poor description:

Expected: Application doesn’t crash

Actual: Application crashes

Better use:

Expected: Application shows up the XYZ menu

Actual: Application raises an access violation (see the attached stack-trace)

Isolate reports

Be conscientious about submitting corollary thoughts as new reports, not just putting them in as comments for an existing report. This will ensure that the issue is tracked and (hopefully for your interest) eventually worked on.

Research bug reporting techniques

Listed below are some example pages for various bug reporting tools found on the Web. While not all of the information or examples provided here may help, in general they certainly discuss good practices that will help you both use QP effectively and get Embarcadero to work things you care about.

Understanding Duplicate reports

A "duplicate" report is marked as such by QA team. Which report is marked as the "master" and which a "duplicate" is based on which report gives the most accurate and detailed information describing the issue both (or many) reports discuss.

The master report can change over time if someone else submits another duplicate, but that duplicate actually would describes the issue better. "Master" and "duplicate" has nothing to do with who got in first, but which report most accurately covers the issue.

Typically, a “duplicate” issue has "Resolved" status and "Duplicate" resolution,  linked to “master” issue with “duplicates” link. You must to check status and watch updates at the "master" issue.

How to interpret some of the fields in QP

Because Quality Portal synchronizes with internal systems, there are some fields that have meaning for our internal processes that may not have obvious meaning outside of our internal processes. The following tables will hopefully explain some of the values for these synchronized fields.

Status field

Value
Description
Reported New defect, requires tester review
Open Open defect, requires resolution
Resolved Internal work done, reporter can verify or dispute resolution
Needs Feedback Requires additional information/steps
Closed Closed defect, no action required

A report starts off with a status of “Reported”. When an Embarcadero QA tester validates it in Embarcadero’s internal bug tracking system, the status goes from “Reported” to “Open”. When work is completed with the report, the status goes from “Open” to “Resolved”.

 Resolution Field

Value
Description
Fixed Bug has been fixed
Cannot Reproduce Bug could not be reproduced as submitted
Works as Expected Behavior is as designed
Duplicate Bug is a duplicate (must note dup bug #)
Test Case Error Bug description is invalid as submitted
Needs More Info Need more information/demo/steps
No Longer Applies Feature has been removed or the bug is no longer relevant
Won't Fix This will never be implemented or fixed

For issues that are returned with Needs More Info, the status will be marked as ‘Needs Feedback’ to allow reporter to add additional information. You must use “Update Content” button when submitting additional information.Once changes submitted via ‘Update Content’ status gets back to ‘Reported’ and QA team will repeat validation internally. "Update content" also may be used in case after issues submitted appeared it need some corrections.

Generally try to clarify description adding more details and/or context info using the recommendations given above or add/review steps to reproduce. Attaching sreenshots and/or projects would be helpful as well.

Hints and Tips

Text effects and code format

Text effects are used to change the formatting of words and sentences. This contributes to create clean and neat bug reports easier to understand.

 

*strong*
Makes text strong.
_emphasis_
Makes text emphasis..
??citation??
Makes text in citation.
-deleted-
Makes text as deleted.
+inserted+
Makes text as inserted.
^superscript^
Makes text in superscript.
~subscript~
Makes text in subscript.
{{monospaced}}
Makes text as monospaced.
bq. Some block quoted text

To make an entire paragraph into a block quotation, place "bq. " before it.

Example:

Some block quoted text
{quote} here is quotable
content to be quoted {quote}

Quote a block of text that's longer than one paragraph.

Example:

here is quotable
content to be quoted
{color:red} look ma, red text! {color} 

Changes the color of a block of text.

Example:

look ma, red text!

Notation
Comment

 

 

 

Code format improves how code is presented

 

{code:delphi}
program Sample_prog; 
begin 
write('Hello World. Prepare to learn Delphi');
readln; 
end.
{code}
program Sample_prog;
begin 
 write('Hello World. Prepare to learn Delphi');
 readln; 
end.

{code:c++}
#include <random>

int main()
{
std::random_device random_device;
std::mt19937 random_engine{random_device()};
std::bernoulli_distribution coin_distribution{0.25};
bool outcome = coin_distribution(random_engine);
}
{code}

#include <random>
int main()
{
 std::random_device random_device;
 std::mt19937 random_engine{random_device()};
 std::bernoulli_distribution coin_distribution{0.25};
 bool outcome = coin_distribution(random_engine);
}
Notation
Comment

 

Sample bug

Here it is a sample bug with all concepts explained above: https://quality.embarcadero.com/browse/RSP-12206

 


Package c:\program files (x86)\embarcadero\studio\16.0\bin\DUnitX...

Written by DavidI on . Posted in Support

If you uninstall Rad Studio XE8 using all the defaults, then install Rad Studio XE8 Subscription Update 1, you will get the following error at start up:


Package c:\program files (x86)\embarcadero\studio\16.0\bin\DUnitXRuntime220.bpl can't be installed because it is not a design time package.
Do you want to attempt to load this package the next time a project is loaded?


DUnitXRuntime220.bpl was incorrectly marked as a Runtime package in the original release of Rad Studio XE8 and this is corrected with Update 1. If you uninstall using all the defaults, all your IDE settings are unchanged when you install Rad Studio XE8 Subscription Update 1. This will cause the IDE to attempt to DUnitXRuntime220.bpl as it did in the past and this error to occur. You may safely not load the package in the future. If you want your IDE settings to be set to the all the defaults (and loose all IDE customizations), then launch your product with the -cleanregistry argument, as documented here:docwiki.embarcadero.com/RADStudio/XE8/en/IDE_Command_Line_Switches_and_Options


Check out more tips and tricks in this development video: