[Ray Konopka]

Hi Ariagna,
CodeSite Studio is sold as a traditional software license. It is a one-time payment, and NOT a subscription. The license is the traditional “like a book” license. You are allowed to install the logging classes (the code that you link into your programs) onto multiple machines provided you are the only one using the software at a time. If you have another developer that will be compiling/building code using the CodeSite logging classes, then a separate license should be purchased for each developer.

Ray

[Ray Konopka]

Hi Ariagna,

Thank you for your interest in CodeSite Studio. I will do my best to answer your questions.
1. I believe what you are asking for in this question is the ability to encrypt the data that is captured with CodeSite. The current version of CodeSite does not support automatically encrypting the message data. We are investigating ways to do this in a relatively seamless manner for a future release.
2. The current version of CodeSite Studio supports sending CodeSite messages to a remote computer using TCP. Specifically, your application would specify a TCP remote destination. Then when your app generates a CodeSite message, it is sent to the CodeSite Dispatcher running locally on the machine. Then the local Dispatcher will send the message to the CodeSite Dispatcher that is running on the remote computer. The Remote Dispatcher will then typically save the CodeSite message to a log file.
3. There are several methods of controlling the amount of data that is generated/sent by CodeSite. For example, you can setup separate CodeSite loggers and specify a Category for each logger. Then you can Enable/Disable the loggers as necessary to control the amount of messages that are logged. The Viewers also provide the ability to create filtered views so that you only see the messages that you are interested in. For example, you can create a new view that only shows you messages from a specific process.

I hope this answers your questions.
Ray

[Ray Konopka]

Hi Chris,

Thank you for submitting the report. I have also been very frustrated with the situation. This is one of the reasons why I have been encouraging people to submit reports so that Embarcadero can see that many, many developers are dependent on these components. I will be presenting at EKON in a couple weeks and will try to connect with Embarcadero team members in attendance.

Ray

[Ray Konopka]

Hi Chris,

Thanks for sending the test project. I was able to reproduce the issue you are running into. The fact that you are building a 64-bit application is key to the issue. More specifically, the “Support address space layout randomization” setting, which in 11.2 is set to True by default for 64-bit applications. You can work around the issue by turning this setting to False. The setting is located in:
Project Options
Building
Delphi Compiler
Linking
Support address space layout randomization

As for reporting issues with KSVC, Embarcadero still hasn’t added specific entries for the components. However, Marco Cantu has suggested that issues can be reported under the general VCL category. Furthermore, the subject of the issue should start with KSVC so that the issue is marked as a KSVC-related issue. For example, if you go to Quality Portal and conduct an issue search for “KSVC” you will see many other examples.

Ray

[Ray Konopka]

Hi Chris,

I have been unable to duplicate the error condition you are experiencing. Are you able to reproduce the issue in a test project? If so, please send the source (no executables) to support at raize.com and I’ll take a look. I’m curious if there are property settings that are resulting in the error.

I would also encourage you to file a report about this issue on Embarcadero’s Quality Portal so they are aware of the issue. Any fix will need to come from Embarcadero as they own the components now.

Ray

[Ray Konopka]

Hi,

I saw some reports on Embarcadero’s Forums regarding issues with installing KSVC in 11.2. It appears that Embarcadero has reverted to a previous build which is now installing properly in 11.2. As such, I would suggest trying to install the components again.

Ray

[Ray Konopka]

Hi Gordon,

While what I stated earlier is indeed true, we discovered that there was an issue with the CodeSite Logging Classes when ASLR (Address Space Layout Randomization) was enabled. The problem affects 64-bit applications and prevents CodeSite messages from being delivered to the CodeSite Dispatcher. As such, Live Logging and File Logging do not work.

We have just released a new 5.4.1 version that fixes this problem. Please see this link for more details: CodeSite ASLR Support

We have also provided Embarcadero with an update to the CodeSite Express edition that is deployed through the GetIt Package Manager. The new 5.4.1 build should be available in GetIt soon.

Ray

[Ray Konopka]

Delphi 11.2 is dcu compatible with 11.0 and 11.1. As such, the latest version of CodeSite will work with 11.2.

Ray

[Ray Konopka]

Hi Steve,
I apologize for the delay. I just created a test app using Delphi 10.2.3 and DropMaster 2.5.2 and the TDMTextTarget component is working just fine in the app.
Are you able to recreate the issue in a test project and send me the source code (no executables) and I can take a closer look?

Did anything change recently with your system? Before Jim went on vacation, he saw your message and thought that it sounded like it might be related to permissions.

Ray

[Ray Konopka]

Hi Steve,
I apologize for the delay. I just created a test app using Delphi 10.2.3 and DropMaster 2.5.2 and the TDMTextTarget component is working just fine in the app.
Are you able to recreate the issue in a test project and send me the source code (no executables) and I can take a closer look?

Did anything change recently with your system? Before Jim went on vacation, he saw your message and thought that it sounded like it might be related to permissions.

Ray

[Ray Konopka]

Hi Dave,

I believe you are getting “Not enough actual parameters errors”.

Yes, Embarcadero needs to update the demo code that comes with the components. In the meantime, you can fix the missing parameter errors with the demo by adding Self as the first parameter to the method calls.

For example,

if UsingSystemStyle then
becomes
if UsingSystemStyle( Self ) then

C := GetGradientPanelFrameColor( FCurrentGCS )
becomes
C := GetGradientPanelFrameColor( Self, FCurrentGCS )

Ray

[Ray Konopka]

Hi Mike,

The event that I mentioned in my response was the OnDblClickOpen event and not the OnDlbClick event. The OnDblClickOpen event handler has the Handled parameter.

Ray

[Ray Konopka]

Hi,

Not in the current version. However, in CodeSite 6, an internal dispatcher will be available, which will mean that the CodeSite Dispatcher application does not need to be installed. The CodeSite Dispatcher will still be available to handle situations where you want to capture CodeSite messages from multiple applications into a single log file.

Ray

[Ray Konopka]

Hi Jan,

Thank you for your interest in the remote logging capabilities of CodeSite. Remote logging leverages the CodeSite Dispatcher to transport CodeSite messages to another CodeSite Dispatcher running on a remote computer. And since CodeSite allows you to specify multiple destinations for your CodeSite messages, you could have an application’s CodeSite messages saved locally in a CodeSite log file as well as being transported to a remote dispatcher where the message could be saved in a “remote” log file, or displayed in the Live Viewer running on the remote machine.
When it comes to logging in general and especially with remote logging, it is important to consider how the logging information is going to be used. You asked about 250 client computers logging to one server. You could certainly configure 250 client computers to transport their CodeSite messages to a single remote computer. Of course, performance is certainly going to be an issue if each client application is sending a high volume of large CodeSite messages.
But even if you will not be taxing the system with lots of data, it is still important to consider what you want to do with the logging information once it is captured. For example, does it make sense for all CodeSite messages from each client to be placed into a single CodeSite Log File on a remote computer? If there are interactions between the various client computers, then perhaps it makes sense to see all the messages in one log file. On the other hand, if the intent is to simply have a remote version of the log so a support staff member can more easily access client logging information, then it may make more sense to have each remote log file include the name of the client computer.
In regards to what kind of server, that will really depend on the volume of CodeSite messages you expect to be sending, and what payload those messages will contain. For example, sending a simple CodeSite message that logs the current value of a property is much different than a CodeSite message that captures all of the published properties of the current form, which is much different than a CodeSite message that contains a screenshot of the current desktop.

Ray

[Ray Konopka]

Hi Mike,

You can create an event handler for the OnDblClickOpen event of the TRzShellList and in the handler set the Handled parameter to True. For example:

procedure TForm38.RzShellList1DblClickOpen(Sender: TObject; var Handled: Boolean);
begin
  Handled := True;
end;

Ray

[Author]

Posts