XS1503 debug error occurs at different places on and on

[Jan]

Hello,

we migrated a project from Vulcan.NET to X#, and the compiler option "Implicit numeric conversions" (/vo4) is set (as it was already in the Vulcan.NET project).

We are getting the follwoing behaviour:

Developer is building the project -> no errors
Devoloper is editing let's say module Alpha.prg
Developer is building the project again -> Error XS1503 Argument1: cannot convert from 'dword' to 'int' in module Beta.prg

We can then correct this by doing explicit type conversions of course, but the above mentioned behavior occurs again and again in modules that compiled without errors before and that have not currently been edited.

Is there a way to end this behaviour?

Version is X# Cahors 2.20.0.3

Thank you,
Jan

[Chris]

Hi Jan,

This behavior usually means that you have selected (through the Solution Properties->Configuration Properties) not to include all projects (libraries) when doing a Project Build, in which case when you do a build, only the "active" project gets built, not the rest. If that's the case, it's only a "Rebuild" that forces rebuilding even projects that are set not to be built always.

So I think in some of the projects (libaries) you have set the /vo4 option to on, but in some others it may be to off. Or it's possible that you have set it to on for say the Debug configuration, but not for the Release configuration, and you do get the error as expected when you build for Release.

[Jan]

Hi Chris,

we have only one project in our solution (with /vo4 checked), and "Build" is checked in Solution->Properties -> Configuration Properties -> (our project) in Debug configuration as well as Release configuration.

Jan Hartmann

[leon-ts]

Hello Chris, Jan,
I reported this problem a year ago.
Here is the link (details there): https://www.xsharp.eu/forum/topic/3320
Since then, the problem has existed in all subsequent versions of X# and is often annoying.

[robert]

Guys,
I understand that this can be quite frustrating.
But without reproducible example, this problem will only be fixed if we accidentally find the code responsible for the problem.
So if you can create/share an example that shows this, then that would be very helpfull.

Robert

[HansjoergP]

Hello,
One question: if the error occurs, is another Visual Studio open in this case? I sometimes have cases where it seems that Visual Studio is getting data from another instance.
We had sometimes the error https://github.com/X-Sharp/XSharpPublic/issues/721