Microsoft vscode is also a very good option to work with MSVC as you can use Antonino Perricone's Harbour debugger for vscode
Microsoft vscode is also a very good option to work with MSVC as you can use Antonino Perricone's Harbour debugger for vscode
D:\Tools\Harbour32MSVC2017\bin\harbour .\Source\open.PRG /m /n /w2 /es2 /gc0 /iD:\Tools\FWH1709\include /iD:\Tools\Harbour32MSVC2017\Include /iD:\Tools\LIB\Hb32_VC_Fwh1709\Include /iD:\Softway\CratusERP_MSVC\Include /o.\source\open.c
Harbour 3.2.0dev (r1703231115)
Copyright (c) 1999-2016, http://harbour-project.org/
Compiling '.\Source\open.PRG'...
Lines 8324, Functions/Procedures 3
Generating C source output to '.\source\open.c'... Done.1>D:\Softway\CratusERP_MSVC\Source\TOOLS.PRG(2338) Error E0030 Syntax error "syntax error at ','"oBrw:aCols[ 2 ]:bStrImage := {|, oBrw| oBrw:aRow[ 2 ] }D:\Tools\Harbour32MSVC2017\bin\harbour "%(FullPath)" /m /n w2 /es2 /gc0 /iD:\Tools\FWH1709\include /iD:\Tools\Harbour32MSVC2017\Include /iD:\Tools\LIB\Hb32_VC_Fwh1709\Include /iD:\Softway\CratusERP_MSVC\Include /o%(RelativeDir)\%(Filename).cChange this:
oBrw:aCols[ 2 ]:bStrImage := {|, oBrw| oBrw:aRow[ 2 ] }
into this:
oBrw:aCols[ 2 ]:bStrImage := {|x, oBrw| oBrw:aRow[ 2 ] }
Thanks Antonio.
But is generated this error:
Warning W0004 Codeblock parameter 'X' declared but not used in function '_BROWSEICONES'
I think because I use the / w2 parameter, which is a very severe build. So I changed it to:
oBrw:aCols[ 1 ]:bStrImage := {|x, oBrw| x := 0, oBrw:aRow[ 1 ] }
That it is ok, no warnings.
Thank you.
very good
Warnings may be useful in refining code, but they still allow a build of an ezecutable. I still see warnings on my builds but usually it has to do with superceeded commands, or that FWH has functions found in separate libraries.
I managed to successfully generate my project using Visual Studio 2019. 499 source files. I had no problem with W10.manifest. As part of the project I have a .LIB with 96 files, I managed to generate it successfully too. Some small details I will still review and test all the features. Overall I am quite satisfied with the changes and the VS environment.
My next step is to generate a DLL to store the icons and bitmaps used in the project.
I noticed that the size of both the .LIB and the EXE increased by approximately 30%.
Would this be normal or because it is being debugged? After all, what would be the difference between debug and release mode in this case?
Thank you all.
The release mode should not have debug info inside and thus the resulting size should be smaller
FUNCION Main ()
...
....
RETURN (NIL)
PROCEDURE ErrorSys ()
ErrorBlock ({| e | SW_ErrorDialog (e)}) // My error function have other name
RETURNfunction Main ()
ErrorBlock ({| e | SW_ErrorDialog (e)})
...
....
return nilUse uppercase for preprocessed keywords only (my advise)
I customized ErrorSys and link it in with no problem. I've added additional data to the report.
I see no problem with making a general change, if there are benefits