RIO: Start Debug Session changes source

[PeterPanettone 157]

In Delphi Rio 10.3.1, the Project is configured for Debugging:

 

 

Steps:

 

1. First I make sure that all source files are saved.

 

2. Then I start debugging (F9) 

 

3. Then, at the first breakpoint, I press F8 (Step Over). This makes this dialog appear:

 

 

When I look in the project folder, the only file which has been changed since debug start is MyProject.res.

 

So why this file gets changed after the start of the debug session?

 

This is the content of the RES file:

 

 

This is very annoying and did not happen in previous Delphi versions.

 

How can this be avoided?

Edited July 14, 2019 by PeterPanettone

[Der schöne Günther 316]

Did you really add your .res file to your project? I think it's an auto-generated one and you should neither have it in source control, nor added to your project...

[PeterPanettone 157]

39 minutes ago, Der schöne Günther said:

Did you really add your .res file to your project? I think it's an auto-generated one and you should neither have it in source control, nor added to your project...

What do you mean with "source control"? The res file is not part of the project files tree:

 

Edited July 15, 2019 by PeterPanettone

[Der schöne Günther 316]

I was talking about a "version control" system that helps you keeping track of what files were changed, when, and why. Notable examples include Git, Mercurial or the good old Subversion.

[PeterBelow 238]

22 hours ago, PeterPanettone said:

In Delphi Rio 10.3.1, the Project is configured for Debugging:

 

 

Steps:

 

1. First I make sure that all source files are saved.

 

2. Then I start debugging (F9) 

 

3. Then, at the first breakpoint, I press F8 (Step Over). This makes this dialog appear:

 

 

When I look in the project folder, the only file which has been changed since debug start is MyProject.res.

 

So why this file gets changed after the start of the debug session?

 

This is the content of the RES file:

 

 

This is very annoying and did not happen in previous Delphi versions.

 

How can this be avoided?

This is not normal behaviour, i have never encountered that myself with Rio. Do you also get that if you do a build before starting the debug session?

[PeterPanettone 157]

2 hours ago, PeterBelow said:

This is not normal behaviour, i have never encountered that myself with Rio. Do you also get that if you do a build before starting the debug session?

Yes, even when I do a build right before starting the debug session.

[PeterPanettone 157]

I HAVE FOUND THE CULPRIT!!! It is one of the CnWizards experts which inserts the compile date into the version record:

 

 

I believe there is no chance to avoid this when inserting the compile date.

[PeterBelow 238]

35 minutes ago, PeterPanettone said:

I HAVE FOUND THE CULPRIT!!! It is one of the CnWizards experts which inserts the compile date into the version record:

 

 

 

I believe there is no chance to avoid this when inserting the compile date.

Thanks for sharing the solution.

[Der schöne Günther 316]

With proper source control you would have seen this immediately 🙃

[PeterPanettone 157]

49 minutes ago, Der schöne Günther said:

With proper source control you would have seen this immediately 🙃

It is called "VERSION CONTROL"!

[PeterPanettone 157]

1 hour ago, PeterBelow said:

Thanks for sharing the solution.

I will ask the CnWizards developer to add an option to not be used in debug mode. If you think about it, there is no sense using the compilation date in when debugging.

[Sherlock 663]

Compilation date is rarely useful, only when you don't use "source version" control, you need that information. Your customers surely don't need it.

[PeterPanettone 157]

3 hours ago, Sherlock said:

Compilation date is rarely useful, only when you don't use "source version" control, you need that information. Your customers surely don't need it.

Well, it could be useful to specify a specific version of the program independently from the version number.

[Sherlock 663]

1 hour ago, PeterPanettone said:

Well, it could be useful to specify a specific version of the program independently from the version number.

Now that is something one should avoid anyway. Special builds for special customers create special problems. One version for all leads to the same problematic source for all - and generally speaking, source code is always problematic, as soon as it consists of more than "Hello World".

[PeterPanettone 157]

6 hours ago, Sherlock said:

source code is always problematic

There is truth in this.