CRLF gives XS0103 error

Anonymous · Post by **Anonymous** » Mon Oct 23, 2017 11:26 am

Hi,

I'm attempting to build my Vulcan solution with XSharp 1.0.2 (plus XSharp103.zip files) in VS2017.

Apart from the many XS0165 errors (use of unassigned locals) that I've had to suppress, why am I getting XS0103 errors for every occurrence of CRLF when this is defined in XSharpDefs.xh?

Mike

ic2 · Post by **ic2** » Mon Oct 23, 2017 12:01 pm

Hello Mike,

Chris wrote us earlier (when we added a seperate define for CRLF):

#include "XSharpDefs.vh"

and CRLF should work.

So I think a missing include may result in XS103 - The name 'identifier' does not exist in the current context.

Dick

MikeB · Post by **MikeB** » Mon Oct 23, 2017 12:34 pm

Hi Dick,

I was going to do that but it conflicts with the documentation where I read that XSharpDefs.xh was implicitly included in XSharp projects, but perhaps this only applied to new projects.

robert · Post by **robert** » Mon Oct 23, 2017 12:42 pm

Mike,
Can you check the project properties, on the Build Page, the value for "Suppress Standard Header file".
If this says false, then the include should be included automatically and CRLF should be defined.
If you are having a problem even when the value says FALSE, then please then send me your xsproj file?

Robert

MikeB · Post by **MikeB** » Mon Oct 23, 2017 12:54 pm

Hi Robert,

The setting is FALSE. XSPROJ file attached as TXT.

Thanks,

Mike

FFF · Post by **FFF** » Mon Oct 23, 2017 4:02 pm

Robert,
as we found, "false" is usually set (from template), but does not work until once swapped to true and back.
Just made a new Winform app, same behaviour as with console...
@Mike: did you try that?

Karl

Chris · Post by **Chris** » Mon Oct 23, 2017 6:18 pm

Hi Karl,

I checked a little further, looks like the problem is related to what Robert described in his previous article about project files, VS and MSBuild, there's a typo in the project option what saved to file. This still looks Greek to me

, but I am sure Robert will be able to fix it.

Chris

MikeB · Post by **MikeB** » Tue Oct 24, 2017 8:48 am

Hi Karl,

Yes, changing setting to TRUE then FALSE resolved this.

Thanks,

Mike

MikeB · Post by **MikeB** » Tue Oct 24, 2017 9:07 am

Hi Robert,

I've attached copies of another project file before and after editing as Karl suggested. I hope this helps.

Regards,

Mike

robert · Post by **robert** » Tue Oct 24, 2017 12:06 pm

Mike,
Thanks for the examples. This is exactly what I expected.
We plan to release a new version next week that will fix this.

Robert

PS: I have moved the whole thread to the product form, where it makes more sense

Main menu