Good Morning,
I did want to report that I downloaded MS Visual Studio 2017 Community ( full package ) to my laptop. I then used it to build my "solution" created on my main machine with MSVS 2015. I ran the CLEAN utility and did a complete rebuild. It automatically prompted me, and updated the referenced libraries with MSVC.
I am still using the older Harbour builds made with VS 2015. The main reason is that Antonio made a few extra .libs to use with it that were Harbour source, but not in the normal .lib folder.
The program works fine with the older Harbour libraries. There are no build problems, nor are there any operational errors when running the program.
In time, I will update the Harbour libraries. I have retained MSVC 2015 plus the older libs on my production builds for now. I have too many developing features to change that at this moment.
For those considering MSVC plus Harbour, I will encourage you to move in that direction. The 2015 version was continually updated until early 2017 when the new version was released. My clients who use the application built with it find it to be smoother and faster than the copy built with xHarbour ( .com version ), and we are able to support more features ( like taking photos from within the application ). Since Visual Studio Community edition is full featured, and FREE ... it might be worth consideration. Also, it builds great in both 32 bit and 64 bit versions of FWH / Harbour ....
Tim
http://www.MasterLinkSoftware.com
http://www.autoshopwriter.com
timstone@masterlinksoftware.com
Using: FWH 23.10 with Harbour 3.2.0 / Microsoft Visual Studio Community 2022-24 32/64 bit