[Ray Konopka]

Hi Andrew,
We’ll be releasing a new version of DropMaster 2.x that includes the necessary files to support the modern 64-bit C++ compiler soon.
Ray

[Ray Konopka]

Hi Chris,
Thanks for the report. Unfortunately, I am unable to duplicate the issue, but that could be because I’ve made other changes to the TRzSpinEdit and those affected this particular behavior. However, I would like to confirm that. Are you able to duplicate the issue in a test project? If so, please the source to the test project (no exe) to our support email and I’ll take a look. Also, what version of Delphi are you using?

Ray

[Ray Konopka]

Hi Chris,
It is best to submit them on Embarcadero’s Quality Portal for tracking. When you do, be sure to put KSVC in the subject line for easier identification. Embarcadero does not have a field to specify this library.
Also, I don’t mind if you also post a heads up here to any reports submitted.
Ray

[Ray Konopka]

Hi Nat,

Thank you for providing more information about what you are trying to do–that is, compiling the RCDemo.

Yes, because of some of the changes that Embarcadero introduced into the PROJ file and the fact that RCDemo supports older versions of Delphi, the prompt to select an SDK is presented when you first open the project in Delphi 11. Typically, the built in SDK is automatically selected and the user just clicks the OK button to continue. However, it appears from the screenshot, that you opted to create a new SDK. That is why you were prompted to download other items from Microsoft’s website.

From the remaining issues you describe it sounds like you created an SDK for creating a UWP app and not a standard Win32 (or Win64) app.

I just loaded the RCDemo project (in Delphi 11) on a new VM and I was prompted to select an SDK, but I just selected the default Win32 SDK that was presented. The project loaded, however, when I tried to compile the demo, I did get an error, but it is a known error. Embarcadero did not update a couple of the source files in the demo with the Delphi 11 release. Fortunately, the fixes are straight-forward.

TabsFrame.pas
In: procedure TFmeTabs.Init;
Replace:
if UsingSystemStyle then
With:
if UsingSystemStyle( Self ) then

CustomFramingFrame.pas
In: procedure TFmeCustomFraming.Init;
Replace
if UsingSystemStyle then
With:
if UsingSystemStyle( Self ) then

MainForm.pas
In: procedure TfrmMain.VisualStyleClick(Sender: TObject);
Replace:
C := GetGradientPanelFrameColor( FCurrentGCS )
With:
C := GetGradientPanelFrameColor( Self, FCurrentGCS )

Then you’ll be able to build the RCDemo project successfully.

As for the TRzRegIniFile component, you are correct, that component does not save data for all components. In fact, the TRzRegIniFile is just a conduit to a data store, as I described in a previous post. The TRzFormState component is designed to save certain properties of a form to the data store referenced by the TRzRegIniFile component. To persist the properties of other components in your application, please take a look at the TRzPropertyStore component.

Ray

[Ray Konopka]

Hi Venkatesan,

Version 5.4.3 of CodeSite has been released. The new version includes the updated CS Tools installer (also with new version number) and a minor update to the CodeSite Viewers.

Ray

[Ray Konopka]

The KSVC controls have no dependencies on Windows Kits. So, I’m not sure what caused Windows Kits to be installed.

As for the TRzRegIniFile, it is designed to use either an INI or the Registry. That is the point of the control. You control where the actual data store is located. The default is an INI file.

“I don’t understand why Embarcadero needed to buy the rights to KSVC if there were problems?”

I’m sorry, but I’m not sure I understand your question.

Ray

[Ray Konopka]

Hi Nat,

That exception is coming from the TRzFormState component. The TRzFormState component utilizes a connected TRzRegIniFile component to control where the form state information is actually stored.

If you select the TRzFormState component in the Form Designer and then press F1, you should see the help for TRzFormState that talks about assigning a TRzRegIniFile component to the RegIniFile property. You can then click on the TRzRegIniFile link to learn more about the components property.

Ray

[Ray Konopka]

Hi Nat,

That appears to be an error that is not related to the KSVC components.

Ray

[Ray Konopka]

Hi Venkatesan,

I understand your request, I will do my best to squeeze this in as soon as possible.

Ray

[Ray Konopka]

Hi Steve,

I apologize for the delay in approving your post to appear in the forum. Unfortunately, the changes that Embarcadero made to the TRzCheckBox and TRzRadioButton components to better support High DPI also broke the functionality of custom glyphs. I am trying to get this issue fixed. I will keep you posted.

Ray

[Ray Konopka]

Hi,
I have modified the CodeSite Tools installer to no longer use WMI and have uploaded the new CS5_Tools installer to the Raize Software website. You can download the new version here: https://raize.com/wp-content/uploads/CS5_Tools.zip

To be clear, the version of the tools is still 5.4.2, it is just the installer that has been updated.

Ray

[Ray Konopka]

Hi,

Thank you for the additional information. I have researched this issue some more, and I have discovered that the InnoSetup script that is used for CodeSite Tools installer does make use of the SWbemLocator to determine if any of the CodeSite Tools applications are currently running. The approach appears to be a pretty common practice with InnoSetups scripts. What is surprising is that WMI is not available on some of your customer’s computers. This particular module is the CodeSite Tools setup has been present for quite some time, and we’ve never received any reports such as this.

I’m looking into alternative methods to using the SWbemLocator and if that is not possible, coming up with a way to gracefully handle the situation that SWbemLocator is not found and still continue with the installer.

Ray

[Ray Konopka]

Hi,

We are not aware of any issues with the CodeSite Tools installer. However, in 5.3.3 the CodeSite Tools installer was changed to InnoSetup. The old installer was built with Wise Installation System.

Is the CS5_Tools.exe installer being run separately? Or, it is being launched from within your own product installer? Are you specifying any parameters to the CS5_Tools.exe program?

What type of machines are you running the installer on? From the message, it appears that InnoSetup may require WMI.

Does this error happen all the time? Or, just a certain machines?

Ray

[Ray Konopka]

Hi Ulrich,

To be honest, I had hoped that CodeSite 6 would be released by now. I had demonstrated many of the new features of CodeSite 6 at EKON and ITDevCon last fall. Unfortunately, like many of you, CodeSite’s tools were impacted by limitations in the KSVC. I hope to have more to say about this soon. I do apologize for being so vague.

Ray

[Ray Konopka]

Hi Csaba,

I already answered same question via email. I’m including response below in case others are interested.

—
One option is to use the CSFileExporter.exe tool that is included with CodeSite (including the Express edition). It is located in the CS5\Bin directory (typically, C:\Program Files (x86)\Raize\CS5\Bin). It is a command line tool that allows you to export messages from a CodeSite log file into a different format (i.e. XML, TXT, CSV).

The one downside to using the CSFileExporter is that you have to manually run it to export the data. One of the requests that we have been getting a lot recently is to provide a means by which CodeSite log data could be ingested into an aggregate system such as Splunk. As a result, in CodeSite 6, we are introducing a new destination type called a Digest that contains CodeSite messages in plain text, formatted for easy ingestion in to Splunk and other aggregate logging systems. Unfortunately, CodeSite 6 has not yet been released.

Another option is to utilize the OnSendMsg event available in CodeSite Studio to write out to a text file for each CodeSite message. The message data is included in the event handler. The downside to this is that you have to have CodeSite Studio and you have to write out the log file manually.

Of course, the Digest option in CodeSite 6 will be the best solution once it is released.

Ray

[Author]

Posts